freebsd-alpha Digest, Vol 67, Issue 2
freebsd-al...@freebsd.org
freebs...@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-alpha
or, via email, send a message with subject or body 'help' to
freebsd-al...@freebsd.org
You can reach the person managing the list at
freebsd-a...@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-alpha digest..."
Today's Topics:
1. Alphastation 200 (and others) PCI-PCI bridge fix (Michael Kukat)
2. [current tinderbox] failure on alpha/alpha (FreeBSD Tinderbox)
3. Current problem reports assigned to you (FreeBSD bugmaster)
4. Re: Alphastation 200 (and others) PCI-PCI bridge fix
(Bernd Walter)
5. Re: Alphastation 200 (and others) PCI-PCI bridge fix
(Michael Kukat)
6. Re: Alphastation 200 (and others) PCI-PCI bridge fix
(Bernd Walter)
7. Re: Alphastation 200 (and others) PCI-PCI bridge fix
(Michael Kukat)
8. Re: Alphastation 200 (and others) PCI-PCI bridge fix
(Michael Kukat)
9. Opinions on freebsd/alpha (Stephen Jones)
10. Re: Opinions on freebsd/alpha (Wilko Bulte)
----------------------------------------------------------------------
Message: 1
Date: Sun, 27 Jun 2004 21:36:14 +0200 (CEST)
From: Michael Kukat <mic...@unixiron.org>
Subject: Alphastation 200 (and others) PCI-PCI bridge fix
To: freebs...@freebsd.org
Message-ID: <200406272...@calchas.unixiron.org>
Content-Type: text/plain; charset="us-ascii"
Hello,
okay, for my problems with quadport NICs, i stick in the following situation
currently:
- fixed intpin/irq mapping stuff in dec_2100_a50.c, seems to work okay with
my ANA-6944, but this card just maps all 4 NICs to INTA of the first chip,
so this doesn't prove the functionality of this fix.
- ANA-62044 really wants 4 INT lines, but due to the architecture of the PCI
bus in the AlphaStation 200, it just gets 2 of them. IRQs are mapped to the
ISA IRQs, which are not shareable. But 2 of the NIC chips on the card need to
share interrupts when plugged into the AS200 (INTD is INTA on the connetor,
and INTC is the same as onboard LAN).
Another problem in my diagnosis of the problems i have with the ANA-62044:
kernel doesn't panic when this card is in the AS200. So the problem with
crashing with access faults just exists on the PC164. Maybe i should try a
32bit slot.
I attached my fix for this interrupt problem, maybe someone can use it. And if
someone with more clue about PCI has a look in this, maybe it's useable for the
repository. Patch applies to 4.9 sources.
Known problems: this fix just handles bridges on pci0. It doesn't handle
bridges on bridged buses :)
Hope it helps someone. It's not tested very well, feedback welcome.
...Michael
--
http://www.unixiron.org/ Home Powered by: (Net|Open|Free)BSD IRIX NonStop-UX
Solaris AIX HP-UX Tru64 MUNIX Ultrix VMS SINIX Dolphin_Unix OpenStep MacOS A/UX
-------------- next part --------------
diff -Naru sys.orig/alpha/alpha/dec_2100_a50.c sys/alpha/alpha/dec_2100_a50.c
--- sys.orig/alpha/alpha/dec_2100_a50.c Thu Jul 20 08:12:12 2000
+++ sys/alpha/alpha/dec_2100_a50.c Sun Jun 27 19:12:20 2004
@@ -164,29 +164,47 @@
u_int8_t pirqline;
u_int32_t pirqreg;
int pirq;
+ int slot, intpin;
pcicfgregs *cfg;
pirq = 0; /* gcc -Wuninitialized XXX */
cfg = (pcicfgregs *)arg;
/*
+ * If we don't live on bus 0, we are behind a bridge. Handle this.
+ */
+
+ slot = cfg->slot;
+ intpin = cfg->intpin;
+ if(cfg->bus > 0) {
+ cfg = pci_devlist_get_parent(cfg);
+ if(cfg == NULL) {
+ printf("failed to get bridge configuration!\n");
+ } else {
+ intpin = (slot + (intpin - 1)) % 4 + 1;
+ slot = cfg->slot;
+ }
+ cfg = (pcicfgregs *)arg;
+ }
+
+ /*
* Slot->interrupt translation. Taken from NetBSD.
*/
- if(cfg->intpin == 0)
+ if(intpin == 0)
return;
- if(cfg->intpin > 4)
- panic("dec_2100_a50_intr_map: bad intpin %d",cfg->intpin);
+ if(intpin > 4)
+ panic("dec_2100_a50_intr_map: bad intpin %d",intpin);
- switch (cfg->slot) {
+ switch (slot) {
case 6: /* NCR SCSI */
pirq = 3;
break;
case 11: /* slot 1 */
case 14: /* slot 3 */
- switch(cfg->intpin) {
+ switch(intpin) {
case 1:
case 4:
pirq = 0;
@@ -199,12 +217,12 @@
break;
default:
panic("dec_2100_a50_intr_map bogus PCI pin %d\n",
- cfg->intpin);
+ intpin);
}
break;
case 12: /* slot 2 */
- switch (cfg->intpin) {
+ switch (intpin) {
case 1:
case 4:
pirq = 1;
@@ -217,13 +235,13 @@
break;
default:
panic("dec_2100_a50_intr_map bogus PCI pin %d\n",
- cfg->intpin);
+ intpin);
};
break;
case 13: /* slot 3 */
- switch (cfg->intpin) {
+ switch (intpin) {
case 1:
case 4:
pirq = 2;
@@ -238,7 +256,7 @@
break;
default:
printf("dec_2100_a50_intr_map: weird slot %d\n",
- cfg->slot);
+ slot);
/* return; */
}
------------------------------
Message: 2
Date: Mon, 28 Jun 2004 05:28:18 -0400 (EDT)
From: FreeBSD Tinderbox <tind...@freebsd.org>
Subject: [current tinderbox] failure on alpha/alpha
To: FreeBSD Tinderbox <tind...@freebsd.org>, <cur...@freebsd.org>,
<al...@freebsd.org>
Message-ID: <200406280928...@freebsd-current.sentex.ca>
TB --- 2004-06-28 08:00:01 - tinderbox 2.3 running on freebsd-current.sentex.ca
TB --- 2004-06-28 08:00:01 - starting CURRENT tinderbox run for alpha/alpha
TB --- 2004-06-28 08:00:01 - checking out the source tree
TB --- 2004-06-28 08:00:01 - cd /home/tinderbox/sandbox/CURRENT/alpha/alpha
TB --- 2004-06-28 08:00:01 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2004-06-28 08:04:31 - building world (CFLAGS=-O2 -pipe)
TB --- 2004-06-28 08:04:31 - cd /home/tinderbox/sandbox/CURRENT/alpha/alpha/src
TB --- 2004-06-28 08:04:31 - /usr/bin/make -B buildworld
>>> Rebuilding the temporary build tree
>>> stage 1.1: legacy release compatibility shims
>>> stage 1.2: bootstrap tools
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3: cross tools
>>> stage 4.1: building includes
>>> stage 4.2: building libraries
>>> stage 4.3: make dependencies
>>> stage 4.4: building everything
TB --- 2004-06-28 09:10:22 - building generic kernel (COPTFLAGS=-O2 -pipe)
TB --- 2004-06-28 09:10:22 - cd /home/tinderbox/sandbox/CURRENT/alpha/alpha/src
TB --- 2004-06-28 09:10:22 - /usr/bin/make buildkernel KERNCONF=GENERIC
>>> Kernel build for GENERIC started on Mon Jun 28 09:10:23 UTC 2004
>>> stage 1: configuring the kernel
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3.1: making dependencies
>>> stage 3.2: building everything
>>> Kernel build for GENERIC completed on Mon Jun 28 09:24:22 UTC 2004
TB --- 2004-06-28 09:24:22 - generating LINT kernel config
TB --- 2004-06-28 09:24:22 - cd /home/tinderbox/sandbox/CURRENT/alpha/alpha/src/sys/alpha/conf
TB --- 2004-06-28 09:24:22 - /usr/bin/make -B LINT
TB --- 2004-06-28 09:24:22 - building LINT kernel (COPTFLAGS=-O2 -pipe)
TB --- 2004-06-28 09:24:22 - cd /home/tinderbox/sandbox/CURRENT/alpha/alpha/src
TB --- 2004-06-28 09:24:22 - /usr/bin/make buildkernel KERNCONF=LINT
>>> Kernel build for LINT started on Mon Jun 28 09:24:22 UTC 2004
>>> stage 1: configuring the kernel
>>> stage 2.1: cleaning up the object tree
>>> stage 2.2: rebuilding the object tree
>>> stage 2.3: build tools
>>> stage 3.1: making dependencies
>>> stage 3.2: building everything
[...]
cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/alpha/alpha/src/sys -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/altq -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/pf -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/alpha/alpha/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /tinderbox/CURRENT/alpha/alpha/src/sys/dev/ex/if_ex_isa.c
/tinderbox/CURRENT/alpha/alpha/src/sys/dev/ex/if_ex_isa.c: In function `ex_isa_identify':
/tinderbox/CURRENT/alpha/alpha/src/sys/dev/ex/if_ex_isa.c:151: warning: unsigned int format, different type arg (arg 2)
/tinderbox/CURRENT/alpha/alpha/src/sys/dev/ex/if_ex_isa.c:159: warning: unsigned int format, different type arg (arg 2)
/tinderbox/CURRENT/alpha/alpha/src/sys/dev/ex/if_ex_isa.c:189: warning: unsigned int format, different type arg (arg 2)
/tinderbox/CURRENT/alpha/alpha/src/sys/dev/ex/if_ex_isa.c: In function `ex_isa_probe':
/tinderbox/CURRENT/alpha/alpha/src/sys/dev/ex/if_ex_isa.c:224: warning: unsigned int format, different type arg (arg 2)
/tinderbox/CURRENT/alpha/alpha/src/sys/dev/ex/if_ex_isa.c:229: warning: unsigned int format, different type arg (arg 2)
*** Error code 1
Stop in /tinderbox/CURRENT/alpha/alpha/obj/alpha/tinderbox/CURRENT/alpha/alpha/src/sys/LINT.
*** Error code 1
Stop in /tinderbox/CURRENT/alpha/alpha/src.
*** Error code 1
Stop in /tinderbox/CURRENT/alpha/alpha/src.
TB --- 2004-06-28 09:28:18 - WARNING: /usr/bin/make returned exit code 1
TB --- 2004-06-28 09:28:18 - ERROR: failed to build lint kernel
TB --- 2004-06-28 09:28:18 - tinderbox aborted
------------------------------
Message: 3
Date: Mon, 28 Jun 2004 11:02:09 GMT
From: FreeBSD bugmaster <bugm...@freebsd.org>
Subject: Current problem reports assigned to you
To: freebs...@FreeBSD.org
Message-ID: <200406281102....@freefall.freebsd.org>
Current FreeBSD problem reports
Critical problems
S Submitted Tracker Resp. Description
-------------------------------------------------------------------------------
o [2004/01/27] alpha/61973 alpha Machine Check on boot-up of AlphaServer 2
1 problem total.
Serious problems
S Submitted Tracker Resp. Description
-------------------------------------------------------------------------------
o [2001/09/10] alpha/30486 alpha AlphaServer DS10 floppy access is broken
o [2001/09/10] alpha/30487 alpha Floppy access on AlphaServer DS20 solid l
o [2003/02/05] alpha/47952 alpha DEFPA causes machine check with V5.0-rele
o [2004/01/26] alpha/61940 alpha Can't disklabel new disk from FreeBSD/alp
o [2004/02/03] alpha/62321 alpha ntpd gives unaligned access errors on alp
o [2004/06/06] alpha/67626 alpha X crashes an alpha machine, resulting reb
6 problems total.
Non-critical problems
S Submitted Tracker Resp. Description
-------------------------------------------------------------------------------
o [2001/01/27] alpha/24663 alpha Console output gets scribbled into /var/l
o [2001/02/22] alpha/25284 alpha PC164 won't reboot with graphics console
o [2001/06/07] alpha/27933 alpha Time jitter under load on FreeBSD 4.3 alp
f [2001/07/29] alpha/29299 alpha FreeBSD 4.3 Alpha + Tekram SCSI adapter p
o [2001/10/01] alpha/30970 alpha Ensoniq 1371 (Creative chipset) does not
o [2002/01/24] alpha/34232 alpha rpc.statd throws alignment errors
o [2002/05/13] alpha/38031 alpha osf1.ko not loaded during boot-time of li
p [2002/11/12] alpha/45240 alpha pstat -f column headings misaligned on Al
o [2003/02/25] alpha/48676 alpha Changing the baud rate of serial consoles
o [2003/04/12] alpha/50868 alpha fd0 floppy device is not mapped into /dev
o [2004/06/13] alpha/67903 alpha hw.chipset.memory: 1099511627776 - thats
11 problems total.
------------------------------
Message: 4
Date: Mon, 28 Jun 2004 14:48:10 +0200
From: Bernd Walter <ti...@cicely12.cicely.de>
Subject: Re: Alphastation 200 (and others) PCI-PCI bridge fix
To: Michael Kukat <mic...@unixiron.org>
Cc: freebs...@freebsd.org
Message-ID: <2004062812...@cicely12.cicely.de>
Content-Type: text/plain; charset=us-ascii
On Sun, Jun 27, 2004 at 09:36:14PM +0200, Michael Kukat wrote:
> Hello,
>
> okay, for my problems with quadport NICs, i stick in the following situation
> currently:
>
> - fixed intpin/irq mapping stuff in dec_2100_a50.c, seems to work okay with
> my ANA-6944, but this card just maps all 4 NICs to INTA of the first chip,
> so this doesn't prove the functionality of this fix.
>
> - ANA-62044 really wants 4 INT lines, but due to the architecture of the PCI
> bus in the AlphaStation 200, it just gets 2 of them. IRQs are mapped to the
> ISA IRQs, which are not shareable. But 2 of the NIC chips on the card need to
> share interrupts when plugged into the AS200 (INTD is INTA on the connetor,
> and INTC is the same as onboard LAN).
The IRQs on the AS200 should be shareable as on every PCI architecture.
> Another problem in my diagnosis of the problems i have with the ANA-62044:
> kernel doesn't panic when this card is in the AS200. So the problem with
> crashing with access faults just exists on the PC164. Maybe i should try a
> 32bit slot.
The pci slots on a PC164 are all on the same bus, so I doubt that it'll
make a big difference.
> I attached my fix for this interrupt problem, maybe someone can use it. And if
> someone with more clue about PCI has a look in this, maybe it's useable for the
> repository. Patch applies to 4.9 sources.
We already have generic code to do interrupt routing over bridges.
See Rev 1.14 in dec_axppci_33.c for a example on how to use it.
It's quite simple to do - getting someone with hardware to test is the
biggest challenge.
I can create you a patch if you need.
> Known problems: this fix just handles bridges on pci0. It doesn't handle
> bridges on bridged buses :)
The generic code used by axppci33 does :)
--
B.Walter BWCT http://www.bwct.de
be...@bwct.de in...@bwct.de
------------------------------
Message: 5
Date: Mon, 28 Jun 2004 14:54:39 +0200
From: Michael Kukat <mic...@unixiron.org>
Subject: Re: Alphastation 200 (and others) PCI-PCI bridge fix
To: ti...@cicely.de
Cc: freebs...@freebsd.org
Message-ID: <200406281454....@unixiron.org>
Content-Type: text/plain; charset="iso-8859-1"
Hi !
On Monday 28 June 2004 14:48, you wrote:
> The IRQs on the AS200 should be shareable as on every PCI architecture.
Tried out - works. New diff available :) I'm trying to test all this a bit
with some stress on the shared interrupts this evening.
> The pci slots on a PC164 are all on the same bus, so I doubt that it'll
> make a big difference.
Hm. isn't there something in the specs, that a 64bit bus will be degraded to
32bit, if there are 32bit cards present? So this 64bit stuff would not be too
useful in this box...
> We already have generic code to do interrupt routing over bridges.
> See Rev 1.14 in dec_axppci_33.c for a example on how to use it.
> It's quite simple to do - getting someone with hardware to test is the
> biggest challenge.
> I can create you a patch if you need.
I'll try to find the time to get the version (uhm, FreeBSD-cvs mirror at home,
no problem so :) and screw it in. Hope to get my tests done with all puzzle
parts put together.
> The generic code used by axppci33 does :)
Hope to be able to bring a "final version" of the patch soon.
...Michael
------------------------------
Message: 6
Date: Mon, 28 Jun 2004 15:04:29 +0200
From: Bernd Walter <ti...@cicely12.cicely.de>
Subject: Re: Alphastation 200 (and others) PCI-PCI bridge fix
To: Michael Kukat <mic...@unixiron.org>
Cc: ti...@cicely.de
Message-ID: <2004062813...@cicely12.cicely.de>
Content-Type: text/plain; charset=us-ascii
On Mon, Jun 28, 2004 at 02:54:39PM +0200, Michael Kukat wrote:
> On Monday 28 June 2004 14:48, you wrote:
> > The pci slots on a PC164 are all on the same bus, so I doubt that it'll
> > make a big difference.
>
> Hm. isn't there something in the specs, that a 64bit bus will be degraded to
> 32bit, if there are 32bit cards present? So this 64bit stuff would not be too
> useful in this box...
No - the bus would only be degraded on 66MHz vs. 33MHz and the PC164
ist 33MHz anyway (as long as you setup the clock divisor correctly).
--
B.Walter BWCT http://www.bwct.de
be...@bwct.de in...@bwct.de
------------------------------
Message: 7
Date: Mon, 28 Jun 2004 16:40:54 +0200 (CEST)
From: Michael Kukat <mic...@unixiron.org>
Subject: Re: Alphastation 200 (and others) PCI-PCI bridge fix
To: ti...@cicely.de
Cc: freebs...@freebsd.org
Message-ID: <2004062816...@calchas.unixiron.org>
Content-Type: TEXT/PLAIN; charset=US-ASCII
Hi !
On Mon, 28 Jun 2004, Bernd Walter wrote:
> We already have generic code to do interrupt routing over bridges.
> See Rev 1.14 in dec_axppci_33.c for a example on how to use it.
> It's quite simple to do - getting someone with hardware to test is the
> biggest challenge.
> I can create you a patch if you need.
Hm. Not funny here. I think i should just upgrade to 5.1, as this uses 1.17,
ans so i can use the pci_intr_route hooks there. So no patches for today, as my
4.9 here doesn't know about this. Maybe next weekend, if i find the time.
But i'll check my stuff and fix some other problems in the sf driver, because
it's a bit horrible code i think...
metis# netstat -ni | grep sf | grep Link
sf0 1500 <Link#2> 00:00:d1:ee:03:f9 8 0 5 0 717259281920
sf1 1500 <Link#3> 00:00:d1:ee:03:fa 7 0 4 0 125335690806784
sf2 1500 <Link#4> 00:00:d1:ee:03:fb 2 0 9 0 133216952971776
sf3 1500 <Link#5> 00:00:d1:ee:03:fc 1 0 9 0 121126624363520
funny collision counters :)
...Michael
--
http://www.unixiron.org/ Home Powered by: (Net|Open|Free)BSD IRIX NonStop-UX
Solaris AIX HP-UX Tru64 MUNIX Ultrix VMS SINIX Dolphin_Unix OpenStep MacOS A/UX
------------------------------
Message: 8
Date: Mon, 28 Jun 2004 18:14:12 +0200 (CEST)
From: Michael Kukat <mic...@unixiron.org>
Subject: Re: Alphastation 200 (and others) PCI-PCI bridge fix
To: ti...@cicely.de
Cc: freebs...@freebsd.org
Message-ID: <2004062818...@calchas.unixiron.org>
Content-Type: TEXT/PLAIN; charset=US-ASCII
Hi again,
On Mon, 28 Jun 2004, Bernd Walter wrote:
> The IRQs on the AS200 should be shareable as on every PCI architecture.
- implemented
> We already have generic code to do interrupt routing over bridges.
> See Rev 1.14 in dec_axppci_33.c for a example on how to use it.
> It's quite simple to do - getting someone with hardware to test is the
> biggest challenge.
- scheduled for soon, need to upgrade to 5.x first
my current state is attached. This is now tested with the ANA-62044, which
really uses 4 IRQs through the bridge. Following configuration:
ANA-62044 in slot 3 of AlphaStation 200, leading to the following IRQ layout:
onboard de0 - IRQ 5
sf0 - IRQ 15
sf1 - IRQ 14
sf2 - IRQ 5
sf3 - IRQ 15
(maybe i confused IRQ 14/15 :)
Tested:
load on sf0 and sf1, on de0 and sf2 and on sf0 and sf3, thus meaning all
combinations of single IRQ, shared on-card and shared on 2 different devices.
Test was done by simply running ping -f through the machine acting as router,
and running ping -f from 2 external hosts onto the alpha in parallel. All tests
ran through without any problems, peak load was about 20000 interrupts/s
(sf0/sf3).
So... this hack can be considered stable and might especially help 4.x-users.
I'll try to re-use this interrupt shareable flag handling in the newer version
using the new routing devmethod functionality. Didn't find a better way to
implement it. And usually sharing IRQs between "ISA devices" is not common :)
...Michael
--
http://www.unixiron.org/ Home Powered by: (Net|Open|Free)BSD IRIX NonStop-UX
Solaris AIX HP-UX Tru64 MUNIX Ultrix VMS SINIX Dolphin_Unix OpenStep MacOS A/UX
------------------------------
Message: 9
Date: Mon, 28 Jun 2004 17:19:24 -0700
From: Stephen Jones <s...@cirr.com>
Subject: Opinions on freebsd/alpha
To: freebs...@freebsd.org
Message-ID: <F9670FE1-C961-11D8...@cirr.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Hi, I'd like to hear some opinions on production implementations in
regards to FreeBSD/alpha.
I'm not really interested in how much uptime you've accumulated on a
idle or lightly used
system. Basically I'd like to hear from people who are using
FreeBSD/alpha with:
* stock DS10L and CS20 machines (AS8400 too)
* At least 10 NFS clients and one or two NFS fileservers
* more than home directory mounts, but steady to intense reads
(mostly), but writes as well 24/7
* NIS for 30,000+ accounts (well, your userbase should be at least 5000
or 5000 'websites')
* MP (at least 2 CPUs)
* 4.10 or 5.2.x (would you consider 5.2.1 for production?)
Have you had any issues with lock manager panics (locking onself) or
vnode 'vnlock'ing with
cascading deadlocks? other issues? lock ups? panics? funky stuff?
You're welcome to email me privately if you don't think it would be
appropriate to share with
the list.
------------------------------
Message: 10
Date: Tue, 29 Jun 2004 07:43:46 +0200
From: Wilko Bulte <w...@freebie.xs4all.nl>
Subject: Re: Opinions on freebsd/alpha
To: Stephen Jones <s...@cirr.com>
Cc: freebs...@freebsd.org
Message-ID: <2004062905...@freebie.xs4all.nl>
Content-Type: text/plain; charset=us-ascii
On Mon, Jun 28, 2004 at 05:19:24PM -0700, Stephen Jones wrote:
> Hi, I'd like to hear some opinions on production implementations in
> regards to FreeBSD/alpha.
> I'm not really interested in how much uptime you've accumulated on a
> idle or lightly used
> system. Basically I'd like to hear from people who are using
> FreeBSD/alpha with:
>
> * stock DS10L and CS20 machines (AS8400 too)
TurboLaser support is shaky, on 4.x (for some version of x) it worked
but 5.x it does no longer (I have not tried for a long time).
DS10[L] support is pretty much OK.
--
Wilko Bulte wi...@FreeBSD.org
------------------------------
_______________________________________________
freebs...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-alpha
To unsubscribe, send any mail to "freebsd-alph...@freebsd.org"
End of freebsd-alpha Digest, Vol 67, Issue 2
********************************************