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 A
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>] _pri
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)
> [0.00]
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
`. `' P
12 matches
Mail list logo