* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
@ 2004-01-29 20:13 ` Mustafa Hussein
2004-01-29 20:18 ` Ben Collins
` (33 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Mustafa Hussein @ 2004-01-29 20:13 UTC (permalink / raw)
To: sparclinux
Hi Ben,
I tried to boot a ~4.1MB 2.6.2-rc2 image using second.b version 1.4.2 that I
compiled overnight. Here is what I got:
SILO version 1.4.2
boot: linux2.6.2-rc2
Allocated 8 megs of memory at 0x40000000 for kernel
Uncompressing image ...
Loaded kernel version 2.6.2 ...
Remapping the kernel ... done
And it doesn't go any further, I had to cold-boot (keyboard unreponsive).
I also have to mention that after unpacking second.b from the silo-loaders
package into /boot and issueing "silo -f" as per your earlier message; I got
a Fast Data Access Miss error, and had to boot off the Debian install cd and
chroot then issue "silo -f" again to fix the problem.
I kept second.b 1.4.2 and it boots the existing image just fine (a 3.4 MB
kernel 2.6.2-rc1 image)
Ultra10/333MHz/384MB/Elite3D-m3/OBP3.31
Thanks,
Mustafa
On Thursday 29 January 2004 12:29 pm, Ben Collins wrote:
> I've tested and fixed initrd support for sparc64, so that's safe.
>
> I've also cleaned up some things. Upon further testing, I was able to
> boot a 6.8Meg image. Not sure why it didn't work the first time, but
> beware it may be flakey.
>
> I'm a little disappointed. I haven't gotten any feedback from people
> testing this new version. So either no one cares, or it works good and
> people don't want to waste their time sending "worked for me" emails :)
>
> Usual place: http://www.sparc-boot.org/pub/silo/
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
2004-01-29 20:13 ` Mustafa Hussein
@ 2004-01-29 20:18 ` Ben Collins
2004-01-29 20:30 ` Ben Collins
` (32 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Ben Collins @ 2004-01-29 20:18 UTC (permalink / raw)
To: sparclinux
On Thu, Jan 29, 2004 at 02:13:21PM -0600, Mustafa Hussein wrote:
> Hi Ben,
> I tried to boot a ~4.1MB 2.6.2-rc2 image using second.b version 1.4.2 that I
> compiled overnight. Here is what I got:
>
> SILO version 1.4.2
> boot: linux2.6.2-rc2
> Allocated 8 megs of memory at 0x40000000 for kernel
> Uncompressing image ...
> Loaded kernel version 2.6.2 ...
> Remapping the kernel ... done
>
Can you boot with "linux2.6.2-rc2 -p", so we can see where it really
stops?
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
2004-01-29 20:13 ` Mustafa Hussein
2004-01-29 20:18 ` Ben Collins
@ 2004-01-29 20:30 ` Ben Collins
2004-01-29 20:34 ` Otto Solares
` (31 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Ben Collins @ 2004-01-29 20:30 UTC (permalink / raw)
To: sparclinux
On Thu, Jan 29, 2004 at 02:34:02PM -0600, Otto Solares wrote:
> On Thu, Jan 29, 2004 at 01:29:54PM -0500, Ben Collins wrote:
> > I've tested and fixed initrd support for sparc64, so that's safe.
> >
> > I've also cleaned up some things. Upon further testing, I was able to
> > boot a 6.8Meg image. Not sure why it didn't work the first time, but
> > beware it may be flakey.
> >
> > I'm a little disappointed. I haven't gotten any feedback from people
> > testing this new version. So either no one cares, or it works good and
> > people don't want to waste their time sending "worked for me" emails :)
> >
> > Usual place: http://www.sparc-boot.org/pub/silo/
>
> You talk something about needed kernel changes to properly use this
> new silo, where are the patches or 2.6.2-rc2-bk3 is good for testing?
You didn't read everything I said then. I said to make use of the larger
kernel sizes, you need the kernel patches, but to use this silo, you
don't. I wanted to make sure it didn't break existing installs.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (2 preceding siblings ...)
2004-01-29 20:30 ` Ben Collins
@ 2004-01-29 20:34 ` Otto Solares
2004-01-29 20:37 ` Ben Collins
` (30 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Otto Solares @ 2004-01-29 20:34 UTC (permalink / raw)
To: sparclinux
On Thu, Jan 29, 2004 at 01:29:54PM -0500, Ben Collins wrote:
> I've tested and fixed initrd support for sparc64, so that's safe.
>
> I've also cleaned up some things. Upon further testing, I was able to
> boot a 6.8Meg image. Not sure why it didn't work the first time, but
> beware it may be flakey.
>
> I'm a little disappointed. I haven't gotten any feedback from people
> testing this new version. So either no one cares, or it works good and
> people don't want to waste their time sending "worked for me" emails :)
>
> Usual place: http://www.sparc-boot.org/pub/silo/
You talk something about needed kernel changes to properly use this
new silo, where are the patches or 2.6.2-rc2-bk3 is good for testing?
-solca
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (3 preceding siblings ...)
2004-01-29 20:34 ` Otto Solares
@ 2004-01-29 20:37 ` Ben Collins
2004-01-29 20:55 ` Otto Solares
` (29 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Ben Collins @ 2004-01-29 20:37 UTC (permalink / raw)
To: sparclinux
> > SILO version 1.4.2
> > boot: linux2.6.2-rc2
> > Allocated 8 megs of memory at 0x40000000 for kernel
> > Uncompressing image ...
> > Loaded kernel version 2.6.2 ...
> > Remapping the kernel ... done
Wait, I know what the issue is here. Dave pulled a change from me that
set the HdrS ver to 0x300, which is what SILO keys off of to see if the
kernel supports being loaded to high memory. Problem is, it doesn't
actually.
So avoid -rc2 with current SILO. Wait for -rc3 (or 2.6.2 final), or use
-rc1.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (4 preceding siblings ...)
2004-01-29 20:37 ` Ben Collins
@ 2004-01-29 20:55 ` Otto Solares
2004-01-29 21:01 ` Ben Collins
` (28 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Otto Solares @ 2004-01-29 20:55 UTC (permalink / raw)
To: sparclinux
On Thu, Jan 29, 2004 at 03:30:39PM -0500, Ben Collins wrote:
> On Thu, Jan 29, 2004 at 02:34:02PM -0600, Otto Solares wrote:
> > On Thu, Jan 29, 2004 at 01:29:54PM -0500, Ben Collins wrote:
> > > I've tested and fixed initrd support for sparc64, so that's safe.
> > >
> > > I've also cleaned up some things. Upon further testing, I was able to
> > > boot a 6.8Meg image. Not sure why it didn't work the first time, but
> > > beware it may be flakey.
> > >
> > > I'm a little disappointed. I haven't gotten any feedback from people
> > > testing this new version. So either no one cares, or it works good and
> > > people don't want to waste their time sending "worked for me" emails :)
> > >
> > > Usual place: http://www.sparc-boot.org/pub/silo/
> >
> > You talk something about needed kernel changes to properly use this
> > new silo, where are the patches or 2.6.2-rc2-bk3 is good for testing?
>
> You didn't read everything I said then. I said to make use of the larger
> kernel sizes, you need the kernel patches, but to use this silo, you
> don't. I wanted to make sure it didn't break existing installs.
That's the point, test the larger kernel sizes. Is pointless to ask
people to test larger sizes and don't provide or make clear where the
kernel patches are. So my original question remains.
-solca
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (5 preceding siblings ...)
2004-01-29 20:55 ` Otto Solares
@ 2004-01-29 21:01 ` Ben Collins
2004-01-29 22:20 ` dree
` (27 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Ben Collins @ 2004-01-29 21:01 UTC (permalink / raw)
To: sparclinux
On Thu, Jan 29, 2004 at 02:55:30PM -0600, Otto Solares wrote:
> On Thu, Jan 29, 2004 at 03:30:39PM -0500, Ben Collins wrote:
> > On Thu, Jan 29, 2004 at 02:34:02PM -0600, Otto Solares wrote:
> > > On Thu, Jan 29, 2004 at 01:29:54PM -0500, Ben Collins wrote:
> > > > I've tested and fixed initrd support for sparc64, so that's safe.
> > > >
> > > > I've also cleaned up some things. Upon further testing, I was able to
> > > > boot a 6.8Meg image. Not sure why it didn't work the first time, but
> > > > beware it may be flakey.
> > > >
> > > > I'm a little disappointed. I haven't gotten any feedback from people
> > > > testing this new version. So either no one cares, or it works good and
> > > > people don't want to waste their time sending "worked for me" emails :)
> > > >
> > > > Usual place: http://www.sparc-boot.org/pub/silo/
> > >
> > > You talk something about needed kernel changes to properly use this
> > > new silo, where are the patches or 2.6.2-rc2-bk3 is good for testing?
> >
> > You didn't read everything I said then. I said to make use of the larger
> > kernel sizes, you need the kernel patches, but to use this silo, you
> > don't. I wanted to make sure it didn't break existing installs.
>
> That's the point, test the larger kernel sizes. Is pointless to ask
> people to test larger sizes and don't provide or make clear where the
> kernel patches are. So my original question remains.
Read the fucking email. I want people to test the _old_ smaller kernels
_first_. I would rather the larger kernels be broken than for the new
SILO to not work with the older kernels.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (6 preceding siblings ...)
2004-01-29 21:01 ` Ben Collins
@ 2004-01-29 22:20 ` dree
2004-01-29 22:58 ` Otto Solares
` (26 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: dree @ 2004-01-29 22:20 UTC (permalink / raw)
To: sparclinux
Hi,
on my ultra10, 128MB, 440Mhz ,running sid:
a vanilla 2.6.1 vmlinux kernel size 3.8 MB boots fine
a 2.4.19 vmlinux kernel size 1.3MB boots fine
a 2.4.24 image image kernel size 3.1 MB boots fine
a 2.4.18-sun4u vmlinux kernel size 1.4 MB boots fine
a 2.6.2-rc2 vmlinux lernel size 3.8 doesn't boot, as reported earlier.
booting that kernel with "-p" gives:
Remapping the kernel... done.
On node 0 totalpages: 15846
I did not however have to use debian-rescue to rerun "silo -f" again.
All my old kernels work without hassle. All in all a fine job.
Thanks for the effort Ben , now we can use the shiny new kernel-build
system, just like the normal people :)
I used the silo-loaders tar-ball for second.b.
Andreas
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (7 preceding siblings ...)
2004-01-29 22:20 ` dree
@ 2004-01-29 22:58 ` Otto Solares
2004-01-30 0:22 ` Erlend Aasland
` (25 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Otto Solares @ 2004-01-29 22:58 UTC (permalink / raw)
To: sparclinux
On Thu, Jan 29, 2004 at 04:01:03PM -0500, Ben Collins wrote:
> Read the fucking email. I want people to test the _old_ smaller kernels
> _first_. I would rather the larger kernels be broken than for the new
> SILO to not work with the older kernels.
Sorry, i think the point was test larger kernels. Anyway
my older kernels boots properly with the new second.b. Newer
larger kernel 2.6.2-rc2-bk3 4M boots perfectly too on 3
different machines.
FYI compiling silo-1.4.3 from source:
gcc -m32 -Os -Wall -I. -I../include -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000 -DLARGE_RELOC=0x380000 -c fs/ufs.c -o fs/ufs.o
In file included from /usr/include/linux/fs.h:16,
from /usr/include/linux/ufs_fs.h:34,
from fs/ufs.c:36:
/usr/include/linux/list.h:594:2: warning: #warning "don't include kernel headers in userspace"
In file included from /usr/include/linux/fs.h:20,
from /usr/include/linux/ufs_fs.h:34,
from fs/ufs.c:36:
/usr/include/linux/radix-tree.h: In function `radix_tree_preload_end':
/usr/include/linux/radix-tree.h:54: error: invalid type argument of `->'
/usr/include/linux/radix-tree.h:54: error: `TIF_NEED_RESCHED' undeclared (first use in this function)
/usr/include/linux/radix-tree.h:54: error: (Each undeclared identifier is reported only once
/usr/include/linux/radix-tree.h:54: error: for each function it appears in.)
make: *** [fs/ufs.o] Error 1
-solca
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (8 preceding siblings ...)
2004-01-29 22:58 ` Otto Solares
@ 2004-01-30 0:22 ` Erlend Aasland
2004-01-30 10:37 ` Christian
` (24 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Erlend Aasland @ 2004-01-30 0:22 UTC (permalink / raw)
To: sparclinux
Hi,
Using an Ultra10, silo-1.4.3 (compiled w/gcc-3.2.3) I can successfully
boot kernel 2.4.23 and 2.4.24 (both 2.9MB).
Regards,
Erlend Aasland
On 01/29/04 13:29, Ben Collins wrote:
> I've tested and fixed initrd support for sparc64, so that's safe.
>
> I've also cleaned up some things. Upon further testing, I was able to
> boot a 6.8Meg image. Not sure why it didn't work the first time, but
> beware it may be flakey.
>
> I'm a little disappointed. I haven't gotten any feedback from people
> testing this new version. So either no one cares, or it works good and
> people don't want to waste their time sending "worked for me" emails :)
>
> Usual place: http://www.sparc-boot.org/pub/silo/
>
> --
> Debian - http://www.debian.org/
> Linux 1394 - http://www.linux1394.org/
> Subversion - http://subversion.tigris.org/
> WatchGuard - http://www.watchguard.com/
> -
> To unsubscribe from this list: send the line "unsubscribe sparclinux" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (9 preceding siblings ...)
2004-01-30 0:22 ` Erlend Aasland
@ 2004-01-30 10:37 ` Christian
2004-01-30 17:04 ` Ben Collins
` (23 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Christian @ 2004-01-30 10:37 UTC (permalink / raw)
To: sparclinux
[-- Attachment #1: Type: text/plain, Size: 473 bytes --]
> I'm a little disappointed. I haven't gotten any feedback from people
> testing this new version. So either no one cares, or it works good and
> people don't want to waste their time sending "worked for me" emails :)
well, I get this (attached) on a Dual UE2, running debian/unstable, with
silo-1.4.3
(deb package) and linux-2.6.2-rc2 (3.5 MB).
On the other side, linux-2.4.23-rc4 (2.9 MB) boots fine. both kernels booted
nicely with silo-1.3.2.
cheers.
Christian
[-- Attachment #2: dmesg.txt --]
[-- Type: text/plain, Size: 6845 bytes --]
Jan 30 11:10:38 eclipse kernel: kjournald starting. Commit interval 5 seconds
Jan 30 11:10:38 eclipse kernel: EXT3-fs: mounted filesystem with ordered data mode.
Jan 30 11:10:38 eclipse kernel: VFS: Mounted root (ext3 filesystem) readonly.
Jan 30 11:10:38 eclipse kernel: Badness in map_area_pte at mm/vmalloc.c:101
Jan 30 11:10:38 eclipse kernel: [000000000048f85c] [000000000048fe8c] [0000000000493920] [0000000000411174] [0000000000010d3c]
Jan 30 11:10:38 eclipse kernel: Badness in map_area_pte at mm/vmalloc.c:101
Jan 30 11:10:38 eclipse kernel: [000000000048f85c] [000000000048fe8c] [0000000000493920] [0000000000411174] [0000000000010d3c]
Jan 30 11:10:38 eclipse kernel: Badness in map_area_pte at mm/vmalloc.c:101
Jan 30 11:10:38 eclipse kernel: [000000000048f85c] [000000000048fe8c] [0000000000493920] [0000000000411174] [0000000000010d3c]
Jan 30 11:10:38 eclipse kernel: Badness in map_area_pte at mm/vmalloc.c:101
Jan 30 11:10:38 eclipse kernel: [000000000048f85c] [000000000048fe8c] [0000000000493920] [0000000000411174] [0000000000010d3c]
Jan 30 11:10:38 eclipse kernel: Badness in map_area_pte at mm/vmalloc.c:101
Jan 30 11:10:38 eclipse kernel: [000000000048f85c] [000000000048fe8c] [0000000000493920] [0000000000411174] [0000000000010d3c]
Jan 30 11:10:38 eclipse kernel: Badness in map_area_pte at mm/vmalloc.c:101
Jan 30 11:10:38 eclipse kernel: [000000000048f85c] [000000000048fe8c] [0000000000493920] [0000000000411174] [0000000000010d3c]
Jan 30 11:10:38 eclipse kernel: Badness in map_area_pte at mm/vmalloc.c:101
Jan 30 11:10:38 eclipse kernel: [000000000048f85c] [000000000048fe8c] [0000000000493920] [0000000000411174] [0000000000010d3c]
Jan 30 11:10:38 eclipse kernel: Badness in map_area_pte at mm/vmalloc.c:101
Jan 30 11:10:38 eclipse kernel: [000000000048f85c] [000000000048fe8c] [0000000000493920] [0000000000411174] [0000000000010d3c]
Jan 30 11:10:38 eclipse kernel: Badness in map_area_pte at mm/vmalloc.c:101
Jan 30 11:10:38 eclipse kernel: [000000000048f85c] [000000000048fe8c] [0000000000493920] [0000000000411174] [0000000000010d3c]
Jan 30 11:10:38 eclipse kernel: Badness in map_area_pte at mm/vmalloc.c:101
Jan 30 11:10:38 eclipse kernel: [000000000048f85c] [000000000048fe8c] [0000000000493920] [0000000000411174] [0000000000010d3c]
Jan 30 11:10:38 eclipse kernel: Badness in map_area_pte at mm/vmalloc.c:101
Jan 30 11:10:38 eclipse kernel: [000000000048f85c] [000000000048fe8c] [0000000000493920] [0000000000411174] [0000000000010d3c]
Jan 30 11:10:38 eclipse kernel: Badness in map_area_pte at mm/vmalloc.c:101
Jan 30 11:10:38 eclipse kernel: [000000000048f85c] [000000000048fe8c] [0000000000493920] [0000000000411174] [0000000000010d3c]
Jan 30 11:10:38 eclipse kernel: Badness in map_area_pte at mm/vmalloc.c:101
Jan 30 11:10:38 eclipse kernel: [000000000048f85c] [000000000048fe8c] [0000000000493920] [0000000000411174] [0000000000010d3c]
Jan 30 11:10:38 eclipse kernel: Badness in map_area_pte at mm/vmalloc.c:101
Jan 30 11:10:38 eclipse kernel: [000000000048f85c] [000000000048fe8c] [0000000000493920] [0000000000411174] [0000000000010d3c]
Jan 30 11:10:38 eclipse kernel: Badness in map_area_pte at mm/vmalloc.c:101
Jan 30 11:10:38 eclipse kernel: [000000000048f85c] [000000000048fe8c] [0000000000493920] [0000000000411174] [0000000000010d3c]
Jan 30 11:10:38 eclipse kernel: Badness in map_area_pte at mm/vmalloc.c:101
Jan 30 11:10:38 eclipse kernel: [000000000048f85c] [000000000048fe8c] [0000000000493920] [0000000000411174] [0000000000010d3c]
Jan 30 11:10:38 eclipse kernel: Badness in map_area_pte at mm/vmalloc.c:101
Jan 30 11:10:38 eclipse kernel: [000000000048f85c] [000000000048fe8c] [0000000000493920] [0000000000411174] [0000000000010d3c]
Jan 30 11:10:38 eclipse kernel: Badness in map_area_pte at mm/vmalloc.c:101
Jan 30 11:10:38 eclipse kernel: [000000000048f85c] [000000000048fe8c] [0000000000493920] [0000000000411174] [0000000000010d3c]
Jan 30 11:10:38 eclipse kernel: Badness in map_area_pte at mm/vmalloc.c:101
Jan 30 11:10:38 eclipse kernel: [000000000048f85c] [000000000048fe8c] [0000000000493920] [0000000000411174] [0000000000010d3c]
Jan 30 11:10:38 eclipse kernel: Badness in map_area_pte at mm/vmalloc.c:101
Jan 30 11:10:38 eclipse kernel: [000000000048f85c] [000000000048fe8c] [0000000000493920] [0000000000411174] [0000000000010d3c]
Jan 30 11:10:38 eclipse kernel: TRAPLOG: Error at trap level 0x2, dumping track stack.
Jan 30 11:10:38 eclipse kernel: TRAPLOG: Trap level 1 TSTATE[0000004411009606] TPC[000000000048f678] TNPC[000000000048f67c] TT[c0]
Jan 30 11:10:38 eclipse kernel: TRAPLOG: Trap level 2 TSTATE[0000004411009505] TPC[0000000000409828] TNPC[000000000040982c] TT[32]
Jan 30 11:10:38 eclipse kernel: TRAPLOG: Trap level 3 TSTATE[0000004411009505] TPC[000000000040d904] TNPC[000000000040d908] TT[68]
Jan 30 11:10:38 eclipse kernel: TRAPLOG: Trap level 4 TSTATE[0000009911049405] TPC[0000000000408d20] TNPC[0000000000408d24] TT[68]
Jan 30 11:10:38 eclipse kernel: \|/ ____ \|/
Jan 30 11:10:38 eclipse kernel: "@'/ .. \`@"
Jan 30 11:10:38 eclipse kernel: /_| \__/ |_\
Jan 30 11:10:38 eclipse kernel: \__U_/
Jan 30 11:10:38 eclipse kernel: swapon(34): TL1: Data Access Exception [#1]
Jan 30 11:10:38 eclipse kernel: TSTATE: 0000004411009505 TPC: 0000000000409828 TNPC: 000000000040982c Y: 00000000 Not tainted
Jan 30 11:10:38 eclipse kernel: TPC: <tl0_f0n+0x28/0x80>
Jan 30 11:10:38 eclipse kernel: g0: 0000000000000065 g1: fffff800479bf2e8 g2: 0000000000000000 g3: 0000000000000000
Jan 30 11:10:38 eclipse kernel: g4: fffff800478186a0 g5: 0000000000000000 g6: fffff80047478000 g7: 0000000000000000
Jan 30 11:10:38 eclipse kernel: o0: fffffc045907f8a8 o1: 000000000002a000 o2: fffff80000f4b528 o3: 8000000000000fb6
Jan 30 11:10:38 eclipse kernel: o4: fffff8004747bdb8 o5: 0000000000000000 sp: fffff8004747b381 ret_pc: 000000000048f6d8
Jan 30 11:10:38 eclipse kernel: RPC: <map_area_pmd+0x58/0xa0>
Jan 30 11:10:38 eclipse kernel: l0: 0000000000800000 l1: 000000000064e800 l2: ffffffffff800000 l3: fffff8004747bbb0
Jan 30 11:10:38 eclipse kernel: l4: fffff80047f007f0 l5: fffff80047f00830 l6: 0000000000000000 l7: 0000000000000000
Jan 30 11:10:38 eclipse kernel: i0: ffffff000d008a04 i1: 0000000140000000 i2: ffffffffffffffff i3: 0000000003ffffff
Jan 30 11:10:38 eclipse kernel: i4: fffff80000f7b220 i5: 00000000ffff9078 i6: fffff8004747ae41 i7: 000000000045e1f4
Jan 30 11:10:38 eclipse kernel: I7: <__mod_timer+0x254/0x380>
Jan 30 11:10:38 eclipse kernel: Instruction DUMP: ee5ba837 f05ba83f f25ba847 <f45ba84f> f65ba857 f85ba85f fa5ba867 fc5ba86f fe5ba877
Jan 30 11:10:38 eclipse kernel: note: swapon[34] exited with preempt_count 1
Jan 30 11:10:38 eclipse kernel: EXT3 FS on sda1, internal journal
Jan 30 11:10:38 eclipse kernel: kjournald starting. Commit interval 5 seconds
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (10 preceding siblings ...)
2004-01-30 10:37 ` Christian
@ 2004-01-30 17:04 ` Ben Collins
2004-01-30 17:37 ` Ben Collins
` (22 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Ben Collins @ 2004-01-30 17:04 UTC (permalink / raw)
To: sparclinux
On Fri, Jan 30, 2004 at 11:37:32AM +0100, Christian Guggenberger wrote:
> >I'm a little disappointed. I haven't gotten any feedback from people
> >testing this new version. So either no one cares, or it works good and
> >people don't want to waste their time sending "worked for me" emails :)
>
> well, I get this (attached) on a Dual UE2, running debian/unstable, with
> silo-1.4.3
> (deb package) and linux-2.6.2-rc2 (3.5 MB).
> On the other side, linux-2.4.23-rc4 (2.9 MB) boots fine. both kernels
> booted nicely with silo-1.3.2.
I don't except 2.6.2-rc2 to work at all. Use rc1, or wait for later than
rc2.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (11 preceding siblings ...)
2004-01-30 17:04 ` Ben Collins
@ 2004-01-30 17:37 ` Ben Collins
2004-01-30 17:39 ` Meelis Roos
` (21 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Ben Collins @ 2004-01-30 17:37 UTC (permalink / raw)
To: sparclinux
On Fri, Jan 30, 2004 at 07:39:52PM +0200, Meelis Roos wrote:
> BC> I'm a little disappointed. I haven't gotten any feedback from people
> BC> testing this new version. So either no one cares, or it works good and
> BC> people don't want to waste their time sending "worked for me" emails :)
>
> Fails here.
>
> I upgraded my sparc32 unstable today (SS5-170, 256M RAM). It has some
> 2.4.21 kernel, probably the default debian kernel, as the default. With
> your previous 1.4.1 Debian package, it booted fine. Now with SILO
> Version 1.4.3, I get
> Uncompressing image...
> Loaded kernel version 2.4.21
> Data Access Exception
> ok
>
> Tried also handcompiled 2.4.21+patches (also worked before) and old
> 2.2.20, still Data Access Exception.
>
> I'm booting from disk1 if this matters (probably not).
So 1.4.1 worked, and 1.4.3 didn't? Is the 1.4.3 compiled by you, or also
the debian package?
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (12 preceding siblings ...)
2004-01-30 17:37 ` Ben Collins
@ 2004-01-30 17:39 ` Meelis Roos
2004-01-30 17:46 ` Meelis Roos
` (20 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Meelis Roos @ 2004-01-30 17:39 UTC (permalink / raw)
To: sparclinux
BC> I'm a little disappointed. I haven't gotten any feedback from people
BC> testing this new version. So either no one cares, or it works good and
BC> people don't want to waste their time sending "worked for me" emails :)
Fails here.
I upgraded my sparc32 unstable today (SS5-170, 256M RAM). It has some
2.4.21 kernel, probably the default debian kernel, as the default. With
your previous 1.4.1 Debian package, it booted fine. Now with SILO
Version 1.4.3, I get
Uncompressing image...
Loaded kernel version 2.4.21
Data Access Exception
ok
Tried also handcompiled 2.4.21+patches (also worked before) and old
2.2.20, still Data Access Exception.
I'm booting from disk1 if this matters (probably not).
Now to netbooting...
--
Meelis Roos (mroos@linux.ee)
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (13 preceding siblings ...)
2004-01-30 17:39 ` Meelis Roos
@ 2004-01-30 17:46 ` Meelis Roos
2004-01-30 17:48 ` Ben Collins
` (19 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Meelis Roos @ 2004-01-30 17:46 UTC (permalink / raw)
To: sparclinux
> So 1.4.1 worked, and 1.4.3 didn't? Is the 1.4.3 compiled by you, or also
> the debian package?
Debian package.
I'm 95% sure that I actually tested the 1.4.1 booting - I turned the
computer on today and it booted and worked. I did dist-upgrade a day or
two ago and I seem to remember it telling me about installing new SILO,
and I remember seeing 1.4.1 being in upgrade list. So if it installed
correctly, it should have been 1.4.1 package.
--
Meelis Roos (mroos@linux.ee)
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (14 preceding siblings ...)
2004-01-30 17:46 ` Meelis Roos
@ 2004-01-30 17:48 ` Ben Collins
2004-01-30 18:19 ` Ben Collins
` (18 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Ben Collins @ 2004-01-30 17:48 UTC (permalink / raw)
To: sparclinux
On Fri, Jan 30, 2004 at 07:46:07PM +0200, Meelis Roos wrote:
> > So 1.4.1 worked, and 1.4.3 didn't? Is the 1.4.3 compiled by you, or also
> > the debian package?
>
> Debian package.
>
> I'm 95% sure that I actually tested the 1.4.1 booting - I turned the
> computer on today and it booted and worked. I did dist-upgrade a day or
> two ago and I seem to remember it telling me about installing new SILO,
> and I remember seeing 1.4.1 being in upgrade list. So if it installed
> correctly, it should have been 1.4.1 package.
Actually I uploaded 1.4.0, 1.4.1, 1.4.2 and 1.4.3 all yesterday. So
there's no way possible you had 1.4.1...maybe it was 1.3.1 :)
Ok, next time you can, when you get the problem, type ".registers" at
the ok prompt, and send me the output please? Also do:
ok> cd /memory
ok> .properties
(send this output)
ok> cd /virtual-memory
ok> .properties
(send this aswell)
And also send me the output of "dump-itlb".
Thanks!
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (15 preceding siblings ...)
2004-01-30 17:48 ` Ben Collins
@ 2004-01-30 18:19 ` Ben Collins
2004-01-30 18:20 ` Meelis Roos
` (17 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Ben Collins @ 2004-01-30 18:19 UTC (permalink / raw)
To: sparclinux
> Uncompressing image...
> Loaded kernel version 2.4.21
> Data Access Exception
Is there anything before the "Uncompressing image..." ?
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (16 preceding siblings ...)
2004-01-30 18:19 ` Ben Collins
@ 2004-01-30 18:20 ` Meelis Roos
2004-01-30 18:30 ` Meelis Roos
` (16 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Meelis Roos @ 2004-01-30 18:20 UTC (permalink / raw)
To: sparclinux
> Actually I uploaded 1.4.0, 1.4.1, 1.4.2 and 1.4.3 all yesterday. So
> there's no way possible you had 1.4.1...maybe it was 1.3.1 :)
Hmm, not sure. I only remember exactly that I did update yesterday or
the day before and it upgraded lilo.
> Ok, next time you can, when you get the problem, type ".registers" at
> the ok prompt, and send me the output please? Also do:
Hand copied because I have my serial gender changer is use - so free
format (hopefully no typos):
%g0 0
%g1 2a3c00
%g2 ffefa398
%g3 20
%g4 2a5000
%g5 0
%g6 0
%g7 ffffffff
PC 286748
nPC 28674c
Y 1c00000
PSR 4801fe6
WIM 80
TBR ffeff090
> ok> cd /memory
> ok> .properties
.attributes actually - OBP 2.29 here.
reg 00000000 00000000 02000000
00000000 02000000 02000000
00000000 04000000 02000000
00000000 06000000 02000000
00000000 08000000 02000000
00000000 0a000000 02000000
00000000 0c000000 02000000
00000000 0e000000 02000000
available 00000000 00000000 0ffa1000
name memory
> ok> cd /virtual-memory
> ok> .properties
available 00000000 fff00000 00100000
00000000 fef00000 00e00000
00000000 00000000 fe400000
00000000 ffed3000 00010000
00000000 ffe15000 000b8000
00000000 ffd00000 00008000
00000000 fe400000 00a00000
reg 00000000 00000000 80000000
00000000 80000000 80000000
name virtual-memory
> And also send me the output of "dump-itlb".
dump-itlb ?
(what's the corresponding word in older obp?)
--
Meelis Roos (mroos@linux.ee)
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (17 preceding siblings ...)
2004-01-30 18:20 ` Meelis Roos
@ 2004-01-30 18:30 ` Meelis Roos
2004-01-30 18:40 ` Ben Collins
` (15 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Meelis Roos @ 2004-01-30 18:30 UTC (permalink / raw)
To: sparclinux
> Is there anything before the "Uncompressing image..." ?
Rebooting with command: disk1
Boot device: /iommu/sbus/espdma@5,8400000/esp@5,8800000/sd@1,0 File and args:
SILO Version 1.4.3
boot:
Uncompressing image...
Loaded kernel version 2.4.21
Data Access Exception
Type help for more information
ok
(this time it also displayed the help hint)
--
Meelis Roos (mroos@linux.ee)
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (18 preceding siblings ...)
2004-01-30 18:30 ` Meelis Roos
@ 2004-01-30 18:40 ` Ben Collins
2004-01-30 18:49 ` Meelis Roos
` (14 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Ben Collins @ 2004-01-30 18:40 UTC (permalink / raw)
To: sparclinux
[-- Attachment #1: Type: text/plain, Size: 775 bytes --]
On Fri, Jan 30, 2004 at 08:30:23PM +0200, Meelis Roos wrote:
> > Is there anything before the "Uncompressing image..." ?
>
> Rebooting with command: disk1
> Boot device: /iommu/sbus/espdma@5,8400000/esp@5,8800000/sd@1,0 File and args:
> SILO Version 1.4.3
> boot:
> Uncompressing image...
> Loaded kernel version 2.4.21
> Data Access Exception
> Type help for more information
> ok
Ok, your system isn't able to allocate the needed memory (must be an OBP
2.x thing). One thing you might try is upgrading your OBP, but in the
mean time, give the attached second.b a try (put it in /boot/ and run
"silo -f").
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
[-- Attachment #2: second.b --]
[-- Type: application/octet-stream, Size: 60928 bytes --]
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (19 preceding siblings ...)
2004-01-30 18:40 ` Ben Collins
@ 2004-01-30 18:49 ` Meelis Roos
2004-01-30 19:17 ` Meelis Roos
` (13 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Meelis Roos @ 2004-01-30 18:49 UTC (permalink / raw)
To: sparclinux
> Ok, your system isn't able to allocate the needed memory (must be an OBP
> 2.x thing). One thing you might try is upgrading your OBP, but in the
> mean time, give the attached second.b a try (put it in /boot/ and run
> "silo -f").
I will be able to do it tomorrow since my RARP boot server is in use in
another network currently.
--
Meelis Roos (mroos@ut.ee) http://www.cs.ut.ee/~mroos/
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (20 preceding siblings ...)
2004-01-30 18:49 ` Meelis Roos
@ 2004-01-30 19:17 ` Meelis Roos
2004-01-30 19:21 ` Ben Collins
` (12 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Meelis Roos @ 2004-01-30 19:17 UTC (permalink / raw)
To: sparclinux
> Ok, your system isn't able to allocate the needed memory (must be an OBP
> 2.x thing). One thing you might try is upgrading your OBP, but in the
> mean time, give the attached second.b a try (put it in /boot/ and run
> "silo -f").
OK, found out that the old RARP server can not come back any time soon
and installed another netboot server.
Still Data Access Exception. This time PC(6760 and nPC(6764 but
other regs are the same as before.
--
Meelis Roos (mroos@linux.ee)
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (21 preceding siblings ...)
2004-01-30 19:17 ` Meelis Roos
@ 2004-01-30 19:21 ` Ben Collins
2004-01-30 19:30 ` Meelis Roos
` (11 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Ben Collins @ 2004-01-30 19:21 UTC (permalink / raw)
To: sparclinux
On Fri, Jan 30, 2004 at 09:17:37PM +0200, Meelis Roos wrote:
> > Ok, your system isn't able to allocate the needed memory (must be an OBP
> > 2.x thing). One thing you might try is upgrading your OBP, but in the
> > mean time, give the attached second.b a try (put it in /boot/ and run
> > "silo -f").
>
> OK, found out that the old RARP server can not come back any time soon
> and installed another netboot server.
>
> Still Data Access Exception. This time PC(6760 and nPC(6764 but
> other regs are the same as before.
Damn, I just realised you are doing this on sparc32.
Anyway, I can't see what would be causing this problem. I didn't really
touch anything with sparc32.
Can you get the silo source and do some compiles for me? Would be easier
than me sending you loaders and waiting. I need you to check the address
image_base and ret_offset in the function bootmain() in the file
second/main.c. Just add some printf's.
Also, you can try commenting out the call to memory_release() at the
bottom of that same file/function.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (22 preceding siblings ...)
2004-01-30 19:21 ` Ben Collins
@ 2004-01-30 19:30 ` Meelis Roos
2004-01-30 19:32 ` Ciaran McCreesh
` (10 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Meelis Roos @ 2004-01-30 19:30 UTC (permalink / raw)
To: sparclinux
> Damn, I just realised you are doing this on sparc32.
Yes. I probably should have made it more clear than just mentioning SS5.
> Can you get the silo source and do some compiles for me? Would be easier
> than me sending you loaders and waiting. I need you to check the address
> image_base and ret_offset in the function bootmain() in the file
> second/main.c. Just add some printf's.
>
> Also, you can try commenting out the call to memory_release() at the
> bottom of that same file/function.
Yes, but it is getting late here, I will try it tomorrow if anything
doesn't disturb me.
--
Meelis Roos (mroos@linux.ee)
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (23 preceding siblings ...)
2004-01-30 19:30 ` Meelis Roos
@ 2004-01-30 19:32 ` Ciaran McCreesh
2004-01-30 19:43 ` Ben Collins
` (9 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Ciaran McCreesh @ 2004-01-30 19:32 UTC (permalink / raw)
To: sparclinux
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
On Thu, 29 Jan 2004 13:29:54 -0500 Ben Collins <bcollins@debian.org>
wrote:
| I'm a little disappointed. I haven't gotten any feedback from people
| testing this new version. So either no one cares, or it works good and
| people don't want to waste their time sending "worked for me" emails
| :)
1.4.3 works for me with an Ultra 10 and an Ultra 1 with various 2.6.1
kernels.
As expected, 2.6.2-rc2 (+ Gentoo patches) refuses to boot. On an Ultra
10, OBP tells me the following:
| Allocated 8 Megs of memory at 0x40000000 for kernel
| Loaded kernel version 2.6.2
|
| Remapping the kernel... done.
and then locks up completely.
On an Ultra 1, it panics at boot (I can make a serial cable if you need
the full text) with init(1): TL1: Data Access Exception [#1].
Sparc32 seems to be totally broken. I'll send debug information once my
soldering iron's warmed up :)
Gentoo people, 1.4.3 is in portage but hard masked for now. Please test
if you're brave...
--
Ciaran McCreesh
Mail: ciaranm at gentoo.org
Web: http://dev.gentoo.org/~ciaranm
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (24 preceding siblings ...)
2004-01-30 19:32 ` Ciaran McCreesh
@ 2004-01-30 19:43 ` Ben Collins
2004-01-30 19:47 ` Meelis Roos
` (8 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Ben Collins @ 2004-01-30 19:43 UTC (permalink / raw)
To: sparclinux
On Fri, Jan 30, 2004 at 09:47:13PM +0200, Meelis Roos wrote:
> > Can you get the silo source and do some compiles for me? Would be easier
> > than me sending you loaders and waiting. I need you to check the address
> > image_base and ret_offset in the function bootmain() in the file
> > second/main.c. Just add some printf's.
>
> What parts of the newly compiled silo do I need to install? Only
> second.b and then do silo -f?
Yes.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (25 preceding siblings ...)
2004-01-30 19:43 ` Ben Collins
@ 2004-01-30 19:47 ` Meelis Roos
2004-01-30 19:52 ` Christian
` (7 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Meelis Roos @ 2004-01-30 19:47 UTC (permalink / raw)
To: sparclinux
> Can you get the silo source and do some compiles for me? Would be easier
> than me sending you loaders and waiting. I need you to check the address
> image_base and ret_offset in the function bootmain() in the file
> second/main.c. Just add some printf's.
What parts of the newly compiled silo do I need to install? Only
second.b and then do silo -f?
--
Meelis Roos (mroos@linux.ee)
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (26 preceding siblings ...)
2004-01-30 19:47 ` Meelis Roos
@ 2004-01-30 19:52 ` Christian
2004-01-30 19:59 ` Meelis Roos
` (6 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Christian @ 2004-01-30 19:52 UTC (permalink / raw)
To: sparclinux
On Fri, Jan 30, 2004 at 12:04:51PM -0500, Ben Collins wrote:
> On Fri, Jan 30, 2004 at 11:37:32AM +0100, Christian Guggenberger wrote:
> > >I'm a little disappointed. I haven't gotten any feedback from people
> > >testing this new version. So either no one cares, or it works good and
> > >people don't want to waste their time sending "worked for me" emails :)
> >
> > well, I get this (attached) on a Dual UE2, running debian/unstable, with
> > silo-1.4.3
> > (deb package) and linux-2.6.2-rc2 (3.5 MB).
> > On the other side, linux-2.4.23-rc4 (2.9 MB) boots fine. both kernels
> > booted nicely with silo-1.3.2.
>
>
> I don't except 2.6.2-rc2 to work at all. Use rc1, or wait for later than
> rc2.
>
thanks for the hint. Indeed, 2.6.2-rc1 (3.5 MB) boots fine with silo-1.4.3
cheers.
Christian
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (27 preceding siblings ...)
2004-01-30 19:52 ` Christian
@ 2004-01-30 19:59 ` Meelis Roos
2004-01-30 20:06 ` Ben Collins
` (5 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Meelis Roos @ 2004-01-30 19:59 UTC (permalink / raw)
To: sparclinux
> Can you get the silo source and do some compiles for me? Would be easier
> than me sending you loaders and waiting. I need you to check the address
> image_base and ret_offset in the function bootmain() in the file
> second/main.c. Just add some printf's.
It doesn't reach the end of the function.
> Also, you can try commenting out the call to memory_release() at the
> bottom of that same file/function.
Removing this call doesn't change anything.
Will continue to narrow it down.
--
Meelis Roos (mroos@linux.ee)
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (28 preceding siblings ...)
2004-01-30 19:59 ` Meelis Roos
@ 2004-01-30 20:06 ` Ben Collins
2004-01-30 20:19 ` Ben Collins
` (4 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Ben Collins @ 2004-01-30 20:06 UTC (permalink / raw)
To: sparclinux
On Fri, Jan 30, 2004 at 09:59:09PM +0200, Meelis Roos wrote:
> > Can you get the silo source and do some compiles for me? Would be easier
> > than me sending you loaders and waiting. I need you to check the address
> > image_base and ret_offset in the function bootmain() in the file
> > second/main.c. Just add some printf's.
>
> It doesn't reach the end of the function.
>
> > Also, you can try commenting out the call to memory_release() at the
> > bottom of that same file/function.
>
> Removing this call doesn't change anything.
>
> Will continue to narrow it down.
Look for where it sets the value for the kernel_params pointer. Add a
line after it sets it:
printf("kernel_params=%x\n", kernel_params);
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (29 preceding siblings ...)
2004-01-30 20:06 ` Ben Collins
@ 2004-01-30 20:19 ` Ben Collins
2004-01-30 20:35 ` Meelis Roos
` (3 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Ben Collins @ 2004-01-30 20:19 UTC (permalink / raw)
To: sparclinux
I just uploaded SILO 1.4.4, which fixes this problem.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (30 preceding siblings ...)
2004-01-30 20:19 ` Ben Collins
@ 2004-01-30 20:35 ` Meelis Roos
2004-01-30 20:55 ` Ciaran McCreesh
` (2 subsequent siblings)
34 siblings, 0 replies; 36+ messages in thread
From: Meelis Roos @ 2004-01-30 20:35 UTC (permalink / raw)
To: sparclinux
> Can you get the silo source and do some compiles for me? Would be easier
> than me sending you loaders and waiting. I need you to check the address
> image_base and ret_offset in the function bootmain() in the file
> second/main.c. Just add some printf's.
before load_file: image_base@00, ret_offset=0
before parse_executable: same.
after parse_executable: same.
This is the load_file+parse_executable in the "else" block, just before
kernel_params is assigned 0 and if(solaris).
kernel_params pointer is FFC00000.
Data Access Exception occurs after this conditional assign to
kernel_params.
Putting in some checkpoints shows that the data access exception comes
from the block
if (kernel_params( {
...
}
I saw the announcement about 1.4.4 but will try it tomorrow - it's
really getting too late.
--
Meelis Roos (mroos@ut.ee) http://www.cs.ut.ee/~mroos/
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (31 preceding siblings ...)
2004-01-30 20:35 ` Meelis Roos
@ 2004-01-30 20:55 ` Ciaran McCreesh
2004-01-31 8:34 ` Ralph Mitchell
2004-01-31 13:14 ` Meelis Roos
34 siblings, 0 replies; 36+ messages in thread
From: Ciaran McCreesh @ 2004-01-30 20:55 UTC (permalink / raw)
To: sparclinux
[-- Attachment #1: Type: text/plain, Size: 565 bytes --]
On Fri, 30 Jan 2004 15:19:47 -0500 Ben Collins <bcollins@debian.org>
wrote:
| I just uploaded SILO 1.4.4, which fixes this problem.
This one worksforme on a sparcstation 5. It also boots a Gentoo-patched
2.6.2_rc2 properly, so I guess it's just sparc64 broken there.
ciaranm@sundrop ciaranm 0 $ qpkg -v -I silo
sys-boot/silo-1.4.4 *
ciaranm@sundrop ciaranm 0 $ uname -a
Linux sundrop 2.6.2-rc2-sparc #1 Thu Jan 29 18:41:07 GMT 2004 sparc
sun4m Fujitsu MB86904 GNU/Linux
--
Ciaran McCreesh
Mail: ciaranm at gentoo.org
Web: http://dev.gentoo.org/~ciaranm
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (32 preceding siblings ...)
2004-01-30 20:55 ` Ciaran McCreesh
@ 2004-01-31 8:34 ` Ralph Mitchell
2004-01-31 13:14 ` Meelis Roos
34 siblings, 0 replies; 36+ messages in thread
From: Ralph Mitchell @ 2004-01-31 8:34 UTC (permalink / raw)
To: sparclinux
Ben Collins wrote:
>I just uploaded SILO 1.4.4, which fixes this problem.
>
>
Works with an old Sparc20/linux-2.4.24:
bbsnp03 root # uname -a
Linux bbsnp03 2.4.24-sparc-r1 #2 Wed Jan 28 11:45:09 CST 2004 sparc
sun4m Texas Instruments, Inc. - SuperSparc-(II) GNU/Linux
Works with a 4-cpu E450/linux-2.6.0:
bbsnp02 root # uname -a
Linux bbsnp02 2.6.0-gentoo-r1 #1 SMP Sat Jan 3 01:37:00 CST 2004 sparc64
sun4u TI UltraSparc II (BlackBird) GNU/Linux
Thanks,
Ralph Mitchell
^ permalink raw reply [flat|nested] 36+ messages in thread* Re: SILO 1.4.2 released
2004-01-29 18:29 SILO 1.4.2 released Ben Collins
` (33 preceding siblings ...)
2004-01-31 8:34 ` Ralph Mitchell
@ 2004-01-31 13:14 ` Meelis Roos
34 siblings, 0 replies; 36+ messages in thread
From: Meelis Roos @ 2004-01-31 13:14 UTC (permalink / raw)
To: sparclinux
> I just uploaded SILO 1.4.4, which fixes this problem.
Confirmed, 1.4.4 works fine on my SS5-170 with 256M RAM and SS10MP
(2CPU) with 128M RAM. Thanks!
--
Meelis Roos (mroos@ut.ee) http://www.cs.ut.ee/~mroos/
^ permalink raw reply [flat|nested] 36+ messages in thread