headers
Julian Coleman | 8 Feb 2007 20:18
Picon

Binary packages for NetBSD-3.0/sparc64 available

Hi,

The results of a pkgsrc bulk build of pkgsrc-2006Q4 on NetBSD-3.0/sparc64
have been uploaded and the packages are now available at:

  ftp://ftp.NetBSD.org/pub/pkgsrc/packages-2006Q4/NetBSD-3.0/sparc64/

and its mirrors.

The packages were built from sources updated on January 02, 2007.  5998
packages were sucessfully built (totalling 5.2GB).

The packages were built on a machine running NetBSD 3.0.2 and should be
useable on any sparc64 machine running NetBSD 3.0.x or NetBSD 3.x.

Now that the pkgsrc-2006Q3 and pkgsrc-2006Q4 packages are available, the
pkgsrc-2006Q2 NetBSD-3.0/sparc64 packages will be removed.

J

--

-- 
  My other computer also runs NetBSD    /        Sailing at Newbiggin
        http://www.netbsd.org/        /   http://www.newbigginsailingclub.org/
Permalink | Reply | 0 comments |
headers
nick thompson | 9 Feb 2007 04:22

Sun Blade 100

Hello all,
 I am wondering, how well supported is the blade 100?

thanks for any info

Nick

"All unix, all the time."

http://npt.ath.cx
Permalink | Reply | 5 comments |
headers
Jukka Salmi | 9 Feb 2007 15:39
Picon

Re: Sun Blade 100

nick thompson --> port-sparc64 (2007-02-08 21:22:18 -0600):
> I am wondering, how well supported is the blade 100?

Some weeks ago I installed -current on a SunBlade 100 and noticed
[1]problems related to more recent OBP versions; downgrading to 4.5.9
worked around these problems. But then I noticed data corruption while
running a GENERIC kernel - and found the following in the GENERIC
config file:

## Disable UDMA 4 which causes data corruption on the Acer Labs
## chipset on Sun Blade 100 and Netra X1 machines.
wd*     at atabus? drive ? flags 0x0000

Hmm, so this comment seems to be a demand note rather than a description
of the following device line... BTW: this [2]used to be `flags 0x0a00',
but was [3]reset [4]unintentionally. Shouldn't this be switched back?

However, IIRC downgrading to UDMA3 did not fix the problems either,
but I didn't even try to track this down because I was about to switch
to a Promise IDE controller. Until I noticed that pdcide(4) is not
supposed to work with NetBSD/sparc64 (see the man page)...

Regards, Jukka

[1] http://mail-index.netbsd.org/port-sparc64/2007/01/01/0000.html
[2] http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/sparc64/conf/GENERIC32.diff?r1=1.20&r2=1.21
[3] http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/sparc64/conf/GENERIC32.diff?r1=1.70&r2=1.71
[4] http://mail-index.netbsd.org/port-sparc64/2004/12/13/0007.html

--

--
(Continue reading)

Permalink | Reply | 4 comments |
headers
Julian Coleman | 9 Feb 2007 16:15
Picon

Re: Sun Blade 100

>                               But then I noticed data corruption while
> running a GENERIC kernel - and found the following in the GENERIC
> config file:
> 
> ## Disable UDMA 4 which causes data corruption on the Acer Labs
> ## chipset on Sun Blade 100 and Netra X1 machines.
> wd*     at atabus? drive ? flags 0x0000
> 
> However, IIRC downgrading to UDMA3 did not fix the problems either,

I've been running a Blade 100 for a while (currently 4.0_BETA) with:

  # Disable UDMA 5 & 6 for disks
  wd0     at atabus0 drive 0 flags 0x0c00
  wd1     at atabus1 drive 0 flags 0x0c00
  # Disable UDMA and DMA for CD
  cd0     at atapibus0 drive 1 flags 0x0ff0       # ATAPI CD-ROM drives

The controller/drives attach as:

  aceride0 at pci0 dev 13 function 0
  aceride0: Acer Labs M5229 UDMA IDE Controller (rev. 0xc3)
  aceride0: bus-master DMA support present
  aceride0: primary channel configured to native-PCI mode
  aceride0: using ivec 180c for native-PCI interrupt

  cd0 at atapibus0 drive 1: <LTN486S, , Y3S2> cdrom removable
  cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2 (Ultra/33)
  wd0 at atabus0 drive 0: <HDS728080PLAT20>
  wd0: drive supports 16-sector PIO transfers, LBA48 addressing
(Continue reading)

Permalink | Reply | 3 comments |
headers
Jukka Salmi | 9 Feb 2007 16:27
Picon

Re: Sun Blade 100

Julian Coleman --> port-sparc64 (2007-02-09 15:15:45 +0000):
> >                               But then I noticed data corruption while
> > running a GENERIC kernel - and found the following in the GENERIC
> > config file:
> > 
> > ## Disable UDMA 4 which causes data corruption on the Acer Labs
> > ## chipset on Sun Blade 100 and Netra X1 machines.
> > wd*     at atabus? drive ? flags 0x0000
> > 
> > However, IIRC downgrading to UDMA3 did not fix the problems either,
> 
> I've been running a Blade 100 for a while (currently 4.0_BETA) with:
> 
>   # Disable UDMA 5 & 6 for disks
>   wd0     at atabus0 drive 0 flags 0x0c00
>   wd1     at atabus1 drive 0 flags 0x0c00
>   # Disable UDMA and DMA for CD
>   cd0     at atapibus0 drive 1 flags 0x0ff0       # ATAPI CD-ROM drives
> 
> The controller/drives attach as:
[...]
>   raid0: RAID Level 1
>   raid0: Components: /dev/wd0a /dev/wd1a
>   raid0: Total Sectors: 160836352 (78533 MB)
> 
> I've not seen any data corruption problems.  I did have the hard drives
> running faster, but ended up with too many:
> 
>   wd1a: DMA error writing fsbn ...
>   wd1: soft error (corrected)
(Continue reading)

Permalink | Reply | 1 comment |
headers
Daniel Jared Dominguez | 9 Feb 2007 17:27
Picon
Favicon

Re: Sun Blade 100

If there is a developer who would like to work on these problems, I have
a spare Blade 100 which I can donate to the cause. I'd prefer having it
go to someone in the Boston area but could make arrangements for
shipping.

--Jared

--

-- 
Daniel Jared Dominguez
Zephyr: danjared <at> ATHENA.MIT.EDU
Jabber: danjared <at> mit.edu
Permalink | Reply | 0 comments |
headers
Michael Lorenz | 9 Feb 2007 19:16
Picon

Re: Sun Blade 100


Hello,

On Feb 9, 2007, at 10:15, Julian Coleman wrote:

>   wd0(aceride0:0:0): using PIO mode 4, Ultra-DMA mode 4 (Ultra/66) 
> (using DMA)
...
> messages.  I need to try them with 80-wire cables.

Err, anything faster than UDMA33 /requires/ 80-wire cables according to 
specs.

> I couldn't get the CD drive to work with DMA at all, so it's forced to 
> be
> PIO only.

I'd suggest some cable swapping, had similar issues on a beige G3 ( IDE 
DMA caused data corruption, PIO worked ) and swapping cables around 
cured it. First I thought the Heathrow IDE controller has some 
weirdness we don't work around yet but it turned out to be bad cables 
all over the place.

have fun
Michael
Permalink | Reply | 0 comments |
headers
Erik Bertelsen | 11 Feb 2007 14:25
Picon

Watchdog Reset and 4.99.10

With netbsd current as of today, my Ultra1 dies in the boot process
saying SIR Reset and Watchdog Reset.

The following is a copy of the console output:

Rebooting with command: boot
Boot device: disk  File and args:
NetBSD IEEE 1275 Bootblock
>> NetBSD/sparc64 OpenFirmware Boot, Revision 1.9
>> (erik <at> medja.h.erikb.net, Sat Jun 17 22:25:15 CEST 2006)
=0x8186d0
Loading netbsd: 1919000+99984+218344 [201288+124069]=0x89d8a8
sparc64_init(0xf005d9b0, 0xfffb5b30, 0x20, 0xf005d9b0, 0xf005d9b0)
sparc64_init: bmagic=44444230, bi=0x189d8b0
console is /sbus <at> 1f,0/zs <at> f,1100000:a
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
    2006, 2007
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 4.99.10 (UNIDATA) #7: Sun Feb 11 11:54:50 CET 2007
        erik <at> unidata.h.erikb.net:/home/NetBSD/obj.sparc64/sys/arch/sparc64/compile/UNIDATA
total memory = 320 MB
avail memory = 304 MB
bootpath: /sbus <at> 1f,0/SUNW,fas <at> e,8800000/sd <at> 0,0:a
mainbus0 (root): SUNW,Ultra-1: hostid 807c3a53
cpu0 at mainbus0: SUNW,UltraSPARC  <at>  167.008 MHz, UPA id 0
cpu0: 32K instruction (32 b/l), 16K data (32 b/l), 512K external (64 b/l)
timer0 at mainbus0 addr 0xfffc7c00 irq vectors 7f0 and 7f1
(Continue reading)

Permalink | Reply | 501 comments |
headers
Martin Husemann | 14 Feb 2007 10:45
Picon

Re: Watchdog Reset and 4.99.10

On Sun, Feb 11, 2007 at 02:25:32PM +0100, Erik Bertelsen wrote:
> With netbsd current as of today, my Ultra1 dies in the boot process
> saying SIR Reset and Watchdog Reset.

Yeah - I tested newlock2 sometime before the merge and it worked, but now
in -current something is wrong. Other machines just hang, or panic when
running a LOCKDEBUG kernel.

Martin
Permalink | Reply | 502 comments |
headers
Tobias Nygren | 17 Feb 2007 21:30
Picon

e450 won't boot after newlock2 merge

Here's what happens:

Kernelized RAIDframe activated
panic: kernel diagnostic assertion "l->l_wchan == NULL && l->l_sleepq == 
NULL" failed: file "/u/src/sys/kern/kern_sleepq.c", line 280
cpu0: kdb breakpoint at 1417c60
Stopped in pid 1.1 (swapper) at netbsd:cpu_Debugger+0x4:        nop

This is a GENERIC with the following modifications:

options        NMBCLUSTERS=4096
options        NKMEMPAGES=65536
makeoptions    DEBUG="-g"
options        DIAGNOSTIC
options        INSECURE
Permalink | Reply | 11 comments |

Gmane