From pparkkin at iki.fi  Sat Nov  8 01:21:01 2008
From: pparkkin at iki.fi (Paavo Parkkinen)
Date: Fri, 7 Nov 2008 20:21:01 -0500
Subject: [movitz-devel] Warning: Auto-bootstrapping CLOS completed.
Message-ID: <b9edbea70811071721h256a89a9v262cd34069ba2737@mail.gmail.com>

I compiled and dumped the los0 image with SBCL, and booted it with
qemu like I've done many times before, only this time I got this:

Enter..Ok.
Installing los0-GC with 63238 KB.
Break: Auto-bootstrapping CLOS.
Warning: Auto-bootstrapping CLOS completed.
 0: Return from break: Auto-bootstrapping CLOS.
[0d] LOS0> 0
Warning: CLOS was already bootstrapped: T
Warning: Auto-bootstrapping CLOS completed.
Error: Out of memory. Please take out the garbage.
[0d] LOS0>

Only thing I can think of that's changed is, I installed the new
version of Ubuntu recently. Any idea what might have changed or if I'm
maybe missing something?

p



From pparkkin at iki.fi  Sat Nov  8 11:59:47 2008
From: pparkkin at iki.fi (Paavo Parkkinen)
Date: Sat, 8 Nov 2008 06:59:47 -0500
Subject: [movitz-devel] Warning: Auto-bootstrapping CLOS completed.
In-Reply-To: <Pine.LNX.4.64.0811080403280.21006@Psilocybe.Update.UU.SE>
References: <b9edbea70811071721h256a89a9v262cd34069ba2737@mail.gmail.com>
	<Pine.LNX.4.64.0811080403280.21006@Psilocybe.Update.UU.SE>
Message-ID: <b9edbea70811080359p1b0de045g9b00725712f921f9@mail.gmail.com>

2008/11/7 Andreas Davour <ante at update.uu.se>:
> On Fri, 7 Nov 2008, Paavo Parkkinen wrote:
>
>> I compiled and dumped the los0 image with SBCL, and booted it with
>> qemu like I've done many times before, only this time I got this:
>>
>> Enter..Ok.
>> Installing los0-GC with 63238 KB.
>> Break: Auto-bootstrapping CLOS.
>> Warning: Auto-bootstrapping CLOS completed.
>> 0: Return from break: Auto-bootstrapping CLOS.
>> [0d] LOS0> 0
>> Warning: CLOS was already bootstrapped: T
>> Warning: Auto-bootstrapping CLOS completed.
>> Error: Out of memory. Please take out the garbage.
>> [0d] LOS0>
>>
>> Only thing I can think of that's changed is, I installed the new
>> version of Ubuntu recently. Any idea what might have changed or if I'm
>> maybe missing something?
>
> I don't think I can help out, but interesting information nevertheless would
> be if this is from cvs or the git repository and when did you check out?

First time I got the Warnings with a pretty old cvs check out. After
that I did a fresh check out and got the same result.

p



From pparkkin at iki.fi  Sat Nov  8 16:47:39 2008
From: pparkkin at iki.fi (Paavo Parkkinen)
Date: Sat, 8 Nov 2008 11:47:39 -0500
Subject: [movitz-devel] Warning: Auto-bootstrapping CLOS completed.
In-Reply-To: <e52ec4270811080816y2edcb365gafe9b55e689f32ae@mail.gmail.com>
References: <b9edbea70811071721h256a89a9v262cd34069ba2737@mail.gmail.com>
	<Pine.LNX.4.64.0811080403280.21006@Psilocybe.Update.UU.SE>
	<b9edbea70811080359p1b0de045g9b00725712f921f9@mail.gmail.com>
	<e52ec4270811080816y2edcb365gafe9b55e689f32ae@mail.gmail.com>
Message-ID: <b9edbea70811080847n10818966t19c216c13a484c45@mail.gmail.com>

I did a fresh install into a formatted / and /home. The first time I
tried creating a new image, I did it in a backup of my old home
directory, but the next time was in the fresh home directory with a
fresh movitz check out.

p

2008/11/8 rob levy <r.p.levy at gmail.com>:
> This is probably way off, but if you installed the new version of Ubuntu and
> it upgraded SBCL, then you may need to delete stale FASLs.
>
> Rob
>
> On Sat, Nov 8, 2008 at 6:59 AM, Paavo Parkkinen <pparkkin at iki.fi> wrote:
>>
>> 2008/11/7 Andreas Davour <ante at update.uu.se>:
>> > On Fri, 7 Nov 2008, Paavo Parkkinen wrote:
>> >
>> >> I compiled and dumped the los0 image with SBCL, and booted it with
>> >> qemu like I've done many times before, only this time I got this:
>> >>
>> >> Enter..Ok.
>> >> Installing los0-GC with 63238 KB.
>> >> Break: Auto-bootstrapping CLOS.
>> >> Warning: Auto-bootstrapping CLOS completed.
>> >> 0: Return from break: Auto-bootstrapping CLOS.
>> >> [0d] LOS0> 0
>> >> Warning: CLOS was already bootstrapped: T
>> >> Warning: Auto-bootstrapping CLOS completed.
>> >> Error: Out of memory. Please take out the garbage.
>> >> [0d] LOS0>
>> >>
>> >> Only thing I can think of that's changed is, I installed the new
>> >> version of Ubuntu recently. Any idea what might have changed or if I'm
>> >> maybe missing something?
>> >
>> > I don't think I can help out, but interesting information nevertheless
>> > would
>> > be if this is from cvs or the git repository and when did you check out?
>>
>> First time I got the Warnings with a pretty old cvs check out. After
>> that I did a fresh check out and got the same result.
>>
>> p
>>
>> _______________________________________________
>> movitz-devel site list
>> movitz-devel at common-lisp.net
>> http://common-lisp.net/mailman/listinfo/movitz-devel
>
>



From r.p.levy at gmail.com  Sat Nov  8 16:16:39 2008
From: r.p.levy at gmail.com (rob levy)
Date: Sat, 8 Nov 2008 11:16:39 -0500
Subject: [movitz-devel] Warning: Auto-bootstrapping CLOS completed.
In-Reply-To: <b9edbea70811080359p1b0de045g9b00725712f921f9@mail.gmail.com>
References: <b9edbea70811071721h256a89a9v262cd34069ba2737@mail.gmail.com>
	<Pine.LNX.4.64.0811080403280.21006@Psilocybe.Update.UU.SE>
	<b9edbea70811080359p1b0de045g9b00725712f921f9@mail.gmail.com>
Message-ID: <e52ec4270811080816y2edcb365gafe9b55e689f32ae@mail.gmail.com>

This is probably way off, but if you installed the new version of Ubuntu and
it upgraded SBCL, then you may need to delete stale FASLs.

Rob

On Sat, Nov 8, 2008 at 6:59 AM, Paavo Parkkinen <pparkkin at iki.fi> wrote:

> 2008/11/7 Andreas Davour <ante at update.uu.se>:
> > On Fri, 7 Nov 2008, Paavo Parkkinen wrote:
> >
> >> I compiled and dumped the los0 image with SBCL, and booted it with
> >> qemu like I've done many times before, only this time I got this:
> >>
> >> Enter..Ok.
> >> Installing los0-GC with 63238 KB.
> >> Break: Auto-bootstrapping CLOS.
> >> Warning: Auto-bootstrapping CLOS completed.
> >> 0: Return from break: Auto-bootstrapping CLOS.
> >> [0d] LOS0> 0
> >> Warning: CLOS was already bootstrapped: T
> >> Warning: Auto-bootstrapping CLOS completed.
> >> Error: Out of memory. Please take out the garbage.
> >> [0d] LOS0>
> >>
> >> Only thing I can think of that's changed is, I installed the new
> >> version of Ubuntu recently. Any idea what might have changed or if I'm
> >> maybe missing something?
> >
> > I don't think I can help out, but interesting information nevertheless
> would
> > be if this is from cvs or the git repository and when did you check out?
>
> First time I got the Warnings with a pretty old cvs check out. After
> that I did a fresh check out and got the same result.
>
> p
>
> _______________________________________________
> movitz-devel site list
> movitz-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/movitz-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/movitz-devel/attachments/20081108/4d09b8c0/attachment.html>

From mbealby at gmail.com  Sat Nov  8 20:39:14 2008
From: mbealby at gmail.com (Martin Bealby)
Date: Sat, 08 Nov 2008 20:39:14 +0000
Subject: [movitz-devel] Warning: Auto-bootstrapping CLOS completed.
References: <b9edbea70811071721h256a89a9v262cd34069ba2737@mail.gmail.com>
	<Pine.LNX.4.64.0811080403280.21006@Psilocybe.Update.UU.SE>
	<b9edbea70811080359p1b0de045g9b00725712f921f9@mail.gmail.com>
	<e52ec4270811080816y2edcb365gafe9b55e689f32ae@mail.gmail.com>
	<b9edbea70811080847n10818966t19c216c13a484c45@mail.gmail.com>
Message-ID: <87bpwqx899.fsf@tombstone.bealbywm.plus.com>

"Paavo Parkkinen" <pparkkin at iki.fi> writes:

> I did a fresh install into a formatted / and /home. The first time I
> tried creating a new image, I did it in a backup of my old home
> directory, but the next time was in the fresh home directory with a
> fresh movitz check out.
>
> p
>

I also have this error appearing on my machine, all fasls were
previously removed.

However, the error only appears when I specify a hard disk image.

fails: qemu -no-kqemu -fda los0-image -hda ~/path/to/harddisk.img -boot
a -m 16

works: qemu -no-kqemu -fda los0-image -boot a -m 16

If this helps:

qemu version 0.9.1
sbcl version 1.0.18

Martin




From frodef at cs.uit.no  Mon Nov 10 23:00:56 2008
From: frodef at cs.uit.no (Frode V. Fjeld)
Date: Tue, 11 Nov 2008 00:00:56 +0100
Subject: [movitz-devel] Warning: Auto-bootstrapping CLOS completed.
References: <b9edbea70811071721h256a89a9v262cd34069ba2737@mail.gmail.com>
Message-ID: <878wrrnq3b.fsf@disk.lan>

"Paavo Parkkinen" <pparkkin at iki.fi> writes:

> I compiled and dumped the los0 image with SBCL, and booted it with
> qemu like I've done many times before, only this time I got this:
>
> Enter..Ok.
> Installing los0-GC with 63238 KB.
> Break: Auto-bootstrapping CLOS.
> Warning: Auto-bootstrapping CLOS completed.
>  0: Return from break: Auto-bootstrapping CLOS.
> [0d] LOS0> 0
> Warning: CLOS was already bootstrapped: T
> Warning: Auto-bootstrapping CLOS completed.
> Error: Out of memory. Please take out the garbage.
> [0d] LOS0>

There is a bootstrapping of CLOS that is initiated quite early in the
boot process, but if some method dispatch is triggered before this
happens, you get the above break. It usually indicates that something
"bad" or too "complex" happened too early in the boot process.

A stack-trace should tell you/us what is triggering the CLOS bootstrap.

-- 
Frode V. Fjeld




From pparkkin at iki.fi  Mon Nov 17 12:25:19 2008
From: pparkkin at iki.fi (Paavo Parkkinen)
Date: Mon, 17 Nov 2008 07:25:19 -0500
Subject: [movitz-devel] Warning: Auto-bootstrapping CLOS completed.
In-Reply-To: <878wrrnq3b.fsf@disk.lan>
References: <b9edbea70811071721h256a89a9v262cd34069ba2737@mail.gmail.com>
	<878wrrnq3b.fsf@disk.lan>
Message-ID: <b9edbea70811170425j72d448b3nb733b18de6fe36ee@mail.gmail.com>

Here's the backtrace from movitz:

Enter..Ok.
Installing los0-GC with 63238 KB.
Break: Auto-bootstrapping CLOS.
Warning: Auto-bootstrapping CLOS completed.
 0: Return from break: Auto-bootstrapping CLOS.
[0d] LOS0> :bt
 <3 (BREAK "Auto-bootstrapping CLOS.")
 <1 (MUERTE::SIGNAL-SIMPLE SIMPLE-CONDITION NEWLINE NIL)
 <= (SIGNAL NEWLINE)
 <= (X86-PC::TEXTMODE-SCROLL-DOWN)
 <= (X86-PC::TEXTMODE-WRITE-CHAR #\Newline)
 <= (TEXTMODE-CONSOLE MUERTE::STREAM-WRITE-CHAR {ebx unknown})
 <= (MUERTE::%WRITE-CHAR #\Newline #<function TEXTMODE-CONSOLE>)
 <= (WRITE-CHAR #\Newline NIL)
 <= (TERPRI)
 <= (MUERTE::FORMAT-BY-STRING "~&Installing los0-GC with ~D KB.~%" #x0 #x0 NIL)
 <= (FORMAT T "~&Installing los0-GC with ~D KB.~%" #xf706)
 <= (GENESIS)
 <= (MUERTE::|losp/los0.lisp|)
 ...


p

2008/11/10 Frode V. Fjeld <frodef at cs.uit.no>:
> "Paavo Parkkinen" <pparkkin at iki.fi> writes:
>
>> I compiled and dumped the los0 image with SBCL, and booted it with
>> qemu like I've done many times before, only this time I got this:
>>
>> Enter..Ok.
>> Installing los0-GC with 63238 KB.
>> Break: Auto-bootstrapping CLOS.
>> Warning: Auto-bootstrapping CLOS completed.
>>  0: Return from break: Auto-bootstrapping CLOS.
>> [0d] LOS0> 0
>> Warning: CLOS was already bootstrapped: T
>> Warning: Auto-bootstrapping CLOS completed.
>> Error: Out of memory. Please take out the garbage.
>> [0d] LOS0>
>
> There is a bootstrapping of CLOS that is initiated quite early in the
> boot process, but if some method dispatch is triggered before this
> happens, you get the above break. It usually indicates that something
> "bad" or too "complex" happened too early in the boot process.
>
> A stack-trace should tell you/us what is triggering the CLOS bootstrap.
>
> --
> Frode V. Fjeld
>
>
> _______________________________________________
> movitz-devel site list
> movitz-devel at common-lisp.net
> http://common-lisp.net/mailman/listinfo/movitz-devel
>



From frodef at cs.uit.no  Fri Nov 21 19:42:42 2008
From: frodef at cs.uit.no (Frode V. Fjeld)
Date: Fri, 21 Nov 2008 20:42:42 +0100
Subject: [movitz-devel] Warning: Auto-bootstrapping CLOS completed.
References: <b9edbea70811071721h256a89a9v262cd34069ba2737@mail.gmail.com>
	<878wrrnq3b.fsf@disk.lan>
	<b9edbea70811170425j72d448b3nb733b18de6fe36ee@mail.gmail.com>
Message-ID: <87y6zcsw5p.fsf@disk.lan>

"Paavo Parkkinen" <pparkkin at iki.fi> writes:

> Here's the backtrace from movitz:
>
> Enter..Ok.
> Installing los0-GC with 63238 KB.
> Break: Auto-bootstrapping CLOS.
> Warning: Auto-bootstrapping CLOS completed.
>  0: Return from break: Auto-bootstrapping CLOS.
> [0d] LOS0> :bt
>  <3 (BREAK "Auto-bootstrapping CLOS.")
>  <1 (MUERTE::SIGNAL-SIMPLE SIMPLE-CONDITION NEWLINE NIL)
>  <= (SIGNAL NEWLINE)
>  <= (X86-PC::TEXTMODE-SCROLL-DOWN)
>  <= (X86-PC::TEXTMODE-WRITE-CHAR #\Newline)
>  <= (TEXTMODE-CONSOLE MUERTE::STREAM-WRITE-CHAR {ebx unknown})
>  <= (MUERTE::%WRITE-CHAR #\Newline #<function TEXTMODE-CONSOLE>)
>  <= (WRITE-CHAR #\Newline NIL)
>  <= (TERPRI)
>  <= (MUERTE::FORMAT-BY-STRING "~&Installing los0-GC with ~D KB.~%" #x0 #x0 NIL)
>  <= (FORMAT T "~&Installing los0-GC with ~D KB.~%" #xf706)
>  <= (GENESIS)
>  <= (MUERTE::|losp/los0.lisp|)

Right, I've seen this before :-)

What happens is simply that the screen is (attempted) scrolled before
CLOS is bootstrapped. As you can see, I signal a condition when this
happens, and conditions are CLOS instances.

This happens e.g. when the BIOS is unusually verbose, or there's
something else early in the boot sequence that prints too much to the
console.

Obviously this is not a satisfactory state of affairs in general, but
I haven't taken the time to devise a good solution to this problem
yet.


Frode




From macoovacany at gmail.com  Sat Nov 22 03:23:35 2008
From: macoovacany at gmail.com (Tim McKeaveney)
Date: Sat, 22 Nov 2008 12:23:35 +0900
Subject: [movitz-devel] Warning: Auto-bootstrapping CLOS completed.
In-Reply-To: <87y6zcsw5p.fsf@disk.lan>
References: <b9edbea70811071721h256a89a9v262cd34069ba2737@mail.gmail.com>
	<878wrrnq3b.fsf@disk.lan>
	<b9edbea70811170425j72d448b3nb733b18de6fe36ee@mail.gmail.com>
	<87y6zcsw5p.fsf@disk.lan>
Message-ID: <4ad0e340811211923v23568640gf84c3564a630ad36@mail.gmail.com>

Frode,

>
> Right, I've seen this before :-)
>
> What happens is simply that the screen is (attempted) scrolled before
> CLOS is bootstrapped. As you can see, I signal a condition when this
> happens, and conditions are CLOS instances.
>

Why did you want to signal a condition here?

Regards,
   Timbo



From frodef at cs.uit.no  Mon Nov 24 17:35:14 2008
From: frodef at cs.uit.no (Frode V. Fjeld)
Date: Mon, 24 Nov 2008 18:35:14 +0100
Subject: [movitz-devel] Warning: Auto-bootstrapping CLOS completed.
References: <b9edbea70811071721h256a89a9v262cd34069ba2737@mail.gmail.com>
	<878wrrnq3b.fsf@disk.lan>
	<b9edbea70811170425j72d448b3nb733b18de6fe36ee@mail.gmail.com>
	<87y6zcsw5p.fsf@disk.lan>
	<4ad0e340811211923v23568640gf84c3564a630ad36@mail.gmail.com>
Message-ID: <87skphrprh.fsf@disk.lan>

>> What happens is simply that the screen is (attempted) scrolled before
>> CLOS is bootstrapped. As you can see, I signal a condition when this
>> happens, and conditions are CLOS instances.

"Tim McKeaveney" <macoovacany at gmail.com> writes:

> Why did you want to signal a condition here?

It's used to e.g. implement the functionality for the :more top-level
command (try e.g. ":more (apropos 'print)).

-- 
Frode




From movitz-devel at common-lisp.net  Tue Nov 25 05:18:49 2008
From: movitz-devel at common-lisp.net (movitz-devel at common-lisp.net)
Date: Tue, 25 Nov 2008 05:18:49 -0000
Subject: [movitz-devel] ci.Doctor Odell
Message-ID: <mailman.0.1428527490.2555.movitz-devel@common-lisp.net>

An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/movitz-devel/attachments/20081125/06e19092/attachment.html>