Hi Geert,
> While the non-working case in your next email has
> "ramdisk dest is 0x0f7f6794" and a matching
> "initrd: 0f7f6794 - 1000".
> /me confused even more...
Just did a fresh test with both, powered down between tests..
Kernel 5.15/intrid 5.15:
Hi Stephen,
On Sat, Sep 10, 2022 at 2:01 AM Stephen Walsh wrote:
> > I think we really need to see the output of "amiboot -d",
> > for both the good and the bad cases.
>
> I had amiboot like so:
>
> amiboot -d -k vmlinux-5.15.0-2-m68k -r initrd.img-5.15.0-2-m68k
> root=/dev/sda2 fb=false
>
>
Hi Geert,
Am 09.09.2022 um 19:34 schrieb Geert Uytterhoeven:
Hi Michael,
On Fri, Sep 9, 2022 at 7:03 AM Michael Schmitz wrote:
Am 09.09.2022 um 13:36 schrieb Finn Thain:
Kernel 5.19, intrd 5.19
[0.00] Linux version 5.19.0-1-m68k (debian-ker...@lists.debian.org)
(gcc-11 (Debian
Hi Geert,
On Fri, 9 Sep 2022 09:34:21 +0200
Geert Uytterhoeven wrote:
> I think we really need to see the output of "amiboot -d",
> for both the good and the bad cases.
https://amiga.vk3heg.net/wp-content/uploads/2022/09/PXL_20220910_004939673-scaled.jpg
Kernel/Intrd: 5.19
Hi Geert.
> I think we really need to see the output of "amiboot -d",
> for both the good and the bad cases.
I had amiboot like so:
amiboot -d -k vmlinux-5.15.0-2-m68k -r initrd.img-5.15.0-2-m68k
root=/dev/sda2 fb=false
Didn't see anything different, in the output except for this at the
start
Hi Michael,
On Fri, 9 Sep 2022, Michael Schmitz wrote:
>
> I know nothing about the way amiboot works, and how the RAM chunk to
> copy the initrd image to is selected.
Same here. This is not a bug I can resolve. It's a bug for someone who
knows Amiga hardware and amiboot algorithms.
> Just
Hi Finn,
On Fri, Sep 9, 2022 at 9:24 AM Finn Thain wrote:
> On Fri, 9 Sep 2022, Stephen Walsh wrote:
> > Here's a test of kernel 5.16, intrid 5.16. It exited to busybox saying
> > it couldn’t find /dev/sda2 (root fs)
> >
> > ...
> > [ 116.98] scsi 1:0:0:0: tag#16 abort command
> > [
Hi Michael,
On Fri, Sep 9, 2022 at 7:03 AM Michael Schmitz wrote:
> Am 09.09.2022 um 13:36 schrieb Finn Thain:
>
> >> Kernel 5.19, intrd 5.19
> >>
> >>
> >> [0.00] Linux version 5.19.0-1-m68k
> >> (debian-ker...@lists.debian.org) (gcc-11 (Debian 11.3.0-5) 11.3.0, GNU
On Fri, 9 Sep 2022, Stephen Walsh wrote:
> Here's a test of kernel 5.16, intrid 5.16. It exited to busybox saying
> it couldn’t find /dev/sda2 (root fs)
>
> ...
> [ 116.98] scsi 1:0:0:0: tag#16 abort command
> [ 117.00] scsi 1:0:0:0: tag#16 New error handler wants HOST reset, cmd
>
Hi Finn,
Am 09.09.2022 um 13:36 schrieb Finn Thain:
Kernel 5.19, intrd 5.19
[0.00] Linux version 5.19.0-1-m68k (debian-ker...@lists.debian.org)
(gcc-11 (Debian 11.3.0-5) 11.3.0, GNU ld (GNU Binutils for Debian)
2.38.90.20220713) #1 Debian 5.19.6-1 (2022-09-01)
[0.00]
Here's a test of kernel 5.16, intrid 5.16. It exited to busybox saying
it couldn’t find /dev/sda2 (root fs)
[0.00] Linux version 5.16.0-6-m68k (debian-ker...@lists.debian.org)
(gcc-11 (Debian 11.2.0-19) 11.2.0, GNU ld (GNU Binutils for Debian) 2.38) #1
Debian
On Fri, 9 Sep 2022, Stephen Walsh wrote:
> Hi Finn,
>
> On Fri, 9 Sep 2022 11:36:49 +1000 (AEST)
> Finn Thain wrote:
>
> > You mean, you tried kernel 5.15 with initrd 5.19? The question is,
> > "did it oops?". Having seen the results below, I suspect that it
> > didn't oops, despite the
Hi Finn,
On Fri, 9 Sep 2022 11:36:49 +1000 (AEST)
Finn Thain wrote:
> You mean, you tried kernel 5.15 with initrd 5.19? The question is,
> "did it oops?". Having seen the results below, I suspect that it
> didn't oops, despite the large initrd.
ohh.. here's a successful boot with
On Fri, 9 Sep 2022, Stephen Walsh wrote:
> Hi Guys.
>
> As requested.
>
Thanks for sending those results.
> Finn I also tried kernel 5.19 with intrid 5.15..
>
> Still only Kernel/Intrid 5.15-02 is the one that boots.
>
You mean, you tried kernel 5.15 with initrd 5.19? The question is,
Hi Guys.
As requested.
Finn I also tried kernel 5.19 with intrid 5.15..
Still only Kernel/Intrid 5.15-02 is the one that boots.
command line was always (With only kernel/intred changes):
amiboot -k vmlinux-5.15.0-2-m68k -r initrd.img-5.15.0-2-m68k
root=/dev/sda2 fb=false debug=mem
Kernel
Hi Finn,
On Thu, Sep 8, 2022 at 2:49 AM Finn Thain wrote:
> On Thu, 8 Sep 2022, Stephen Walsh wrote:
> > >> amiboot -k vmlinux-5.15.0-2-m68k -r initrd.img-5.15.0-2-m68k
> > >> root=/dev/sda2 fb=false debug=mem
> > >
> > > Are you sure that is what you really used?
> > >
> >
> > Yes, that is what
Hi Stephen,
On Thu, Sep 8, 2022 at 1:58 AM Stephen Walsh wrote:
> >> amiboot -k vmlinux-5.15.0-2-m68k -r initrd.img-5.15.0-2-m68k
> >> root=/dev/sda2 fb=false debug=mem
> >
> > Are you sure that is what you really used?
>
> Yes, that is what I've been using and works with 5.15
>
> Screen shot of
On Thu, 8 Sep 2022, Stephen Walsh wrote:
> Hi Geert,
>
> >> amiboot -k vmlinux-5.15.0-2-m68k -r initrd.img-5.15.0-2-m68k
> >> root=/dev/sda2 fb=false debug=mem
> >
> > Are you sure that is what you really used?
> >
>
> Yes, that is what I've been using and works with 5.15
>
I think that
Hi Finn,
On 2022-09-08 08:19, Finn Thain wrote:
Kernel command line: ignore_loglevel -r initrd.img-5.19.0-1-m68k
root=/dev/sda2 fb=false debug=mem BOOT_IMAGE=vmlinux-5.19.0-1-m68k
Hence Amiboot didn't provide the initrd...
Okay, so the first couple of logs Stephen sent used the correct
Hi Geert,
amiboot -k vmlinux-5.15.0-2-m68k -r initrd.img-5.15.0-2-m68k
root=/dev/sda2 fb=false debug=mem
Are you sure that is what you really used?
Yes, that is what I've been using and works with 5.15
Screen shot of just before I started a new test. I boot the Amiga with
no
On Wed, 7 Sep 2022, Andreas Schwab wrote:
> On Sep 07 2022, Geert Uytterhoeven wrote:
>
> > So if the initrd is stored at the end of motherboard RAM:
> >
> > initrd: 0783283d - 0800
> >
> > The code
> >
> > memcmp(data, BOOTCONFIG_MAGIC, BOOTCONFIG_MAGIC_LEN)
> >
> > works. When the
On Wed, 7 Sep 2022, Geert Uytterhoeven wrote:
> On Wed, Sep 7, 2022 at 4:04 AM Stephen Walsh wrote:
> > On Wed, 7 Sep 2022 11:59:17 +1000 (AEST)
> > Finn Thain wrote:
> >
> > > > Here are three debugs. mixing the kernel/intrid's...
> > >
> > > What happens if you boot the 5.19 kernel/initrd
On Sep 07 2022, Geert Uytterhoeven wrote:
> So if the initrd is stored at the end of motherboard RAM:
>
> initrd: 0783283d - 0800
>
> The code
>
> memcmp(data, BOOTCONFIG_MAGIC, BOOTCONFIG_MAGIC_LEN)
>
> works. When the initrd is stored at the end of WarpEngine RAM:
>
> initrd:
On Sep 07 2022, Finn Thain wrote:
> On Wed, 7 Sep 2022, Geert Uytterhoeven wrote:
>
>> On Wed, Sep 7, 2022 at 12:09 AM Finn Thain wrote:
>> > Regarding the oops that was originally reported, the kernel already told
>> > us why it crashed:
>> >
>> > [0.00] Ignoring memory chunk at
On Wed, Sep 7, 2022 at 11:42 AM Andreas Schwab wrote:
> On Sep 07 2022, Finn Thain wrote:
> > On Wed, 7 Sep 2022, Geert Uytterhoeven wrote:
> >> On Wed, Sep 7, 2022 at 12:09 AM Finn Thain wrote:
> >> > Regarding the oops that was originally reported, the kernel already told
> >> > us why it
On Wed, 7 Sep 2022, Geert Uytterhoeven wrote:
> On Wed, Sep 7, 2022 at 12:09 AM Finn Thain wrote:
> > Regarding the oops that was originally reported, the kernel already told
> > us why it crashed:
> >
> > [0.00] Ignoring memory chunk at 0x780:0x80 before the first
> > chunk
> >
Hi Stephen,
On Wed, Sep 7, 2022 at 4:04 AM Stephen Walsh wrote:
> On Wed, 7 Sep 2022 11:59:17 +1000 (AEST)
> Finn Thain wrote:
>
> > > Here are three debugs. mixing the kernel/intrid's...
> >
> > What happens if you boot the 5.19 kernel/initrd pair with
> > "root=/dev/sda2" omitted from the
Hi Finn,
On Wed, Sep 7, 2022 at 12:09 AM Finn Thain wrote:
> Regarding the oops that was originally reported, the kernel already told
> us why it crashed:
>
> [0.00] Ignoring memory chunk at 0x780:0x80 before the first
> chunk
> [0.00] Fix your bootloader or use a
On Wed, 7 Sep 2022, Finn Thain wrote:
> On Wed, 7 Sep 2022, Stephen Walsh wrote:
>
> > On Wed, 7 Sep 2022 11:59:17 +1000 (AEST)
> > Finn Thain wrote:
> >
> > > > Here are three debugs. mixing the kernel/intrid's...
> > >
> > > What happens if you boot the 5.19 kernel/initrd pair with
> >
On Wed, 7 Sep 2022, Stephen Walsh wrote:
> On Wed, 7 Sep 2022 11:59:17 +1000 (AEST)
> Finn Thain wrote:
>
> > > Here are three debugs. mixing the kernel/intrid's...
> >
> > What happens if you boot the 5.19 kernel/initrd pair with
> > "root=/dev/sda2" omitted from the kernel parameters?
On Wed, 7 Sep 2022, Stephen Walsh wrote:
>
> Here are three debugs. mixing the kernel/intrid's...
>
What happens if you boot the 5.19 kernel/initrd pair with "root=/dev/sda2"
omitted from the kernel parameters?
It looks like the oops from the 5.18 build disappeared in the 5.19 build.
Hi Finn,
On Wed, 7 Sep 2022 11:59:17 +1000 (AEST)
Finn Thain wrote:
> > Here are three debugs. mixing the kernel/intrid's...
>
> What happens if you boot the 5.19 kernel/initrd pair with
> "root=/dev/sda2" omitted from the kernel parameters?
>
> It looks like the oops from the 5.18 build
Hi Geert,
On Tue, 6 Sep 2022 09:40:27 +0200
Geert Uytterhoeven wrote:
> > 5.18.16-1 (2022-08-10) [0.00] printk: debug: ignoring
> > loglevel setting. [0.00] printk: console [debug0] enabled [
> >0.00] Amiga hardware found: [A3000] VIDEO BLITTER AMBER_FF
> > AUDIO FLOPPY
On Tue, 6 Sep 2022, Laurent Vivier wrote:
> Le 06/09/2022 à 17:52, Andreas Schwab a écrit :
> > On Sep 06 2022, Eero Tamminen wrote:
> >
> >> Hi,
> >>
> >> On 6.9.2022 4.46, Stephen Walsh wrote:
> >>> [3.11] Call Trace: [<00354d80>] panic+0xc4/0x246
> >>> [3.11] [<00355744>]
Le 06/09/2022 à 17:52, Andreas Schwab a écrit :
On Sep 06 2022, Eero Tamminen wrote:
Hi,
On 6.9.2022 4.46, Stephen Walsh wrote:
[3.11] Call Trace: [<00354d80>] panic+0xc4/0x246
[3.11] [<00355744>] _printk+0x0/0x18
[3.11] [<00355756>] _printk+0x12/0x18
[3.11]
On Sep 06 2022, Eero Tamminen wrote:
> Hi,
>
> On 6.9.2022 4.46, Stephen Walsh wrote:
>> [3.11] Call Trace: [<00354d80>] panic+0xc4/0x246
>> [3.11] [<00355744>] _printk+0x0/0x18
>> [3.11] [<00355756>] _printk+0x12/0x18
>> [3.11] [<001ed30c>] strlen+0x0/0x14
>> [
Hi,
On 6.9.2022 4.46, Stephen Walsh wrote:
[3.11] Call Trace: [<00354d80>] panic+0xc4/0x246
[3.11] [<00355744>] _printk+0x0/0x18
[3.11] [<00355756>] _printk+0x12/0x18
[3.11] [<001ed30c>] strlen+0x0/0x14
[3.11] [<0051054a>] mount_block_root+0x17a/0x194
Hi Stephen,
On Tue, Sep 6, 2022 at 3:47 AM Stephen Walsh wrote:
> Debug booting 5.15.0-2
>
> [0.00] Linux version 5.15.0-2-m68k (debian-ker...@lists.debian.org)
> (gcc-11 (Debian 11.2.0-12) 11.2.0, GNU ld (GNU Binutils for Debian) 2.37) #1
> Debian 5.15.5-2 (2021-12-18)
> [
Hi Ingo,
On Tue, Sep 6, 2022 at 7:46 AM Ingo Jürgensmann wrote:
> Am 06.09.2022 um 03:46 schrieb Stephen Walsh :
> >> So, here is the error and a possible solution: using a memfile might
> >> help.
> > I've not done a memfile before so will need a pointer or two.
>
> Quick pointer was to look it
Hi Stephen!
On 9/4/22 03:48, Stephen Walsh wrote:
Also, kernel 5.19.6 is currently being built and should be available
soonish.
I'll test that when it's released.
It's in the archives now. You can give it a try.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `'
Am 06.09.2022 um 03:46 schrieb Stephen Walsh :
>> So, here is the error and a possible solution: using a memfile might
>> help.
> I've not done a memfile before so will need a pointer or two.
Quick pointer was to look it up in my blog about the BigRamPlus:
Hello Ingo,
On Sun, 4 Sep 2022 10:55:40 +0200
Ingo Jürgensmann wrote:
> > 0x0a00-0x0fff] [0.00] Initmem setup
> > node 0 [mem 0x0a00-0x0fff] [0.00]
> > Unable to handle kernel access at virtual address (ptrval)
>
> So, here is the
On Sun, 4 Sep 2022, Stephen Walsh wrote:
> > What happens if you boot the known-good initrd (v5.15) with the
> > crashy vmlinux binary (v5.18)?
>
> > The combination won't boot normally but should fail normally (wrong
> > modules) and not fail with an oops.
>
> It still crashes, but I can see
Hi Finn,
> What happens if you boot the known-good initrd (v5.15) with the
> crashy vmlinux binary (v5.18)?
> The combination won't boot normally but should fail normally (wrong
> modules) and not fail with an oops.
It still crashes, but I can see the process.
Searching for SAVEKMSG magic...
Hi Stephen,
On Sun, 4 Sep 2022, Stephen Walsh wrote:
> On Sat, 3 Sep 2022 13:10:46 +0200
> Ingo Jürgensmann wrote:
>
> > > Amiga 3000
> > > Warpengine 68040@40Mhz
> > > 128Mb ram on warpengine
> >
> > Uhm? How do you get the Warpengine with 128MB into an A3000? Usually
> > there is not enough
Am 04.09.2022 um 03:50 schrieb Stephen Walsh :
>>> Amiga 3000
>>> Warpengine 68040@40Mhz
>>> 128Mb ram on warpengine
>> Uhm? How do you get the Warpengine with 128MB into an A3000? Usually
>> there is not enough space on the Warpengine for 4x 32 MB SIMMs - or
>> did you use 2x 64MB ones or 4x
On Sat, 3 Sep 2022 13:10:46 +0200
Ingo Jürgensmann wrote:
> > Amiga 3000
> > Warpengine 68040@40Mhz
> > 128Mb ram on warpengine
>
> Uhm? How do you get the Warpengine with 128MB into an A3000? Usually
> there is not enough space on the Warpengine for 4x 32 MB SIMMs - or
> did you use 2x 64MB
Hi Adrian,
On Sat, 3 Sep 2022 09:25:13 +0200
John Paul Adrian Glaubitz wrote:
> Might be a wise idea to cross-post this to the Linux/m68k kernel
> mailing list.
Didn't know there was one.
> Also, kernel 5.19.6 is currently being built and should be available
> soonish.
I'll test that when
Am 03.09.2022 um 02:24 schrieb Stephen Walsh :
> I have "Debian GNU/Linux bookworm/sid" installed on both Qemu-user and
> real hardware.
> Amiga 3000
> Warpengine 68040@40Mhz
> 128Mb ram on warpengine
Uhm? How do you get the Warpengine with 128MB into an A3000? Usually there is
not enough space
Hi Stephen!
Might be a wise idea to cross-post this to the Linux/m68k kernel mailing list.
Also, kernel 5.19.6 is currently being built and should be available soonish.
Adrian
On 9/3/22 02:24, Stephen Walsh wrote:
I have "Debian GNU/Linux bookworm/sid" installed on both Qemu-user and
real
Hi Guys,
I have "Debian GNU/Linux bookworm/sid" installed on both Qemu-user and
real hardware.
Amiga 3000
Warpengine 68040@40Mhz
128Mb ram on warpengine
8Mb Fast ram on MB
2Mb Chip ram
X-surf Network card (Original)
Kickstart 3.2
Qemu is working with no issues.
Real hardware issue:
Booting
51 matches
Mail list logo
