headers
Bernd Sieker | 2 Jul 2004 08:45
Picon
Picon

Re: HyperSPARC w/2.0

On 01.07.04, 19:15:38, Sean Hafeez wrote:
> I have a quad HyperSPARC SS20. Any ETA on the release of the 2.0 for it?
> 
> Are the ISO of the snap shot of the beta that can be installed from? Or 
> is it 1.6.2 and CVSup?

As far as I know there are no official iso images, but regular
binary snapshots on ftp://releng.netbsd.org/pub/NetBSD-daily/netbsd-2-0/

> 
> Thanks!
> 

--

-- 
Bernd Sieker

NetBSD: To serve the power.
		-- Herb Peyerl
Permalink | Reply |
headers
Havard Eidnes | 2 Jul 2004 21:33
Picon

Re: HyperSPARC w/2.0

> > I have a quad HyperSPARC SS20. Any ETA on the release of the 2.0 for it?
> >
> > Are the ISO of the snap shot of the beta that can be installed from? Or
> > is it 1.6.2 and CVSup?
>
> As far as I know there are no official iso images, but regular
> binary snapshots on ftp://releng.netbsd.org/pub/NetBSD-daily/netbsd-2-0/

...and the latest for sparc64 at the moment is in

  ftp://releng.netbsd.org/pub/NetBSD-daily/netbsd-2-0/200406120000/sparc/

There is some hope that the next autobuild round will produce a
new set for sparc (there has been some intermediate failed builds
for sparc between then and now).

Regards,

- Håvard (a happy user of 2.0F in SMP config on a dual HyperSPARC SS20)
Permalink | Reply |
headers
Christian Corti | 3 Jul 2004 14:50
Picon
Picon
Favicon

Re: HyperSPARC w/2.0

On Fri, 2 Jul 2004, Havard Eidnes wrote:
> - Håvard (a happy user of 2.0F in SMP config on a dual HyperSPARC SS20)

Well, 2.0F still has severe memory leaks in the kernel so I have to reboot
my SMP SS10 once a day. Until this bug is located and fixed there cannot
be a final release. See my other postings on this list for this issue.

Christian Corti
Permalink | Reply |
headers
Bernd Sieker | 3 Jul 2004 17:35
Picon
Picon

Re: HyperSPARC w/2.0

On 03.07.04, 14:50:42, Christian Corti wrote:
> On Fri, 2 Jul 2004, Havard Eidnes wrote:
> > - H?vard (a happy user of 2.0F in SMP config on a dual HyperSPARC SS20)
> 
> Well, 2.0F still has severe memory leaks in the kernel so I have to reboot
> my SMP SS10 once a day. Until this bug is located and fixed there cannot
> be a final release. See my other postings on this list for this issue.

2.0F is not supposed to become a release anytime soon, it's the
bleeding edge development branch called "-current".

For a more stable environment, try 2.0_BETA, which will become 2.0
RSN. (cvs tag "netbsd-2-0")

I have an SS20-MP running with two CPUs on the 2.0 release branch,
and it does not leak (any more). Has been up for 19+ days now, and
"vmstat -m" shows a steady kernel memory usage of around 10 +-2
MB.

(Ok, so I only have SuperSPARC-II, and not HyperSPARC, but I should
mention that the two CPUs have different major revision SuperCache
Controllers (3.x vs. 4.x), which is officially discouraged when
running Solaris. Seems to work fine with NetBSD.)

The machine is doing IP-NAT for my DSL connection, ipfilter, and
is running a squid proxy for my LAN.

> 
> Christian Corti
>
(Continue reading)

Permalink | Reply |
headers
Christian Corti | 4 Jul 2004 12:27
Picon
Picon
Favicon

Re: HyperSPARC w/2.0

On Sat, 3 Jul 2004, Bernd Sieker wrote:
> 2.0F is not supposed to become a release anytime soon, it's the
> bleeding edge development branch called "-current".
> For a more stable environment, try 2.0_BETA, which will become 2.0
> RSN. (cvs tag "netbsd-2-0")

Seems I don't understand the NetBSD version numbering. 2.0F sounds much
less BETA than 2.0_BETA.

> I have an SS20-MP running with two CPUs on the 2.0 release branch,
> and it does not leak (any more). Has been up for 19+ days now, and
> "vmstat -m" shows a steady kernel memory usage of around 10 +-2
> MB.

I started with netbsd-2-0 a few months ago and it wasn't stable at all. It
had many errors with the SCSI bus and many memory leaks. That's why I
switched to -current. Nobody has ever anounced that the memory leaks were
fixed so I haven't switched "back" to BETA yet. I will try it next week.
One question: Will this break binaries compiled under 2.0F from pkgsrc? If
yes I'd like to see the memory leaks removed from -current instead of
switching to BETA.

Christian
Permalink | Reply |
headers
Bernd Sieker | 4 Jul 2004 13:05
Picon
Picon

Re: HyperSPARC w/2.0

On 04.07.04, 12:27:00, Christian Corti wrote:
> On Sat, 3 Jul 2004, Bernd Sieker wrote:
> > 2.0F is not supposed to become a release anytime soon, it's the
> > bleeding edge development branch called "-current".
> > For a more stable environment, try 2.0_BETA, which will become 2.0
> > RSN. (cvs tag "netbsd-2-0")
> 
> Seems I don't understand the NetBSD version numbering. 2.0F sounds much
> less BETA than 2.0_BETA.
> 

Take a look at this to clarify the naming scheme in NetBSD:

http://www.netbsd.org/Releases/release-map.html

> 
> I started with netbsd-2-0 a few months ago and it wasn't stable at all. It
> had many errors with the SCSI bus and many memory leaks. That's why I
> switched to -current. Nobody has ever anounced that the memory leaks were
> fixed so I haven't switched "back" to BETA yet. I will try it next week.
> One question: Will this break binaries compiled under 2.0F from pkgsrc? If

Probably yes, there were some API changes.

> yes I'd like to see the memory leaks removed from -current instead of
> switching to BETA.

Report them. See send-pr(1). Well, first check if they already have been
reported. But it is the nature of -current that sometimes new problems
are introduced whilst fixing others or adding new stuff.
(Continue reading)

Permalink | Reply |

Gmane