From owner-freebsd-alpha Sun Jul 9 2:42:24 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from penfret.boisvieux.com (r76m119.cybercable.tm.fr [195.132.76.119])
by hub.freebsd.org (Postfix) with ESMTP id 0E3EE37B543
for <freebsd-alpha@freebsd.org>; Sun, 9 Jul 2000 02:42:19 -0700 (PDT)
(envelope-from jfb@penfret.boisvieux.com)
Received: (from jfb@localhost)
by penfret.boisvieux.com (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id LAA05084;
Sun, 9 Jul 2000 11:42:16 GMT
Date: Sun, 9 Jul 2000 11:42:16 +0000
From: Jean-Francois Boisvieux <jfb@penfret.boisvieux.com>
To: freebsd-alpha@freebsd.org
Cc: pour Ponthieu <jfb@wemsdiet.com>
Subject: Problem installing freeBSD on XP1000
Message-ID: <20000709114216.A5076@penfret.boisvieux.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.4i
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
I've an XP1000 (667 Mhz, 512 Mo memory, 4 disk one of which is free) running
linux (suse 6.3) quit satisfactorily.
The first disk is plan to install freebsd, I've downloaded the last
image.iso of free and try to boot with it
everithing seems to go nicely execpt that after the apparition of a red
screen which (I think) presents options, I have a kernel panic and a reboot
with the following message
"panic going nowhere without my init"
I'am aware of the scsi hose problem and I've installed my scsi controller on
upper PCI slots.
I've tried to find info and I can't find anything useful. I've also tried to
boot netbsd but then it says that it sees only 1 disk which prevent me to go
further since I don't want to break my linux installation
can you help or give me pointer since I'm sure that free runs on xp1000, and
I want to use it as a server.
Thanks for help
-- in case I join you the linux dmesg
___ BEGIN LOG
: 65536 (order 6, 512k)
POSIX conformance testing by UNIFIX
Alpha PCI BIOS32 revision 0.04
PCI: Probing PCI hardware
SMC37c669 Super I/O Controller found @ 0x3f0
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Unix domain sockets 1.0 for Linux NET4.0.
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
TCP: Hash tables configured (ehash 524288 bhash 65536)
Starting kswapd v 1.5
Detected PS/2 Mouse Port.
pty: 256 Unix98 ptys configured
RAM disk driver initialized: 16 RAM disks of 4096K size
loop: registered device at major 7
hda: Compaq CRD-8322B, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Floppy drive(s): fd0 is 2.88M
FDC 0 is a post-1991 82077
sym53c8xx: at PCI bus 0, device 12, function 0
sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up)
sym53c8xx: 53c895 detected
sym53c895-0: rev=0x01, base=0xe020000, io_port=0x8800, irq=36
sym53c895-0: NCR clock is 40037KHz, 40218KHz
sym53c895-0: ID 7, Fast-40, Parity Checking
sym53c895-0: on-chip RAM at 0xe021000
sym53c895-0: restart (scsi reset).
sym53c895-0: Downloading SCSI SCRIPTS.
sym53c895-0: SCSI bus mode change from 80 to 80.
sym53c895-0: restart (scsi mode change).
sym53c895-0: Downloading SCSI SCRIPTS.
ncr53c8xx: at PCI bus 0, device 12, function 0
ncr53c8xx: IO region 0x8800 to 0x887f is in use
scsi0 : sym53c8xx - version 1.3g
scsi1 : SCSI host adapter emulation for IDE ATAPI devices
scsi : 2 hosts.
Vendor: COMPAQ Model: BD009222C7 Rev: B016
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
Vendor: SEAGATE Model: ST39102LW Rev: 8320
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdb at scsi0, channel 0, id 1, lun 0
Vendor: SEAGATE Model: ST39102LW Rev: 8320
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdc at scsi0, channel 0, id 3, lun 0
Vendor: SEAGATE Model: ST318203LW Rev: 0002
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdd at scsi0, channel 0, id 4, lun 0
sym53c895-0-<0,0>: tagged command queue depth set to 8
sym53c895-0-<1,0>: tagged command queue depth set to 8
sym53c895-0-<3,0>: tagged command queue depth set to 8
sym53c895-0-<4,0>: tagged command queue depth set to 8
Vendor: COMPAQ Model: CRD-8322B Rev: 1.07
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr0 at scsi1, channel 0, id 0, lun 0
Vendor: COMPAQ Model: CRD-8322B Rev: 1.07
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr1 at scsi1, channel 0, id 0, lun 1
Vendor: COMPAQ Model: CRD-8322B Rev: 1.07
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr2 at scsi1, channel 0, id 0, lun 2
Vendor: COMPAQ Model: CRD-8322B Rev: 1.07
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr3 at scsi1, channel 0, id 0, lun 3
Vendor: COMPAQ Model: CRD-8322B Rev: 1.07
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr4 at scsi1, channel 0, id 0, lun 4
Vendor: COMPAQ Model: CRD-8322B Rev: 1.07
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr5 at scsi1, channel 0, id 0, lun 5
Vendor: COMPAQ Model: CRD-8322B Rev: 1.07
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr6 at scsi1, channel 0, id 0, lun 6
Vendor: COMPAQ Model: CRD-8322B Rev: 1.07
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr7 at scsi1, channel 0, id 0, lun 7
scsi : detected 8 SCSI cdroms 4 SCSI disks total.
sr0: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
Uniform CDROM driver Revision: 2.56
sr1: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
sr2: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
sr3: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
sr4: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
sr5: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
sr6: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
sr7: scsi3-mmc drive: 32x/32x cd/rw xa/form2 cdda tray
sda: Spinning up disk...<6>sym53c895-0-<0,*>: FAST-10 SCSI 10.0 MB/s (100 ns, offset 31)
....................ready
SCSI device sda: hdwr sector= 512 bytes. Sectors= 17773524 [8678 MB] [8.7 GB]
sym53c895-0-<1,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 15)
SCSI device sdb: hdwr sector= 512 bytes. Sectors= 17783240 [8683 MB] [8.7 GB]
sym53c895-0-<3,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 15)
SCSI device sdc: hdwr sector= 512 bytes. Sectors= 17783240 [8683 MB] [8.7 GB]
sym53c895-0-<4,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 15)
SCSI device sdd: hdwr sector= 512 bytes. Sectors= 35566480 [17366 MB] [17.4 GB]
3c59x.c:v0.99H 11/17/98 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
eth0: 3Com 3c905B Cyclone 100baseTx at 0x10000a000, 00:10:5a:64:69:b1, IRQ 28
8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface.
MII transceiver found at address 24, status 786d.
MII transceiver found at address 0, status 786d.
Enabling bus-master transmits and whole-frame receives.
tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov
eth1: Digital DS21143 Tulip rev 65 at 0x100009000, 00:00:F8:71:59:0B, IRQ 45.
eth1: EEPROM default media type Autosense.
eth1: Index #0 - Media 10baseT (#0) described by a 21142 Serial PHY (2) block.
eth1: Index #1 - Media 10base2 (#1) described by a 21142 Serial PHY (2) block.
eth1: Index #2 - Media AUI (#2) described by a 21142 Serial PHY (2) block.
eth1: Index #3 - Media 10baseT-FD (#4) described by a 21142 Serial PHY (2) block.
eth1: Index #4 - Media 100baseTx (#3) described by a 21143 SYM PHY (4) block.
eth1: Index #5 - Media 100baseTx-FD (#5) described by a 21143 SYM PHY (4) block.
Partition check:
sda: sda1 sda2
sdb: sdb1 sdb2 sdb3 sdb4 sdb5 sdb6
sdc: sdc1 sdc2 sdc3
sdd: sdd1
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 152k freed
Adding Swap: 1023984k swap-space (priority -1)
<sc 224(3ffc00041e0,3ffc0000ad0,f)><sc 224(3ffc00042a0,3ffc0000ad0,f)><sc 224(3ffc0004360,3ffc0000ad0,f)><sc 224(3ffc00044e0,3ffc0000ad0,f)><sc 224(3ffc0004660,3ffc0000ad0,f)><sc 224(3ffc00047e0,3ffc0000ad0,f)><sc 224(3ffc0004960,3ffc0000ad0,f)><sc 224(3ffc0004ae0,3ffc0000ad0,f)><sc 224(3ffc0004c60,3ffc0000ad0,f)><sc 224(3ffc0004de0,3ffc0000ad0,f)><sc 224(3ffc0004ea0,3ffc0000ad0,f)><sc 224(3ffc0005080,3ffc0000ad0,f)><sc 224(3ffc0005200,3ffc0000ad0,f)>set_program_attributes(12000000 d8c000 14000000 46ad10)
<sc 0(84,64,11ffff710)><sc 53(8,64,11ffff710)><sc 0(17,521c,11ffff710)><sc 53(8,521c,11ffff710)><sc 224(3ffc00041e0,3ffc0000ad0,f)><sc 224(3ffc00042a0,3ffc0000ad0,f)><sc 224(3ffc0004360,3ffc0000ad0,f)><sc 224(3ffc00044e0,3ffc0000ad0,f)><sc 224(3ffc0004660,3ffc0000ad0,f)><sc 224(3ffc00047e0,3ffc0000ad0,f)><sc 224(3ffc0004960,3ffc0000ad0,f)><sc 224(3ffc0004ae0,3ffc0000ad0,f)><sc 224(3ffc0004c60,3ffc0000ad0,f)><sc 224(3ffc0004de0,3ffc0000ad0,f)><sc 224(3ffc0004ea0,3ffc0000ad0,f)><sc 224(3ffc0005080,3ffc0000ad0,f)><sc 224(3ffc0005200,3ffc0000ad0,f)>set_program_attributes(12000000 d8c000 14000000 46ad10)
<sc 0(84,64,11ffff718)><sc 53(8,64,11ffff718)><sc 0(17,521c,11ffff718)><sc 53(8,521c,11ffff718)><sc 224(11fffdcd0,3ffc0000ad0,132c0)><sc 224(146f97c0,3ffc0000ad0,132c0)><sc 224(146f97c0,3ffc0000ad0,132c0)><sc 224(146f97c0,3ffc0000ad0,132c0)><sc 224(146f9880,3ffc0000ad0,132c0)><sc 224(146f9880,3ffc0000ad0,132c0)><sc 224(14761a80,3ffc0000ad0,132c0)><sc 224(11fffcb70,3ffc0000ad0,132c0)><sc 0(a0,11fffd668,11fffd488)><sc 0(a0,11fffc6c8,11fffc4e8)>
--- END LOG
thanks
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Sun Jul 9 7:25:34 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
by hub.freebsd.org (Postfix) with ESMTP id C45EB37B839
for <freebsd-alpha@FreeBSD.ORG>; Sun, 9 Jul 2000 07:25:31 -0700 (PDT)
(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA29621;
Sun, 9 Jul 2000 10:25:30 -0400 (EDT)
Received: (from gallatin@localhost)
by grasshopper.cs.duke.edu (8.9.3/8.9.1) id KAA20896;
Sun, 9 Jul 2000 10:25:30 -0400 (EDT)
(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Sun, 9 Jul 2000 10:25:29 -0400 (EDT)
To: Jean-Francois Boisvieux <jfb@boisvieux.com>
Cc: freebsd-alpha@FreeBSD.ORG, pour Ponthieu <jfb@wemsdiet.com>
Subject: Re: Problem installing freeBSD on XP1000
In-Reply-To: <20000709114216.A5076@penfret.boisvieux.com>
References: <20000709114216.A5076@penfret.boisvieux.com>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid
Message-ID: <14696.35504.246759.81650@grasshopper.cs.duke.edu>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Jean-Francois Boisvieux writes:
>
> "panic going nowhere without my init"
For some reason, our install kernel is seriously confused when it is
presented with multiple disks with BSD disklabels.
Try unplugging all disks but the one you want to install freebsd on,
then booting.
Cheers,
Drew
------------------------------------------------------------------------------
Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin
Duke University Email: gallatin@cs.duke.edu
Department of Computer Science Phone: (919) 660-6590
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Sun Jul 9 7:53:50 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
by hub.freebsd.org (Postfix) with ESMTP id DC63F37B839
for <freebsd-alpha@FreeBSD.ORG>; Sun, 9 Jul 2000 07:53:46 -0700 (PDT)
(envelope-from mjacob@feral.com)
Received: from beppo.feral.com (beppo [192.67.166.79])
by feral.com (8.9.3/8.9.3) with ESMTP id HAA24428;
Sun, 9 Jul 2000 07:53:40 -0700
Date: Sun, 9 Jul 2000 07:53:41 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Jean-Francois Boisvieux <jfb@boisvieux.com>
Cc: freebsd-alpha@FreeBSD.ORG, pour Ponthieu <jfb@wemsdiet.com>
Subject: Re: Problem installing freeBSD on XP1000
In-Reply-To: <20000709114216.A5076@penfret.boisvieux.com>
Message-ID: <Pine.BSF.4.10.10007090750530.27449-100000@beppo.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
You have to sway *what* you were trying to install and give some messages.
If you were trying to install FreeBSD-4.0, yes, there are some known problems
with the Qlogic driver which can cause the disks to not be seen sometimes-
although your linux messages indicate that this was with a SYM board.
If it was with the Qlogic board, Try a newer snapshot or wait for 4.1 (out in
a few weeks). If something else, we need more information, thanks.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Sun Jul 9 14:33:34 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137])
by hub.freebsd.org (Postfix) with ESMTP id C69B437B669
for <alpha@freebsd.org>; Sun, 9 Jul 2000 14:33:31 -0700 (PDT)
(envelope-from gibbs@plutotech.com)
Received: from caspian.plutotech.com (root@mail.plutotech.com [206.168.67.137])
by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id PAA27142;
Sun, 9 Jul 2000 15:33:29 -0600 (MDT)
(envelope-from gibbs@plutotech.com)
Message-Id: <200007092133.PAA27142@pluto.plutotech.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: mjacob@feral.com
Cc: "Justin T. Gibbs" <gibbs@plutotech.com>, alpha@freebsd.org
Subject: Re: AHC_ALLOW_MEMIO in 4.1 && 5.0 for alpha?
In-Reply-To: Your message of "Sat, 08 Jul 2000 17:36:15 PDT."
<Pine.BSF.4.05.10007081734420.93991-100000@semuta.feral.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 09 Jul 2000 15:34:07 -0600
From: "Justin T. Gibbs" <gibbs@plutotech.com>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
>Justin- things work a lot better on alphas when they use mem space in
>preference to I/O space- in particular I just got bit by a 3940 not working
>(past the bridge) in I/O space.
>
>Do you mind if I we set this option into the GENERIC for alpha?
As far as I'm concerned, the "allow memio" options in drivers are
a hack that was supposed to be temporary. Memory mapped I/O should
always be preferred and the allocation fail if the path to the device
cannot support it. Unfortunately we don't have that mechanism yet.
In the mean time, I'll let others dictate the default policy for which
type of access method is attempted first.
--
Justin
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Sun Jul 9 15:44:24 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
by hub.freebsd.org (Postfix) with ESMTP id 65A9237B684
for <freebsd-alpha@freebsd.org>; Sun, 9 Jul 2000 15:44:22 -0700 (PDT)
(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id SAA03817
for <freebsd-alpha@freebsd.org>; Sun, 9 Jul 2000 18:44:20 -0400 (EDT)
Received: (from gallatin@localhost)
by grasshopper.cs.duke.edu (8.9.3/8.9.1) id SAA21599;
Sun, 9 Jul 2000 18:44:20 -0400 (EDT)
(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Sun, 9 Jul 2000 18:44:20 -0400 (EDT)
To: freebsd-alpha@freebsd.org
Subject: XFree86-4.0.1 seems to work!!
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid
Message-ID: <14696.65054.358275.5292@grasshopper.cs.duke.edu>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Anybody out there who is having trouble with XFree86 related panics
(panic: machine check) should try upgrading to -stable & building the
latest XFree86-4.0.1.
I had been seeing machine checks when running XFree86-4.0 on my Miata
with a powerstorm 4D10 (3dlabs) but I no longer see them. I'd been
planning on spending the evening debugging the panics when, much to my
surprise, everything "just worked" (with the exception of the build
expecting a directory which doesn't exist:
xc/programs/Xserver/hw/xfree86/drivers/AgpGartDrivers)
I'm unsure if this newfound stability is due to the new toolchain that
was MFC'ed to -stable last week, or if its due to a change in X
itself..
Cheers,
Drew
------------------------------------------------------------------------------
Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin
Duke University Email: gallatin@cs.duke.edu
Department of Computer Science Phone: (919) 660-6590
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Mon Jul 10 13:10:51 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from ganymede.or.intel.com (ganymede.or.intel.com [134.134.248.3])
by hub.freebsd.org (Postfix) with ESMTP id AD84437B8DD
for <freebsd-alpha@FreeBSD.org>; Mon, 10 Jul 2000 13:10:45 -0700 (PDT)
(envelope-from kyle.unice@intel.com)
Received: from SMTP (orsmsxvs01-1.jf.intel.com [192.168.65.200])
by ganymede.or.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.30 2000/06/08 18:25:35 dmccart Exp $) with SMTP id NAA05261
for <freebsd-alpha@FreeBSD.org>; Mon, 10 Jul 2000 13:10:43 -0700 (PDT)
Received: from orsmsx28.jf.intel.com ([192.168.70.28]) by 192.168.70.200
(Norton AntiVirus for Internet Email Gateways 1.0) ;
Mon, 10 Jul 2000 20:10:43 0000 (GMT)
Received: by orsmsx28.jf.intel.com with Internet Mail Service (5.5.2650.21)
id <3KFKAZA4>; Mon, 10 Jul 2000 13:10:41 -0700
Message-ID: <A7675204C322D411820600A0C96B7BF5092BB2@ORSMSX36>
From: "Unice, Kyle" <kyle.unice@intel.com>
To: "'freebsd-alpha@FreeBSD.org'" <freebsd-alpha@FreeBSD.org>
Subject:
Date: Mon, 10 Jul 2000 12:58:35 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
charset="iso-8859-1"
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
W. Kyle Unice
Senior Software Eng. Mail Stop UT2 F2-46
Internet Management Appliance Division American Fork, Utah 84003
Intel Corporation Voice: (801)
763-2853
734 East Utah Valley Drive, Suite #300 FAX: (801) 763-2897
Email: kyle <dot> unice <at> intel <dot> com
Viewpoints, opinions, and content are my own and not neccessarily those of
Intel Inc.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Tue Jul 11 6:27: 3 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from fw.brother.com.mx (via-lan-200.33-165-151.brother.com.mx [200.33.165.151])
by hub.freebsd.org (Postfix) with ESMTP id 92C7237BF61
for <freebsd-alpha@FreeBSD.ORG>; Tue, 11 Jul 2000 06:26:59 -0700 (PDT)
(envelope-from szapata@creatos.com.mx)
Received: by fw.brother.com.mx; id IAA07881; Tue, 11 Jul 2000 08:25:11 -0500 (CDT)
Received: from du-148-235-218-222.prodigy.net.mx(148.235.218.222) by fw.brother.com.mx via smap (V4.2)
id xma007875; Tue, 11 Jul 00 08:24:57 -0500
Message-ID: <396B3C49.6696EDE4@creatos.com.mx>
Date: Tue, 11 Jul 2000 08:24:57 -0700
From: Santiago Zapata <szapata@creatos.com.mx>
Reply-To: szapata@creatos.com.mx
Organization: Metcom
X-Mailer: Mozilla 4.7C-CCK-MCD {C-UDP; EBM-APPLE} (Macintosh; I; PPC)
X-Accept-Language: en
MIME-Version: 1.0
To: freebsd-alpha@FreeBSD.ORG
Subject: newbie installation question on Alpha Server 1000
Content-Type: text/plain; charset=us-ascii; x-mac-type="54455854"; x-mac-creator="4D4F5353"
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Hi:
I am trying to install 4.0-RELEASE on an AlphaServer 1000.
I already downloaded the boot floppies, I even reach the initial
installation screen when I boot from the floppies but my hard drive is
not recognized
I tried to do my homewoork searching the list, I found a cuple of
similar questions but I could not find an answer posted.
I read about having to spin the hard drive to be recogized but I did not
find how. I also read in the HARDWARE.TXT file that the kernel needs
"options DEC_1000A" but I do not know how to do it at boot time
I have installed a couple of FreeBSD on Intel but it is my first Alpha,
I have no other Alpha experience
Thanks a lot
Santiago Zapata
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Tue Jul 11 6:32:35 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
by hub.freebsd.org (Postfix) with ESMTP id 7686537BBF2
for <freebsd-alpha@FreeBSD.ORG>; Tue, 11 Jul 2000 06:32:32 -0700 (PDT)
(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA01331;
Tue, 11 Jul 2000 09:32:30 -0400 (EDT)
Received: (from gallatin@localhost)
by grasshopper.cs.duke.edu (8.9.3/8.9.1) id JAA27793;
Tue, 11 Jul 2000 09:32:30 -0400 (EDT)
(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Tue, 11 Jul 2000 09:32:30 -0400 (EDT)
To: szapata@creatos.com.mx
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: newbie installation question on Alpha Server 1000
In-Reply-To: <396B3C49.6696EDE4@creatos.com.mx>
References: <396B3C49.6696EDE4@creatos.com.mx>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid
Message-ID: <14699.8405.370034.463341@grasshopper.cs.duke.edu>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Santiago Zapata writes:
> Hi:
>
> I am trying to install 4.0-RELEASE on an AlphaServer 1000.
> I already downloaded the boot floppies, I even reach the initial
> installation screen when I boot from the floppies but my hard drive is
> not recognized
>
> I tried to do my homewoork searching the list, I found a cuple of
> similar questions but I could not find an answer posted.
>
As you probably found when doing your homework, it is impossible for
us to help without a good description of your hardware, the version of
FreeBSD you are using, and whatever output you saw when you booted
FreeBSD.
Please post the output of the SRM 'show conf' command. Please also
post the boot output from FreeBSD. It is helpful to use a serial
console to capture this output (you may also be able to scroll back in
a graphics console by hitting scroll-lock & using the pageup/pagedown
keys).
Cheers,
Drew
------------------------------------------------------------------------------
Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin
Duke University Email: gallatin@cs.duke.edu
Department of Computer Science Phone: (919) 660-6590
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Tue Jul 11 6:42:55 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from gw.one.com.au (gw.one.com.au [203.18.85.1])
by hub.freebsd.org (Postfix) with ESMTP id 6777737B931
for <freebsd-alpha@FreeBSD.ORG>; Tue, 11 Jul 2000 06:42:49 -0700 (PDT)
(envelope-from raymond@one.com.au)
Received: from one.com.au (pmo.local [10.18.85.2])
by gw.one.com.au (8.9.2/8.9.2) with SMTP id XAA39132
for freebsd-alpha@FreeBSD.ORG; Tue, 11 Jul 2000 23:42:42 +1000 (EST)
(envelope-from raymond@one.com.au)
Date: Tue, 11 Jul 2000 23:42:42 +1000 (EST)
From: User Raymond <raymond@one.com.au>
Message-Id: <200007111342.XAA39132@gw.one.com.au>
Subject: newbie installation question on Alpha Server 1000
To: freebsd-alpha@FreeBSD.ORG
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
To: freebsd-alpha@FreeBSD.ORG
Andrew Gallatin wrote:
> Santiago Zapata writes:
> > Hi:
> >
> > I am trying to install 4.0-RELEASE on an AlphaServer 1000.
> > I already downloaded the boot floppies, I even reach the initial
> > installation screen when I boot from the floppies but my hard drive is
> > not recognized
> >
> > I tried to do my homewoork searching the list, I found a cuple of
> > similar questions but I could not find an answer posted.
> >
>
> As you probably found when doing your homework, it is impossible for
> us to help without a good description of your hardware, the version of
> FreeBSD you are using, and whatever output you saw when you booted
> FreeBSD.
>
> Please post the output of the SRM 'show conf' command. Please also
> post the boot output from FreeBSD. It is helpful to use a serial
> console to capture this output (you may also be able to scroll back in
> a graphics console by hitting scroll-lock & using the pageup/pagedown
> keys).
>
> Cheers,
>
> Drew
I'm sorry to have to say this Drew but Santiago already gave the version
of FreeBSD in his initial message.
Basically, 4.0-RELEASE isn't usable. It took me a month to get installed.
My questions re "can't get anywhere without my init" went largely unanswered.
After that month, I found it wouldn't run my app anyway (see Problem Report
alpha/18808). No one seems that interested. I suggest you move the
"alpha port" back into "under development".
Ray Newman
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Tue Jul 11 7:10:48 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
by hub.freebsd.org (Postfix) with ESMTP id 6DB0137BFC5
for <freebsd-alpha@FreeBSD.ORG>; Tue, 11 Jul 2000 07:10:41 -0700 (PDT)
(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA02033;
Tue, 11 Jul 2000 10:10:36 -0400 (EDT)
Received: (from gallatin@localhost)
by grasshopper.cs.duke.edu (8.9.3/8.9.1) id KAA27902;
Tue, 11 Jul 2000 10:10:36 -0400 (EDT)
(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Tue, 11 Jul 2000 10:10:36 -0400 (EDT)
To: User Raymond <raymond@one.com.au>
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: newbie installation question on Alpha Server 1000
In-Reply-To: <200007111342.XAA39132@gw.one.com.au>
References: <200007111342.XAA39132@gw.one.com.au>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid
Message-ID: <14699.9355.110436.792570@grasshopper.cs.duke.edu>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
User Raymond writes:
> To: freebsd-alpha@FreeBSD.ORG
>
> Andrew Gallatin wrote:
> >
> > Please post the output of the SRM 'show conf' command. Please also
> > post the boot output from FreeBSD. It is helpful to use a serial
> > console to capture this output (you may also be able to scroll back in
> > a graphics console by hitting scroll-lock & using the pageup/pagedown
> > keys).
<snip>
> I'm sorry to have to say this Drew but Santiago already gave the version
> of FreeBSD in his initial message.
You might notice that I did not ask him for the version precisely
because he supplied it. I was merely restating the information that
we need in order to be able to help.
> Basically, 4.0-RELEASE isn't usable. It took me a month to get installed.
> My questions re "can't get anywhere without my init" went largely unanswered.
> After that month, I found it wouldn't run my app anyway (see Problem Report
> alpha/18808). No one seems that interested. I suggest you move the
> "alpha port" back into "under development".
Rather than being insulting, you might get better results if you
stated your problems more clearly.
As to alpha/18808, I'm afraid I don't understand the problem you're
having & cannot duplicate it. Perhaps if you were to ammend the
problem report with some sample code, somebody might be able to
address it.
Can tell me why I cannot duplicate the problem? Here's what I did:
Script started on Tue Jul 11 10:00:28 2000
tcsh 6.08.00 (Astron) 1998-10-02 (alpha-unknown-FreeBSD) options 8b,nls,dl,sm,rh,nd,color
setting up context sens completions....done
.aliases: No such file or directory.
gallatin has logged on ttyp0 from grasshopper
<DING!>vivaldi/gallatin:hacks>uname -srm
FreeBSD 4.0-RELEASE alpha
<10:00am>vivaldi/gallatin:hacks>cat unaligned.c
#include <stdio.h>
#include <stdlib.h>
static long
foo(long *i)
{
*i = 7;
printf("%ld\n", *i);
return(*i);
}
main ()
{
char hack[16];
foo(&hack[3]);
}
<10:00am>vivaldi/gallatin:hacks>make unaligned
cc -g unaligned.c -o unaligned
unaligned.c: In function `main':
unaligned.c:16: warning: passing arg 1 of `foo' from incompatible pointer type
<10:00am>vivaldi/gallatin:hacks>./unaligned
pid 27485 (unaligned): unaligned access: va=0x11ffb3bb pc=0x1200006c8 ra=0x120000744 op=stq
pid 27485 (unaligned): unaligned access: va=0x11ffb3bb pc=0x1200006d4 ra=0x120000744 op=ldq
7
pid 27485 (unaligned): unaligned access: va=0x11ffb3bb pc=0x1200006ec ra=0x1200006dc op=ldq
<10:00am>vivaldi/gallatin:hacks>uac
parent printing is on
parent fixup is on
parent sigbus is off
<10:00am>vivaldi/gallatin:hacks>uac -p
parent printing is off
parent fixup is on
parent sigbus is off
<10:00am>vivaldi/gallatin:hacks>./unaligned
7
<10:00am>vivaldi/gallatin:hacks>exit
exit
Script done on Tue Jul 11 10:01:01 2000
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Tue Jul 11 8: 4:56 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from mx1.thebiz.net (mx1.thebiz.net [216.238.0.20])
by hub.freebsd.org (Postfix) with SMTP id 1B6A337C03C
for <freebsd-alpha@FreeBSD.ORG>; Tue, 11 Jul 2000 08:04:53 -0700 (PDT)
(envelope-from maz@albany.net)
Received: (qmail 8841 invoked from network); 11 Jul 2000 11:04:49 -0400
Received: from mail2.thebiz.net (172.16.0.129)
by mx1.thebiz.net with SMTP; 11 Jul 2000 11:04:49 -0400
Received: (qmail 31997 invoked by uid 0); 11 Jul 2000 11:04:49 -0400
Received: from unknown (HELO mahatma) (216.238.1.20)
by mail.albany.net with SMTP; 11 Jul 2000 11:04:49 -0400
Message-ID: <000f01bfeb48$e1b4d300$1401eed8@mahatma>
From: "Matthew Zahorik" <maz@albany.net>
To: <freebsd-alpha@FreeBSD.ORG>
Subject: /dev/[u]random on Alphas?
Date: Tue, 11 Jul 2000 11:01:24 -0400
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
/dev/urandom and /dev/random don't work on Alpha boxes under FreeBSD
4.0-RELEASE
alpha/alpha/mem.c doesn't have the case 3 and case 4 in mmrw() that the i386
code does.
Is this a known problem/limitation, and is there a workaround?
Right now my SSL web servers are using fixed files as the random number
seed, rather than /dev/urandom. Not a great source of entropy.
- Matt
--
Matthew Zahorik Director of Systems and Networking - BiznessOnline.com
matt@thebiz.net President of AlbanyNet Inc. - a BiznessOnline subsidiary
maz@albany.net Voice: (518) 292-1001 Fax: (518) 626-0793
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Tue Jul 11 8:50:52 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from malkavian.org (malkavian.org [206.136.132.23])
by hub.freebsd.org (Postfix) with ESMTP id 143EE37BEB5
for <freebsd-alpha@FreeBSD.ORG>; Tue, 11 Jul 2000 08:50:49 -0700 (PDT)
(envelope-from rbw@myplace.org)
Received: from localhost (rbw@localhost [127.0.0.1])
by malkavian.org (8.9.3/8.9.3) with ESMTP id LAA41155;
Tue, 11 Jul 2000 11:50:38 -0400 (EDT)
(envelope-from rbw@myplace.org)
Date: Tue, 11 Jul 2000 08:50:38 -0700 (MST)
From: "brian j. peterson" <rbw@myplace.org>
To: Matthew Zahorik <maz@albany.net>
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: /dev/[u]random on Alphas?
In-Reply-To: <000f01bfeb48$e1b4d300$1401eed8@mahatma>
Message-ID: <Pine.BSF.4.21.0007110838500.1652-100000@malkavian.org>
X-Prime: (2 ^ 6972593) - 1
X-URL: http://rbw.myplace.org/
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Tue, 11 Jul 2000, Matthew Zahorik wrote:
# /dev/urandom and /dev/random don't work on Alpha boxes under FreeBSD
# 4.0-RELEASE
#
# alpha/alpha/mem.c doesn't have the case 3 and case 4 in mmrw() that the i386
# code does.
#
# Is this a known problem/limitation, and is there a workaround?
#
# Right now my SSL web servers are using fixed files as the random number
# seed, rather than /dev/urandom. Not a great source of entropy.
forgive the length of this url, but here is the FreeBSD Security Advisory
on the matter:
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=17867+0+archive/2000/freebsd-security/20000618.freebsd-security
for some reason, it wasn't listed at http://www.freebsd.org/security/#adv .
-brian
--
--===-----=======-----------=============-----------------===================
| rbw aka bjp | god's final message to his creation: |
| rbw@myplace.org | we apologize for the inconvenience. |
===================-----------------=============-----------=======-----===--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Tue Jul 11 8:57:40 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from plato.phy.ohiou.edu (plato.phy.ohiou.edu [132.235.24.25])
by hub.freebsd.org (Postfix) with ESMTP id F240E37C0B2
for <freebsd-alpha@FreeBSD.ORG>; Tue, 11 Jul 2000 08:57:37 -0700 (PDT)
(envelope-from cfulton@plato.phy.ohiou.edu)
Received: from plato.phy.ohiou.edu (plato.phy.ohiou.edu [132.235.24.25])
by plato.phy.ohiou.edu (8.9.1/8.9.1) with SMTP id LAA24382
for <freebsd-alpha@FreeBSD.ORG>; Tue, 11 Jul 2000 11:55:32 -0400 (EDT)
Date: Tue, 11 Jul 2000 11:55:32 -0400 (EDT)
From: Charles Fulton <cfulton@plato.phy.ohiou.edu>
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Broken reboot
In-Reply-To: <000f01bfeb48$e1b4d300$1401eed8@mahatma>
Message-ID: <Pine.SOL.3.96.1000711115002.23094E-100000@plato.phy.ohiou.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
I've got 3.4-Release on an EB164 333 that when I issue a reboot command I
get a halt on console with machine code 660.
It's not often that it get's restarted anyway but it would be nice to know
what it means. I have the SRM user manual and the EB164 manual but
they're no help.
Charlie
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Tue Jul 11 9: 5:49 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
by hub.freebsd.org (Postfix) with ESMTP id 7181737B57F
for <freebsd-alpha@FreeBSD.ORG>; Tue, 11 Jul 2000 09:05:40 -0700 (PDT)
(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id MAA04551;
Tue, 11 Jul 2000 12:05:39 -0400 (EDT)
Received: (from gallatin@localhost)
by grasshopper.cs.duke.edu (8.9.3/8.9.1) id MAA28070;
Tue, 11 Jul 2000 12:05:38 -0400 (EDT)
(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Tue, 11 Jul 2000 12:05:38 -0400 (EDT)
To: Charles Fulton <cfulton@plato.phy.ohiou.edu>
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: Broken reboot
In-Reply-To: <Pine.SOL.3.96.1000711115002.23094E-100000@plato.phy.ohiou.edu>
References: <000f01bfeb48$e1b4d300$1401eed8@mahatma>
<Pine.SOL.3.96.1000711115002.23094E-100000@plato.phy.ohiou.edu>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid
Message-ID: <14699.17539.189844.549036@grasshopper.cs.duke.edu>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Charles Fulton writes:
> I've got 3.4-Release on an EB164 333 that when I issue a reboot command I
> get a halt on console with machine code 660.
>
> It's not often that it get's restarted anyway but it would be nice to know
> what it means. I have the SRM user manual and the EB164 manual but
> they're no help.
>
> Charlie
I'm a little unclear on exacly what you're seeing. Do you see
something like "panic: machine check" and then the 660? Is the
message coming from FreeBSD or from the SRM?
At any rate, you might try upgrading the firmware to the lastest you
can get your hands on (that solves some problems with the console
being unusable after a halt & might fix problems with rebooting).
Also, when 4.1 comes out, you should really consider upgrading. There
have been countless bugfixes & features added since 3.x
Drew
------------------------------------------------------------------------------
Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin
Duke University Email: gallatin@cs.duke.edu
Department of Computer Science Phone: (919) 660-6590
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Tue Jul 11 9:43:49 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from mx1.thebiz.net (mx1.thebiz.net [216.238.0.20])
by hub.freebsd.org (Postfix) with SMTP id 0B05137B533
for <freebsd-alpha@FreeBSD.ORG>; Tue, 11 Jul 2000 09:43:46 -0700 (PDT)
(envelope-from maz@albany.net)
Received: (qmail 32745 invoked from network); 11 Jul 2000 12:43:44 -0400
Received: from mail2.thebiz.net (172.16.0.129)
by mx1.thebiz.net with SMTP; 11 Jul 2000 12:43:44 -0400
Received: (qmail 2115 invoked by uid 0); 11 Jul 2000 12:43:43 -0400
Received: from unknown (HELO mahatma) (216.238.1.20)
by mail.albany.net with SMTP; 11 Jul 2000 12:43:43 -0400
Message-ID: <00f801bfeb56$b2aa18f0$1401eed8@mahatma>
From: "Matthew Zahorik" <maz@albany.net>
To: <freebsd-alpha@FreeBSD.ORG>
References: <Pine.BSF.4.21.0007110838500.1652-100000@malkavian.org>
Subject: Re: /dev/[u]random on Alphas?
Date: Tue, 11 Jul 2000 12:40:18 -0400
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
:
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=17867+0+archive/2000/freebsd-se
curity/20000618.freebsd-security
Ah, thanks. Thankfully the keys were generated on a different architecture.
I'll apply the diffs and recompile.
- Matt
--
Matthew Zahorik Director of Systems and Networking - BiznessOnline.com
matt@thebiz.net President of AlbanyNet Inc. - a BiznessOnline subsidiary
maz@albany.net Voice: (518) 292-1001 Fax: (518) 626-0793
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Tue Jul 11 10: 7: 7 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from plato.phy.ohiou.edu (plato.phy.ohiou.edu [132.235.24.25])
by hub.freebsd.org (Postfix) with ESMTP id B7A6837C054
for <freebsd-alpha@FreeBSD.ORG>; Tue, 11 Jul 2000 10:06:59 -0700 (PDT)
(envelope-from cfulton@plato.phy.ohiou.edu)
Received: from plato.phy.ohiou.edu (plato.phy.ohiou.edu [132.235.24.25])
by plato.phy.ohiou.edu (8.9.1/8.9.1) with SMTP id NAA24908
for <freebsd-alpha@FreeBSD.ORG>; Tue, 11 Jul 2000 13:04:52 -0400 (EDT)
Date: Tue, 11 Jul 2000 13:04:52 -0400 (EDT)
From: Charles Fulton <cfulton@plato.phy.ohiou.edu>
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: Broken reboot
In-Reply-To: <14699.17539.189844.549036@grasshopper.cs.duke.edu>
Message-ID: <Pine.SOL.3.96.1000711124533.23094F-100000@plato.phy.ohiou.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
The error is coming from the SRM; the version is 4.8 (last one released
for EB164) The kernel exits fine, no complaints.
I also get a boot error if I do a halt. I assumed that this was normal
and due to the kernel saying it was a halt and stopping the auto_action
from happening. But it just complains and gives the SRM prompt and is
still usable. I can type 'boot' and it goes on its merry way.
I did notice when I flashed the SRM the first time that the debug monitor
says there is a bad checksum for both the SRM and the ARC ROM. The ARC
was fine before the SRM was added. I flashed it again with no change.
This is a 'full flash' board where both can be present and I haven't
touched the ARC image. Both seem to work though.
I tried to install 4.0-release but I was doing an FTP install and it
wouldn't fire up my DEC network card where 3.4 worked fine, hence I've got
3.4.
Charlie
On Tue, 11 Jul 2000, Andrew Gallatin wrote:
>
> > I've got 3.4-Release on an EB164 333 that when I issue a reboot command I
> > get a halt on console with machine code 660.
>
> I'm a little unclear on exacly what you're seeing. Do you see
> something like "panic: machine check" and then the 660? Is the
> message coming from FreeBSD or from the SRM?
>
> At any rate, you might try upgrading the firmware to the lastest you
> can get your hands on (that solves some problems with the console
> being unusable after a halt & might fix problems with rebooting).
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Tue Jul 11 10:48:42 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
by hub.freebsd.org (Postfix) with ESMTP id CAF1637B6C1
for <freebsd-alpha@FreeBSD.ORG>; Tue, 11 Jul 2000 10:48:35 -0700 (PDT)
(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA06830;
Tue, 11 Jul 2000 13:48:29 -0400 (EDT)
Received: (from gallatin@localhost)
by grasshopper.cs.duke.edu (8.9.3/8.9.1) id NAA28227;
Tue, 11 Jul 2000 13:48:29 -0400 (EDT)
(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Tue, 11 Jul 2000 13:48:29 -0400 (EDT)
To: Charles Fulton <cfulton@plato.phy.ohiou.edu>
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: Broken reboot
In-Reply-To: <Pine.SOL.3.96.1000711124533.23094F-100000@plato.phy.ohiou.edu>
References: <14699.17539.189844.549036@grasshopper.cs.duke.edu>
<Pine.SOL.3.96.1000711124533.23094F-100000@plato.phy.ohiou.edu>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid
Message-ID: <14699.23557.850328.913880@grasshopper.cs.duke.edu>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Charles Fulton writes:
> The error is coming from the SRM; the version is 4.8 (last one released
> for EB164) The kernel exits fine, no complaints.
As far as I know, the halt/reboot code is pretty platform independant.
Do other OSes reboot OK on this box?
> I also get a boot error if I do a halt. I assumed that this was normal
> and due to the kernel saying it was a halt and stopping the auto_action
> from happening. But it just complains and gives the SRM prompt and is
> still usable. I can type 'boot' and it goes on its merry way.
>
> I did notice when I flashed the SRM the first time that the debug monitor
> says there is a bad checksum for both the SRM and the ARC ROM. The ARC
> was fine before the SRM was added. I flashed it again with no change.
> This is a 'full flash' board where both can be present and I haven't
> touched the ARC image. Both seem to work though.
>
> I tried to install 4.0-release but I was doing an FTP install and it
> wouldn't fire up my DEC network card where 3.4 worked fine, hence I've got
> 3.4.
Is it a 21143 based card? Do you see 'de0' or 'dc0' on the console
when you boot 4.x? Please give 4.1 a try when it comes out (or any
snaps that happen before the release).
Cheers,
Drew
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Tue Jul 11 11:11:17 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from plato.phy.ohiou.edu (plato.phy.ohiou.edu [132.235.24.25])
by hub.freebsd.org (Postfix) with ESMTP id CEDC537B653
for <freebsd-alpha@freebsd.org>; Tue, 11 Jul 2000 11:11:14 -0700 (PDT)
(envelope-from cfulton@plato.phy.ohiou.edu)
Received: from plato.phy.ohiou.edu (plato.phy.ohiou.edu [132.235.24.25])
by plato.phy.ohiou.edu (8.9.1/8.9.1) with SMTP id OAA25390
for <freebsd-alpha@freebsd.org>; Tue, 11 Jul 2000 14:09:06 -0400 (EDT)
Date: Tue, 11 Jul 2000 14:09:06 -0400 (EDT)
From: Charles Fulton <cfulton@plato.phy.ohiou.edu>
To: freebsd-alpha@freebsd.org
Subject: Re: Broken reboot
In-Reply-To: <14699.23557.850328.913880@grasshopper.cs.duke.edu>
Message-ID: <Pine.SOL.3.96.1000711135438.25339A-100000@plato.phy.ohiou.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
> > The error is coming from the SRM; the version is 4.8 (last one released
> > for EB164) The kernel exits fine, no complaints.
>
> As far as I know, the halt/reboot code is pretty platform independant.
> Do other OSes reboot OK on this box?
I can't say about this... the only other OS that's been on it is Win2k...
and that was short lived once I got a hold of it. But I'm sure it's a
firmware issue though. I haven't felt quite right since that bad checksum
showed up for the ROM image so I'm curious what a code 660 means.
Would it matter that I used the ARC to flash the SRM console?
> Is it a 21143 based card? Do you see 'de0' or 'dc0' on the console
> when you boot 4.x? Please give 4.1 a try when it comes out (or any
> snaps that happen before the release).
I'm pretty sure it a 21043 based card. The install kernel does let me set
up de0 but it never finds the FTP. Is there a way to just give an IP
instead of selecting from the list? To see if it's just not finding the
nameserver.
Thanks,
Charlie
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Tue Jul 11 11:24: 3 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21])
by hub.freebsd.org (Postfix) with ESMTP id CE9A637B5F3
for <freebsd-alpha@freebsd.org>; Tue, 11 Jul 2000 11:23:51 -0700 (PDT)
(envelope-from wkb@freebie.demon.nl)
Received: from [212.238.54.101] (helo=freebie.demon.nl)
by post.mail.nl.demon.net with smtp (Exim 3.14 #4)
id 13C4gr-0005DI-00; Tue, 11 Jul 2000 18:23:29 +0000
Received: (from wkb@localhost)
by freebie.demon.nl (8.9.3/8.9.3) id UAA01446;
Tue, 11 Jul 2000 20:23:28 +0200 (CEST)
(envelope-from wkb)
Date: Tue, 11 Jul 2000 20:23:28 +0200
From: Wilko Bulte <wkb@freebie.demon.nl>
To: Charles Fulton <cfulton@plato.phy.ohiou.edu>
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: Broken reboot
Message-ID: <20000711202328.A1351@freebie.demon.nl>
Reply-To: wilko@FreeBSD.ORG
References: <14699.23557.850328.913880@grasshopper.cs.duke.edu> <Pine.SOL.3.96.1000711135438.25339A-100000@plato.phy.ohiou.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <Pine.SOL.3.96.1000711135438.25339A-100000@plato.phy.ohiou.edu>; from cfulton@plato.phy.ohiou.edu on Tue, Jul 11, 2000 at 02:09:06PM -0400
X-OS: FreeBSD 4.0-STABLE
X-PGP: finger wilko@freebsd.org
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Tue, Jul 11, 2000 at 02:09:06PM -0400, Charles Fulton wrote:
> > > The error is coming from the SRM; the version is 4.8 (last one released
> > > for EB164) The kernel exits fine, no complaints.
> >
> > As far as I know, the halt/reboot code is pretty platform independant.
> > Do other OSes reboot OK on this box?
>
> I can't say about this... the only other OS that's been on it is Win2k...
Win2K on Alpha?
> and that was short lived once I got a hold of it. But I'm sure it's a
> firmware issue though. I haven't felt quite right since that bad checksum
> showed up for the ROM image so I'm curious what a code 660 means.
>
> Would it matter that I used the ARC to flash the SRM console?
No, that is a valid way to do it.
> > Is it a 21143 based card? Do you see 'de0' or 'dc0' on the console
> > when you boot 4.x? Please give 4.1 a try when it comes out (or any
> > snaps that happen before the release).
>
> I'm pretty sure it a 21043 based card. The install kernel does let me set
> up de0 but it never finds the FTP. Is there a way to just give an IP
> instead of selecting from the list? To see if it's just not finding the
> nameserver.
SHOW CONF in the SRM will tell you what card/chip type it is.
--
Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try"
wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes Back
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Tue Jul 11 11:33:43 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from plato.phy.ohiou.edu (plato.phy.ohiou.edu [132.235.24.25])
by hub.freebsd.org (Postfix) with ESMTP id 65A3C37B639
for <freebsd-alpha@FreeBSD.ORG>; Tue, 11 Jul 2000 11:33:41 -0700 (PDT)
(envelope-from cfulton@plato.phy.ohiou.edu)
Received: from plato.phy.ohiou.edu (plato.phy.ohiou.edu [132.235.24.25])
by plato.phy.ohiou.edu (8.9.1/8.9.1) with SMTP id OAA25554
for <freebsd-alpha@FreeBSD.ORG>; Tue, 11 Jul 2000 14:31:34 -0400 (EDT)
Date: Tue, 11 Jul 2000 14:31:34 -0400 (EDT)
From: Charles Fulton <cfulton@plato.phy.ohiou.edu>
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: Broken reboot
In-Reply-To: <20000711202328.A1351@freebie.demon.nl>
Message-ID: <Pine.SOL.3.96.1000711142444.25339C-100000@plato.phy.ohiou.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Tue, 11 Jul 2000, Wilko Bulte wrote:
> > I can't say about this... the only other OS that's been on it is Win2k...
>
> Win2K on Alpha?
Yep, I blame the microsoft aquisition sticker on the side of it.
> SHOW CONF in the SRM will tell you what card/chip type it is.
I have it running headless right now but I can check this evening when I
can steal a monitor from one of the linux boxes. As I recall it's a
21043... either way though the kernel found it but didn't use it properly.
Is it possible to give an IP address to the FTP install or is the list as
far as it goes?
Charlie
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Tue Jul 11 11:36:11 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51])
by hub.freebsd.org (Postfix) with ESMTP id 8520937B808
for <freebsd-alpha@FreeBSD.ORG>; Tue, 11 Jul 2000 11:36:07 -0700 (PDT)
(envelope-from msmith@mass.osd.bsdi.com)
Received: from mass.osd.bsdi.com (localhost [127.0.0.1])
by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id LAA13432;
Tue, 11 Jul 2000 11:44:12 -0700 (PDT)
(envelope-from msmith@mass.osd.bsdi.com)
Message-Id: <200007111844.LAA13432@mass.osd.bsdi.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Charles Fulton <cfulton@plato.phy.ohiou.edu>
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: Broken reboot
In-reply-to: Your message of "Tue, 11 Jul 2000 14:31:34 EDT."
<Pine.SOL.3.96.1000711142444.25339C-100000@plato.phy.ohiou.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 11 Jul 2000 11:44:12 -0700
From: Mike Smith <msmith@freebsd.org>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
> Is it possible to give an IP address to the FTP install or is the list as
> far as it goes?
You can give it a URL containing an IP address, yes. Second entry on the
list lets you enter your own.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Tue Jul 11 11:39:14 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20])
by hub.freebsd.org (Postfix) with ESMTP id 6E2E937B5F0
for <freebsd-alpha@freebsd.org>; Tue, 11 Jul 2000 11:39:11 -0700 (PDT)
(envelope-from wkb@freebie.demon.nl)
Received: from [212.238.54.101] (helo=freebie.demon.nl)
by post.mail.nl.demon.net with smtp (Exim 3.14 #2)
id 13C4w1-0006vv-00; Tue, 11 Jul 2000 18:39:09 +0000
Received: (from wkb@localhost)
by freebie.demon.nl (8.9.3/8.9.3) id UAA01591;
Tue, 11 Jul 2000 20:39:08 +0200 (CEST)
(envelope-from wkb)
Date: Tue, 11 Jul 2000 20:39:08 +0200
From: Wilko Bulte <wkb@freebie.demon.nl>
To: Santiago Zapata <szapata@creatos.com.mx>
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: newbie installation question on Alpha Server 1000
Message-ID: <20000711203908.B1457@freebie.demon.nl>
Reply-To: wilko@FreeBSD.ORG
References: <396B3C49.6696EDE4@creatos.com.mx>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <396B3C49.6696EDE4@creatos.com.mx>; from szapata@creatos.com.mx on Tue, Jul 11, 2000 at 08:24:57AM -0700
X-OS: FreeBSD 4.0-STABLE
X-PGP: finger wilko@freebsd.org
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Tue, Jul 11, 2000 at 08:24:57AM -0700, Santiago Zapata wrote:
> I am trying to install 4.0-RELEASE on an AlphaServer 1000.
> I already downloaded the boot floppies, I even reach the initial
> installation screen when I boot from the floppies but my hard drive is
> not recognized
What is that harddisk connected to? The onboard SCSI controller of the
Alpha? What does the SRM console tell you when you type SHOW CONF
and SHOW DEV at the >>> prompt?
> I read about having to spin the hard drive to be recogized but I did not
> find how. I also read in the HARDWARE.TXT file that the kernel needs
> "options DEC_1000A" but I do not know how to do it at boot time
You don't have to, the install kernels are compiled with the necessary
support code (options FOO is a config/compile time thing).
Another question: is it an AlphaServer 1000 or an AlphaServer 1000A (note
the trailing A)
--
Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try"
wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes Back
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Tue Jul 11 11:40:39 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from plato.phy.ohiou.edu (plato.phy.ohiou.edu [132.235.24.25])
by hub.freebsd.org (Postfix) with ESMTP id A000437B6CF
for <freebsd-alpha@FreeBSD.ORG>; Tue, 11 Jul 2000 11:40:37 -0700 (PDT)
(envelope-from cfulton@plato.phy.ohiou.edu)
Received: from plato.phy.ohiou.edu (plato.phy.ohiou.edu [132.235.24.25])
by plato.phy.ohiou.edu (8.9.1/8.9.1) with SMTP id OAA25659
for <freebsd-alpha@FreeBSD.ORG>; Tue, 11 Jul 2000 14:38:31 -0400 (EDT)
Date: Tue, 11 Jul 2000 14:38:30 -0400 (EDT)
From: Charles Fulton <cfulton@plato.phy.ohiou.edu>
Cc: freebsd-alpha@FreeBSD.ORG
Subject: 4.0 ftp install was: [Broken reboot]
In-Reply-To: <200007111844.LAA13432@mass.osd.bsdi.com>
Message-ID: <Pine.SOL.3.96.1000711143526.25339D-100000@plato.phy.ohiou.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
> You can give it a URL containing an IP address, yes. Second entry on the
> list lets you enter your own.
Oops, must have skipped down to USA a little too fast; didn't even see
that one.
Thanks, I'll see if I can get 4.0 installed that way.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Tue Jul 11 11:48:14 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from marble.fbcc.com (ns2.fbcc.com [216.54.252.3])
by hub.freebsd.org (Postfix) with SMTP id B19C337B6C7
for <freebsd-alpha@FreeBSD.ORG>; Tue, 11 Jul 2000 11:48:06 -0700 (PDT)
(envelope-from king@sstar.com)
Received: (qmail 5264 invoked from network); 11 Jul 2000 18:50:48 -0000
Received: from unknown (HELO bluto.jimking.net) (216.54.255.8)
by ns2.fbcc.com with SMTP; 11 Jul 2000 18:50:48 -0000
Received: from jking (jking.lgc.com [134.132.75.164])
by bluto.jimking.net (8.9.3/8.9.3) with SMTP id NAA13695;
Tue, 11 Jul 2000 13:48:01 -0500 (CDT)
(envelope-from king@sstar.com)
Message-ID: <006f01bfeb68$8a9bb690$a44b8486@jking>
From: "Jim King" <king@sstar.com>
To: <wilko@FreeBSD.ORG>
Cc: <freebsd-alpha@FreeBSD.ORG>
References: <14699.23557.850328.913880@grasshopper.cs.duke.edu> <Pine.SOL.3.96.1000711135438.25339A-100000@plato.phy.ohiou.edu> <20000711202328.A1351@freebie.demon.nl>
Subject: Re: Broken reboot
Date: Tue, 11 Jul 2000 13:48:01 -0500
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Wilko Bulte wrote:
> On Tue, Jul 11, 2000 at 02:09:06PM -0400, Charles Fulton wrote:
> > > > The error is coming from the SRM; the version is 4.8 (last one
released
> > > > for EB164) The kernel exits fine, no complaints.
> > >
> > > As far as I know, the halt/reboot code is pretty platform independant.
> > > Do other OSes reboot OK on this box?
> >
> > I can't say about this... the only other OS that's been on it is
Win2k...
>
> Win2K on Alpha?
Up until the announcement from Compaq dropping NT support for Alpha,
Microsoft was shipping beta versions of Win2000 for Alpha. I think I still
have one of the CD's as a souvenir. Rumor had it that they were even doing
internal builds of the 64-bit Win2000 on Alpha.
Jim
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Tue Jul 11 12: 0:58 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from phy.ucsf.edu (phy.ucsf.edu [128.218.64.200])
by hub.freebsd.org (Postfix) with ESMTP id 8B98E37B653
for <freebsd-alpha@freebsd.org>; Tue, 11 Jul 2000 12:00:56 -0700 (PDT)
(envelope-from dkleinh@phy.ucsf.edu)
Received: from amadeus.ucsf.edu (dkleinh@amadeus.ucsf.edu [128.218.65.107])
by phy.ucsf.edu (8.10.1/8.10.1) with ESMTP id e6BJ0uk04544
for <freebsd-alpha@freebsd.org>; Tue, 11 Jul 2000 12:00:56 -0700 (PDT)
Received: from localhost by amadeus.ucsf.edu (8.8.6) id MAA17935; Tue, 11 Jul 2000 12:00:55 -0700 (PDT)
Date: Tue, 11 Jul 2000 12:00:53 -0700 (PDT)
From: Dirk Kleinhesselink <dkleinh@phy.ucsf.edu>
X-Sender: dkleinh@amadeus.ucsf.edu
To: freebsd-alpha@freebsd.org
Subject: Re: Broken reboot
In-Reply-To: <006f01bfeb68$8a9bb690$a44b8486@jking>
Message-ID: <Pine.OSF.3.95.1000711115736.17926A-100000@amadeus.ucsf.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Tue, 11 Jul 2000, Jim King wrote:
> Wilko Bulte wrote:
>
> > On Tue, Jul 11, 2000 at 02:09:06PM -0400, Charles Fulton wrote:
> > > > > The error is coming from the SRM; the version is 4.8 (last one
> released
> > > > > for EB164) The kernel exits fine, no complaints.
> > > >
> > > > As far as I know, the halt/reboot code is pretty platform independant.
> > > > Do other OSes reboot OK on this box?
> > >
> > > I can't say about this... the only other OS that's been on it is
> Win2k...
> >
> > Win2K on Alpha?
>
> Up until the announcement from Compaq dropping NT support for Alpha,
> Microsoft was shipping beta versions of Win2000 for Alpha. I think I still
> have one of the CD's as a souvenir. Rumor had it that they were even doing
> internal builds of the 64-bit Win2000 on Alpha.
Win2K for the alpha was even in release candidacy -- I had a subscription
to Microsoft Technet Plus that included beta software and I received the
beta 3 and release candidate 1 CDs for Win2000 Alpha.
Dirk
>
> Jim
>
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-alpha" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Tue Jul 11 12:13:52 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21])
by hub.freebsd.org (Postfix) with ESMTP
id 5068F37B6F1; Tue, 11 Jul 2000 12:13:46 -0700 (PDT)
(envelope-from wkb@freebie.demon.nl)
Received: from [212.238.54.101] (helo=freebie.demon.nl)
by post.mail.nl.demon.net with smtp (Exim 3.14 #4)
id 13C5TP-0006CD-00; Tue, 11 Jul 2000 19:13:39 +0000
Received: (from wkb@localhost)
by freebie.demon.nl (8.9.3/8.9.3) id VAA00392;
Tue, 11 Jul 2000 21:13:39 +0200 (CEST)
(envelope-from wkb)
Date: Tue, 11 Jul 2000 21:13:39 +0200
From: Wilko Bulte <wkb@freebie.demon.nl>
To: Jim King <king@sstar.com>
Cc: wilko@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG
Subject: Re: Broken reboot
Message-ID: <20000711211339.A378@freebie.demon.nl>
Reply-To: wilko@FreeBSD.ORG
References: <14699.23557.850328.913880@grasshopper.cs.duke.edu> <Pine.SOL.3.96.1000711135438.25339A-100000@plato.phy.ohiou.edu> <20000711202328.A1351@freebie.demon.nl> <006f01bfeb68$8a9bb690$a44b8486@jking>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <006f01bfeb68$8a9bb690$a44b8486@jking>; from king@sstar.com on Tue, Jul 11, 2000 at 01:48:01PM -0500
X-OS: FreeBSD 4.0-STABLE
X-PGP: finger wilko@freebsd.org
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Tue, Jul 11, 2000 at 01:48:01PM -0500, Jim King wrote:
> Wilko Bulte wrote:
>
> > On Tue, Jul 11, 2000 at 02:09:06PM -0400, Charles Fulton wrote:
> > > > > The error is coming from the SRM; the version is 4.8 (last one
> released
> > > > > for EB164) The kernel exits fine, no complaints.
> > > >
> > > > As far as I know, the halt/reboot code is pretty platform independant.
> > > > Do other OSes reboot OK on this box?
> > >
> > > I can't say about this... the only other OS that's been on it is
> Win2k...
> >
> > Win2K on Alpha?
>
> Up until the announcement from Compaq dropping NT support for Alpha,
> Microsoft was shipping beta versions of Win2000 for Alpha. I think I still
> have one of the CD's as a souvenir. Rumor had it that they were even doing
> internal builds of the 64-bit Win2000 on Alpha.
Ah, I was not aware of the fact there were betas out before we pulled the
plug on NT/alpha. Sorry, offtopic.
--
Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try"
wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes Back
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Wed Jul 12 9:53:33 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
by hub.freebsd.org (Postfix) with ESMTP id B74E237B5EB
for <freebsd-alpha@FreeBSD.ORG>; Wed, 12 Jul 2000 09:53:24 -0700 (PDT)
(envelope-from mjacob@feral.com)
Received: from semuta.feral.com (semuta [192.67.166.70])
by feral.com (8.9.3/8.9.3) with ESMTP id JAA05488;
Wed, 12 Jul 2000 09:53:22 -0700
Date: Wed, 12 Jul 2000 09:51:19 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Matthew Zahorik <maz@albany.net>
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: /dev/[u]random on Alphas?
In-Reply-To: <000f01bfeb48$e1b4d300$1401eed8@mahatma>
Message-ID: <Pine.BSF.4.05.10007120950090.2727-100000@semuta.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Tue, 11 Jul 2000, Matthew Zahorik wrote:
> /dev/urandom and /dev/random don't work on Alpha boxes under FreeBSD
> 4.0-RELEASE
>
> alpha/alpha/mem.c doesn't have the case 3 and case 4 in mmrw() that the i386
> code does.
>
> Is this a known problem/limitation, and is there a workaround?
>
> Right now my SSL web servers are using fixed files as the random number
> seed, rather than /dev/urandom. Not a great source of entropy.
I just checked the -stable branch, and the alpha code now has
/dev/random and /dev/urandom in mem.c (and in MAKEDEV).
So, 4.1 will have this or you can update to this via the usual means.
-matt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Wed Jul 12 14:17:26 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21])
by hub.freebsd.org (Postfix) with ESMTP
id 2196F37B6EE; Wed, 12 Jul 2000 14:17:22 -0700 (PDT)
(envelope-from wkb@freebie.demon.nl)
Received: from [212.238.54.101] (helo=freebie.demon.nl)
by post.mail.nl.demon.net with smtp (Exim 3.14 #4)
id 13CTse-000Azu-00; Wed, 12 Jul 2000 21:17:20 +0000
Received: (from wkb@localhost)
by freebie.demon.nl (8.9.3/8.9.3) id XAA02167;
Wed, 12 Jul 2000 23:17:00 +0200 (CEST)
(envelope-from wkb)
Date: Wed, 12 Jul 2000 23:17:00 +0200
From: Wilko Bulte <wkb@freebie.demon.nl>
To: freebsd-alpha@freebsd.org, freebsd-current@freebsd.org
Subject: unaligned access fault panic during boot?
Message-ID: <20000712231700.A2143@freebie.demon.nl>
Reply-To: wilko@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
X-OS: FreeBSD 4.0-STABLE
X-PGP: finger wilko@freebsd.org
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Using a freshly supped -current source tree (2 hours ago) I'm getting a panic on
boot:
trap entry = 0x4 (unaligned access fault)
a0 = 0xfffffc0000590a33
a1 = 0x2c
a2 = 0x2
pc = 0xfffffc00003a970c
ra = 0xfffffc00003a96b8
curproc = 0
This is a Miata GL 600ua. Anybody else seeing this ? I had hoped to build a
release overnight to (hopefully) be able to test Lynx support.
Wilko
--
Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try"
wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes Back
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Wed Jul 12 14:28: 0 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
by hub.freebsd.org (Postfix) with ESMTP
id D827237BE50; Wed, 12 Jul 2000 14:27:56 -0700 (PDT)
(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA13464;
Wed, 12 Jul 2000 17:27:56 -0400 (EDT)
Received: (from gallatin@localhost)
by grasshopper.cs.duke.edu (8.9.3/8.9.1) id RAA30704;
Wed, 12 Jul 2000 17:27:56 -0400 (EDT)
(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 12 Jul 2000 17:27:56 -0400 (EDT)
To: wilko@freebsd.org
Cc: freebsd-alpha@freebsd.org
Subject: Re: unaligned access fault panic during boot?
In-Reply-To: <20000712231700.A2143@freebie.demon.nl>
References: <20000712231700.A2143@freebie.demon.nl>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid
Message-ID: <14700.58027.671131.446614@grasshopper.cs.duke.edu>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Wilko Bulte writes:
> Using a freshly supped -current source tree (2 hours ago) I'm getting a panic on
> boot:
> trap entry = 0x4 (unaligned access fault)
> a0 = 0xfffffc0000590a33
> a1 = 0x2c
> a2 = 0x2
> pc = 0xfffffc00003a970c
> ra = 0xfffffc00003a96b8
> curproc = 0
>
> This is a Miata GL 600ua. Anybody else seeing this ? I had hoped to build a
> release overnight to (hopefully) be able to test Lynx support.
The obvious question is what functions do the pc & ra map to?
Drew
------------------------------------------------------------------------------
Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin
Duke University Email: gallatin@cs.duke.edu
Department of Computer Science Phone: (919) 660-6590
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Wed Jul 12 14:29:57 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
by hub.freebsd.org (Postfix) with ESMTP
id 1B4FA37BE50; Wed, 12 Jul 2000 14:29:55 -0700 (PDT)
(envelope-from mjacob@feral.com)
Received: from semuta.feral.com (semuta [192.67.166.70])
by feral.com (8.9.3/8.9.3) with ESMTP id OAA06777;
Wed, 12 Jul 2000 14:29:53 -0700
Date: Wed, 12 Jul 2000 14:27:49 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Andrew Gallatin <gallatin@cs.duke.edu>
Cc: wilko@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG
Subject: Re: unaligned access fault panic during boot?
In-Reply-To: <14700.58027.671131.446614@grasshopper.cs.duke.edu>
Message-ID: <Pine.BSF.4.05.10007121427430.2727-100000@semuta.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
For me, it was ohci_root_ctrl_start
On Wed, 12 Jul 2000, Andrew Gallatin wrote:
>
> Wilko Bulte writes:
> > Using a freshly supped -current source tree (2 hours ago) I'm getting a panic on
> > boot:
> > trap entry = 0x4 (unaligned access fault)
> > a0 = 0xfffffc0000590a33
> > a1 = 0x2c
> > a2 = 0x2
> > pc = 0xfffffc00003a970c
> > ra = 0xfffffc00003a96b8
> > curproc = 0
> >
> > This is a Miata GL 600ua. Anybody else seeing this ? I had hoped to build a
> > release overnight to (hopefully) be able to test Lynx support.
>
> The obvious question is what functions do the pc & ra map to?
>
> Drew
> ------------------------------------------------------------------------------
> Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin
> Duke University Email: gallatin@cs.duke.edu
> Department of Computer Science Phone: (919) 660-6590
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-alpha" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Wed Jul 12 14:40:58 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20])
by hub.freebsd.org (Postfix) with ESMTP
id 0DBD637BE50; Wed, 12 Jul 2000 14:40:50 -0700 (PDT)
(envelope-from wkb@freebie.demon.nl)
Received: from [212.238.54.101] (helo=freebie.demon.nl)
by post.mail.nl.demon.net with smtp (Exim 3.14 #2)
id 13CUFM-0005DE-00; Wed, 12 Jul 2000 21:40:48 +0000
Received: (from wkb@localhost)
by freebie.demon.nl (8.9.3/8.9.3) id XAA02598;
Wed, 12 Jul 2000 23:40:44 +0200 (CEST)
(envelope-from wkb)
Date: Wed, 12 Jul 2000 23:40:44 +0200
From: Wilko Bulte <wkb@freebie.demon.nl>
To: Matthew Jacob <mjacob@feral.com>
Cc: Andrew Gallatin <gallatin@cs.duke.edu>, wilko@freebsd.org,
freebsd-alpha@freebsd.org
Subject: Re: unaligned access fault panic during boot?
Message-ID: <20000712234044.C2459@freebie.demon.nl>
Reply-To: wilko@freebsd.org
References: <14700.58027.671131.446614@grasshopper.cs.duke.edu> <Pine.BSF.4.05.10007121427430.2727-100000@semuta.feral.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <Pine.BSF.4.05.10007121427430.2727-100000@semuta.feral.com>; from mjacob@feral.com on Wed, Jul 12, 2000 at 02:27:49PM -0700
X-OS: FreeBSD 4.0-STABLE
X-PGP: finger wilko@freebsd.org
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Wed, Jul 12, 2000 at 02:27:49PM -0700, Matthew Jacob wrote:
>
> For me, it was ohci_root_ctrl_start
Meaning: I'm not alone?
>
>
> On Wed, 12 Jul 2000, Andrew Gallatin wrote:
>
> >
> > Wilko Bulte writes:
> > > Using a freshly supped -current source tree (2 hours ago) I'm getting a panic on
> > > boot:
> > > trap entry = 0x4 (unaligned access fault)
> > > a0 = 0xfffffc0000590a33
> > > a1 = 0x2c
> > > a2 = 0x2
> > > pc = 0xfffffc00003a970c
> > > ra = 0xfffffc00003a96b8
> > > curproc = 0
> > >
> > > This is a Miata GL 600ua. Anybody else seeing this ? I had hoped to build a
> > > release overnight to (hopefully) be able to test Lynx support.
> >
> > The obvious question is what functions do the pc & ra map to?
nm on the kernel says:
fffffc00005245fc t Lret_result
fffffc00004e892c t Lsavectx1
fffffc00003a50c0 T MD5Final
fffffc00003a4e80 T MD5Init
fffffc00003a5020 T MD5Pad
fffffc00003a5140 T MD5Transform
fffffc00003a4ec0 T MD5Update
fffffc0000550490 D M_ACCF
fffffc00005504e0 d M_ACCF_init_sys_init
Does this make any sense?
--
Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try"
wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes Back
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Wed Jul 12 14:44:56 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
by hub.freebsd.org (Postfix) with ESMTP
id 90D7737C2CD; Wed, 12 Jul 2000 14:44:53 -0700 (PDT)
(envelope-from mjacob@feral.com)
Received: from semuta.feral.com (semuta [192.67.166.70])
by feral.com (8.9.3/8.9.3) with ESMTP id OAA06856;
Wed, 12 Jul 2000 14:44:53 -0700
Date: Wed, 12 Jul 2000 14:42:49 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: wilko@freebsd.org
Cc: Andrew Gallatin <gallatin@cs.duke.edu>, freebsd-alpha@freebsd.org
Subject: Re: unaligned access fault panic during boot?
In-Reply-To: <20000712234044.C2459@freebie.demon.nl>
Message-ID: <Pine.BSF.4.05.10007121442300.2727-100000@semuta.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
> Meaning: I'm not alone?
No, just comparing with a Generic kernel..
>
> >
> >
> > On Wed, 12 Jul 2000, Andrew Gallatin wrote:
> >
> > >
> > > Wilko Bulte writes:
> > > > Using a freshly supped -current source tree (2 hours ago) I'm getting a panic on
> > > > boot:
> > > > trap entry = 0x4 (unaligned access fault)
> > > > a0 = 0xfffffc0000590a33
> > > > a1 = 0x2c
> > > > a2 = 0x2
> > > > pc = 0xfffffc00003a970c
> > > > ra = 0xfffffc00003a96b8
> > > > curproc = 0
> > > >
> > > > This is a Miata GL 600ua. Anybody else seeing this ? I had hoped to build a
> > > > release overnight to (hopefully) be able to test Lynx support.
> > >
> > > The obvious question is what functions do the pc & ra map to?
>
> nm on the kernel says:
>
> fffffc00005245fc t Lret_result
> fffffc00004e892c t Lsavectx1
> fffffc00003a50c0 T MD5Final
> fffffc00003a4e80 T MD5Init
> fffffc00003a5020 T MD5Pad
> fffffc00003a5140 T MD5Transform
> fffffc00003a4ec0 T MD5Update
> fffffc0000550490 D M_ACCF
> fffffc00005504e0 d M_ACCF_init_sys_init
>
> Does this make any sense?
Are you loading randomdev?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Wed Jul 12 14:58:40 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20])
by hub.freebsd.org (Postfix) with ESMTP
id 0001537BCEB; Wed, 12 Jul 2000 14:58:32 -0700 (PDT)
(envelope-from wkb@freebie.demon.nl)
Received: from [212.238.54.101] (helo=freebie.demon.nl)
by post.mail.nl.demon.net with smtp (Exim 3.14 #2)
id 13CUWU-0005Rp-00; Wed, 12 Jul 2000 21:58:31 +0000
Received: (from wkb@localhost)
by freebie.demon.nl (8.9.3/8.9.3) id XAA02787;
Wed, 12 Jul 2000 23:58:30 +0200 (CEST)
(envelope-from wkb)
Date: Wed, 12 Jul 2000 23:58:30 +0200
From: Wilko Bulte <wkb@freebie.demon.nl>
To: Matthew Jacob <mjacob@feral.com>
Cc: wilko@freebsd.org, Andrew Gallatin <gallatin@cs.duke.edu>,
freebsd-alpha@freebsd.org
Subject: Re: unaligned access fault panic during boot?
Message-ID: <20000712235830.B2745@freebie.demon.nl>
Reply-To: wilko@freebsd.org
References: <20000712234044.C2459@freebie.demon.nl> <Pine.BSF.4.05.10007121442300.2727-100000@semuta.feral.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <Pine.BSF.4.05.10007121442300.2727-100000@semuta.feral.com>; from mjacob@feral.com on Wed, Jul 12, 2000 at 02:42:49PM -0700
X-OS: FreeBSD 4.0-STABLE
X-PGP: finger wilko@freebsd.org
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Wed, Jul 12, 2000 at 02:42:49PM -0700, Matthew Jacob wrote:
>
> > Meaning: I'm not alone?
>
> No, just comparing with a Generic kernel..
Ah, OK.
> > > > > release overnight to (hopefully) be able to test Lynx support.
> > > >
> > > > The obvious question is what functions do the pc & ra map to?
> >
> > nm on the kernel says:
> >
> > fffffc00005245fc t Lret_result
> > fffffc00004e892c t Lsavectx1
> > fffffc00003a50c0 T MD5Final
> > fffffc00003a4e80 T MD5Init
> > fffffc00003a5020 T MD5Pad
> > fffffc00003a5140 T MD5Transform
> > fffffc00003a4ec0 T MD5Update
> > fffffc0000550490 D M_ACCF
> > fffffc00005504e0 d M_ACCF_init_sys_init
> >
> > Does this make any sense?
>
> Are you loading randomdev?
The config file has:
options RANDOMDEV #entropy device
I assume this should be sufficient?
--
Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try"
wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes Back
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Wed Jul 12 15: 2:38 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
by hub.freebsd.org (Postfix) with ESMTP
id 85E3B37C090; Wed, 12 Jul 2000 15:02:33 -0700 (PDT)
(envelope-from mjacob@feral.com)
Received: from semuta.feral.com (semuta [192.67.166.70])
by feral.com (8.9.3/8.9.3) with ESMTP id PAA06936;
Wed, 12 Jul 2000 15:02:30 -0700
Date: Wed, 12 Jul 2000 15:00:27 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: wilko@freebsd.org
Cc: Andrew Gallatin <gallatin@cs.duke.edu>, freebsd-alpha@freebsd.org
Subject: Re: unaligned access fault panic during boot?
In-Reply-To: <20000712235830.B2745@freebie.demon.nl>
Message-ID: <Pine.BSF.4.05.10007121500160.2727-100000@semuta.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
>
> The config file has:
>
> options RANDOMDEV #entropy device
>
> I assume this should be sufficient?
Hmm, yes, I would think..
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Wed Jul 12 18:51:37 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from june.cs.washington.edu (june.cs.washington.edu [128.95.1.4])
by hub.freebsd.org (Postfix) with ESMTP id 13EEB37B521
for <freebsd-alpha@freebsd.org>; Wed, 12 Jul 2000 18:51:21 -0700 (PDT)
(envelope-from wolman@cs.washington.edu)
Received: from miles.cs.washington.edu (miles.cs.washington.edu [128.95.4.177])
by june.cs.washington.edu (8.9.3/8.9.3/0.3j) with ESMTP id SAA69649
for <freebsd-alpha@freebsd.org>; Wed, 12 Jul 2000 18:51:15 -0700 (PDT)
(envelope-from wolman@cs.washington.edu)
Received: from miles.cs.washington.edu (localhost [127.0.0.1])
by miles.cs.washington.edu (8.9.3/8.9.3) with ESMTP id SAA25627
for <freebsd-alpha@freebsd.org>; Wed, 12 Jul 2000 18:51:14 -0700 (PDT)
(envelope-from wolman@miles.cs.washington.edu)
Message-Id: <200007130151.SAA25627@miles.cs.washington.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: freebsd-alpha@freebsd.org
Subject: warning: received processor correctable error message
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 12 Jul 2000 18:51:14 -0700
From: "Alec Wolman" <wolman@cs.washington.edu>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
I've got an XP1000 running 4.0-STABLE from around June 18th, and
I get the following error message listed a few times on the console:
Warning: received processor correctable error.
Warning: received processor correctable error.
Warning: received processor correctable error.
Is this likely to be a hardware problem?
Alec
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Wed Jul 12 19: 6: 9 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
by hub.freebsd.org (Postfix) with ESMTP id E2ED237C0EC
for <freebsd-alpha@FreeBSD.ORG>; Wed, 12 Jul 2000 19:06:01 -0700 (PDT)
(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id WAA20025;
Wed, 12 Jul 2000 22:05:58 -0400 (EDT)
Received: (from gallatin@localhost)
by grasshopper.cs.duke.edu (8.9.3/8.9.1) id WAA31133;
Wed, 12 Jul 2000 22:05:58 -0400 (EDT)
(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 12 Jul 2000 22:05:58 -0400 (EDT)
To: "Alec Wolman" <wolman@cs.washington.edu>
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: warning: received processor correctable error message
In-Reply-To: <200007130151.SAA25627@miles.cs.washington.edu>
References: <200007130151.SAA25627@miles.cs.washington.edu>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid
Message-ID: <14701.9102.36017.419004@grasshopper.cs.duke.edu>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Alec Wolman writes:
>
> I've got an XP1000 running 4.0-STABLE from around June 18th, and
> I get the following error message listed a few times on the console:
>
> Warning: received processor correctable error.
> Warning: received processor correctable error.
> Warning: received processor correctable error.
>
> Is this likely to be a hardware problem?
Yes. Most likely its telling you it corrected memory error, but it
could be other things too. Is it properly cooled?
I think I may have the docs for decoding these on the tsunami.. I
should probably write some code to give a more meaningful message.
Drew
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Wed Jul 12 19:13:19 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from june.cs.washington.edu (june.cs.washington.edu [128.95.1.4])
by hub.freebsd.org (Postfix) with ESMTP id E1E2B37B67C
for <freebsd-alpha@FreeBSD.ORG>; Wed, 12 Jul 2000 19:13:10 -0700 (PDT)
(envelope-from wolman@cs.washington.edu)
Received: from miles.cs.washington.edu (miles.cs.washington.edu [128.95.4.177])
by june.cs.washington.edu (8.9.3/8.9.3/0.3j) with ESMTP id TAA70351;
Wed, 12 Jul 2000 19:12:24 -0700 (PDT)
(envelope-from wolman@cs.washington.edu)
Received: from miles.cs.washington.edu (localhost [127.0.0.1])
by miles.cs.washington.edu (8.9.3/8.9.3) with ESMTP id TAA25730;
Wed, 12 Jul 2000 19:12:20 -0700 (PDT)
(envelope-from wolman@miles.cs.washington.edu)
Message-Id: <200007130212.TAA25730@miles.cs.washington.edu>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Andrew Gallatin <gallatin@cs.duke.edu>
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: warning: received processor correctable error message
In-Reply-To: Message from Andrew Gallatin <gallatin@cs.duke.edu>
of "Wed, 12 Jul 2000 22:05:58 EDT." <14701.9102.36017.419004@grasshopper.cs.duke.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 12 Jul 2000 19:12:20 -0700
From: "Alec Wolman" <wolman@cs.washington.edu>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
> Alec Wolman writes:
> >
> > I've got an XP1000 running 4.0-STABLE from around June 18th, and
> > I get the following error message listed a few times on the console:
> >
> > Warning: received processor correctable error.
> > Warning: received processor correctable error.
> > Warning: received processor correctable error.
> >
> > Is this likely to be a hardware problem?
>
> Yes. Most likely its telling you it corrected memory error, but it
> could be other things too. Is it properly cooled?
Yes, its in an air conditioned room with good airflow around it.
If it is a memory error, will there be any way to detect which SIMM?
It seems to be quite infrequent.
Alec
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Wed Jul 12 19:21:57 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
by hub.freebsd.org (Postfix) with ESMTP id 9C04E37B67C
for <freebsd-alpha@FreeBSD.ORG>; Wed, 12 Jul 2000 19:21:54 -0700 (PDT)
(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id WAA20251;
Wed, 12 Jul 2000 22:21:53 -0400 (EDT)
Received: (from gallatin@localhost)
by grasshopper.cs.duke.edu (8.9.3/8.9.1) id WAA31158;
Wed, 12 Jul 2000 22:21:53 -0400 (EDT)
(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 12 Jul 2000 22:21:53 -0400 (EDT)
To: "Alec Wolman" <wolman@cs.washington.edu>
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: warning: received processor correctable error message
In-Reply-To: <200007130212.TAA25730@miles.cs.washington.edu>
References: <gallatin@cs.duke.edu>
<14701.9102.36017.419004@grasshopper.cs.duke.edu>
<200007130212.TAA25730@miles.cs.washington.edu>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid
Message-ID: <14701.10036.523075.203941@grasshopper.cs.duke.edu>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Alec Wolman writes:
>
> If it is a memory error, will there be any way to detect which SIMM?
I don't know.
> It seems to be quite infrequent.
In that case, I wouldn't worry about it.. I've got a few AlphaStation
500s that spit out 4-5 of these per month with no apparent ill effects.
Drew
------------------------------------------------------------------------------
Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin
Duke University Email: gallatin@cs.duke.edu
Department of Computer Science Phone: (919) 660-6590
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Wed Jul 12 23:22:43 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20])
by hub.freebsd.org (Postfix) with ESMTP id 352CE37B9E0
for <freebsd-alpha@freebsd.org>; Wed, 12 Jul 2000 23:22:41 -0700 (PDT)
(envelope-from wkb@freebie.demon.nl)
Received: from [212.238.54.101] (helo=freebie.demon.nl)
by post.mail.nl.demon.net with smtp (Exim 3.14 #2)
id 13CcOL-00018I-00; Thu, 13 Jul 2000 06:22:37 +0000
Received: (from wkb@localhost)
by freebie.demon.nl (8.9.3/8.9.3) id IAA04837;
Thu, 13 Jul 2000 08:22:37 +0200 (CEST)
(envelope-from wkb)
Date: Thu, 13 Jul 2000 08:22:37 +0200
From: Wilko Bulte <wkb@freebie.demon.nl>
To: Alec Wolman <wolman@cs.washington.edu>
Cc: freebsd-alpha@freebsd.org
Subject: Re: warning: received processor correctable error message
Message-ID: <20000713082237.A4271@freebie.demon.nl>
Reply-To: wilko@freebsd.org
References: <200007130151.SAA25627@miles.cs.washington.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <200007130151.SAA25627@miles.cs.washington.edu>; from wolman@cs.washington.edu on Wed, Jul 12, 2000 at 06:51:14PM -0700
X-OS: FreeBSD 4.0-STABLE
X-PGP: finger wilko@freebsd.org
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Wed, Jul 12, 2000 at 06:51:14PM -0700, Alec Wolman wrote:
>
> I've got an XP1000 running 4.0-STABLE from around June 18th, and
> I get the following error message listed a few times on the console:
>
> Warning: received processor correctable error.
> Warning: received processor correctable error.
> Warning: received processor correctable error.
>
> Is this likely to be a hardware problem?
Yes. But if it just occurs very seldom I would not worry about it. Probably
the ECC of the memory doing what it is designed to do.
--
Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try"
wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes Back
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Wed Jul 12 23:24:17 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21])
by hub.freebsd.org (Postfix) with ESMTP id DADEB37B572
for <freebsd-alpha@freebsd.org>; Wed, 12 Jul 2000 23:24:14 -0700 (PDT)
(envelope-from wkb@freebie.demon.nl)
Received: from [212.238.54.101] (helo=freebie.demon.nl)
by post.mail.nl.demon.net with smtp (Exim 3.14 #4)
id 13CcPt-000Fe8-00; Thu, 13 Jul 2000 06:24:13 +0000
Received: (from wkb@localhost)
by freebie.demon.nl (8.9.3/8.9.3) id IAA04847;
Thu, 13 Jul 2000 08:24:13 +0200 (CEST)
(envelope-from wkb)
Date: Thu, 13 Jul 2000 08:24:13 +0200
From: Wilko Bulte <wkb@freebie.demon.nl>
To: Andrew Gallatin <gallatin@cs.duke.edu>
Cc: Alec Wolman <wolman@cs.washington.edu>, freebsd-alpha@freebsd.org
Subject: Re: warning: received processor correctable error message
Message-ID: <20000713082413.B4271@freebie.demon.nl>
Reply-To: wilko@freebsd.org
References: <gallatin@cs.duke.edu> <14701.9102.36017.419004@grasshopper.cs.duke.edu> <200007130212.TAA25730@miles.cs.washington.edu> <14701.10036.523075.203941@grasshopper.cs.duke.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <14701.10036.523075.203941@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, Jul 12, 2000 at 10:21:53PM -0400
X-OS: FreeBSD 4.0-STABLE
X-PGP: finger wilko@freebsd.org
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Wed, Jul 12, 2000 at 10:21:53PM -0400, Andrew Gallatin wrote:
>
> Alec Wolman writes:
> >
> > If it is a memory error, will there be any way to detect which SIMM?
>
> I don't know.
Yes there is. But not with FreeBSD AFAIK. DECevent used on the binary errlog
of Tru64 UNIX gives you enough info, when combined with the service manuals
of a machine, to determine which DIMM/SIMM is problematic.
--
Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try"
wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes Back
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Thu Jul 13 1:53:50 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from radius.city-guide.com (radius.cityisp.net [216.2.9.5])
by hub.freebsd.org (Postfix) with ESMTP
id 3C36137C32D; Thu, 13 Jul 2000 01:53:46 -0700 (PDT)
(envelope-from lynch@cityisp.net)
Received: from enitech (unverified [216.2.8.218]) by radius.city-guide.com
(Vircom SMTPRS 4.2.181) with SMTP id <B0006335296@radius.city-guide.com>;
Thu, 13 Jul 2000 05:04:58 -0400
Message-ID: <004f01bfeca8$244b78d0$da0802d8@CityGuide.com>
From: "Chris Lynch" <lynch@cityisp.net>
To: <freebsd-alpha@freebsd.org>
Cc: <newbies@FreeBSD.ORG>
Subject: First Time Alpha install
Date: Thu, 13 Jul 2000 04:55:44 -0400
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
I'm trying to install FreeBSD 4.0 on a DEC AlphaPC 164 LX. I've made two
floppies, but, since it doesn't automatically boot from the floppy, I'm not
sure what to put int the OS Selection Setup.
I've inserted a new OS call it FreeBSD, boot from A: kern.flp
I'm not sure what to pass the OS options. It has a nifty Install Windows NT
options...but , why? :)
thanks,
Chris
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Thu Jul 13 2:13:27 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from mass.osd.bsdi.com (adsl-63-193-112-57.dsl.snfc21.pacbell.net [63.193.112.57])
by hub.freebsd.org (Postfix) with ESMTP
id C0E1137C334; Thu, 13 Jul 2000 02:13:24 -0700 (PDT)
(envelope-from msmith@mass.osd.bsdi.com)
Received: from mass.osd.bsdi.com (localhost [127.0.0.1])
by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id CAA00886;
Thu, 13 Jul 2000 02:21:47 -0700 (PDT)
(envelope-from msmith@mass.osd.bsdi.com)
Message-Id: <200007130921.CAA00886@mass.osd.bsdi.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: "Chris Lynch" <lynch@cityisp.net>
Cc: freebsd-alpha@freebsd.org, newbies@freebsd.org
Subject: Re: First Time Alpha install
In-reply-to: Your message of "Thu, 13 Jul 2000 04:55:44 EDT."
<004f01bfeca8$244b78d0$da0802d8@CityGuide.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 13 Jul 2000 02:21:47 -0700
From: Mike Smith <msmith@freebsd.org>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
> I'm trying to install FreeBSD 4.0 on a DEC AlphaPC 164 LX. I've made two
> floppies, but, since it doesn't automatically boot from the floppy, I'm not
> sure what to put int the OS Selection Setup.
You don't boot FreeBSD from AlphaBIOS. Go to the setup screen and change
the OS to Unix, then save and power cycle the machine. When it comes
back, insert the first floppy and say 'boot dva0' at the prompt.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Thu Jul 13 2:26:10 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
by hub.freebsd.org (Postfix) with ESMTP
id B51C937BC57; Thu, 13 Jul 2000 02:26:06 -0700 (PDT)
(envelope-from mjacob@feral.com)
Received: from beppo.feral.com (beppo [192.67.166.79])
by feral.com (8.9.3/8.9.3) with ESMTP id CAA08747;
Thu, 13 Jul 2000 02:26:03 -0700
Date: Thu, 13 Jul 2000 02:26:05 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Chris Lynch <lynch@cityisp.net>
Cc: freebsd-alpha@FreeBSD.ORG, newbies@FreeBSD.ORG
Subject: Re: First Time Alpha install
In-Reply-To: <004f01bfeca8$244b78d0$da0802d8@CityGuide.com>
Message-ID: <Pine.BSF.4.10.10007130225250.32741-100000@beppo.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Ah, you need to switch from ARC to SRM- or flash new f/w in that has SRM.
None of the *BSD's support ARC as the OS monitor.
On Thu, 13 Jul 2000, Chris Lynch wrote:
> I'm trying to install FreeBSD 4.0 on a DEC AlphaPC 164 LX. I've made two
> floppies, but, since it doesn't automatically boot from the floppy, I'm not
> sure what to put int the OS Selection Setup.
> I've inserted a new OS call it FreeBSD, boot from A: kern.flp
> I'm not sure what to pass the OS options. It has a nifty Install Windows NT
> options...but , why? :)
>
> thanks,
> Chris
>
>
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-alpha" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Thu Jul 13 2:29:52 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from radius.city-guide.com (radius.cityisp.net [216.2.9.5])
by hub.freebsd.org (Postfix) with ESMTP
id EB71637C354; Thu, 13 Jul 2000 02:29:47 -0700 (PDT)
(envelope-from lynch@cityisp.net)
Received: from enitech (unverified [216.2.8.218]) by radius.city-guide.com
(Vircom SMTPRS 4.2.181) with SMTP id <B0006335478@radius.city-guide.com>;
Thu, 13 Jul 2000 05:41:00 -0400
Message-ID: <007901bfecad$2d10db40$da0802d8@CityGuide.com>
From: "Chris Lynch" <lynch@cityisp.net>
To: <mjacob@feral.com>
Cc: <freebsd-alpha@FreeBSD.ORG>, <newbies@FreeBSD.ORG>
References: <Pine.BSF.4.10.10007130225250.32741-100000@beppo.feral.com>
Subject: Re: First Time Alpha install
Date: Thu, 13 Jul 2000 05:31:47 -0400
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Yeah, That's what I'm doing now. Thanks for the quick responce people.
Chris
>
> Ah, you need to switch from ARC to SRM- or flash new f/w in that has SRM.
> None of the *BSD's support ARC as the OS monitor.
>
> On Thu, 13 Jul 2000, Chris Lynch wrote:
>
> > I'm trying to install FreeBSD 4.0 on a DEC AlphaPC 164 LX. I've made two
> > floppies, but, since it doesn't automatically boot from the floppy, I'm
not
> > sure what to put int the OS Selection Setup.
> > I've inserted a new OS call it FreeBSD, boot from A: kern.flp
> > I'm not sure what to pass the OS options. It has a nifty Install Windows
NT
> > options...but , why? :)
> >
> > thanks,
> > Chris
> >
> >
> >
> >
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-alpha" in the body of the message
> >
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Thu Jul 13 11: 8:49 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21])
by hub.freebsd.org (Postfix) with ESMTP
id 90E8F37BF6C; Thu, 13 Jul 2000 11:08:39 -0700 (PDT)
(envelope-from wkb@freebie.demon.nl)
Received: from [212.238.54.101] (helo=freebie.demon.nl)
by post.mail.nl.demon.net with smtp (Exim 3.14 #4)
id 13CnPZ-00073p-00; Thu, 13 Jul 2000 18:08:37 +0000
Received: (from wkb@localhost)
by freebie.demon.nl (8.9.3/8.9.3) id TAA01052;
Thu, 13 Jul 2000 19:46:04 +0200 (CEST)
(envelope-from wkb)
Date: Thu, 13 Jul 2000 19:46:04 +0200
From: Wilko Bulte <wkb@freebie.demon.nl>
To: Mike Smith <msmith@freebsd.org>
Cc: Chris Lynch <lynch@cityisp.net>, freebsd-alpha@freebsd.org,
newbies@freebsd.org
Subject: Re: First Time Alpha install
Message-ID: <20000713194604.C975@freebie.demon.nl>
Reply-To: wilko@freebsd.org
References: <004f01bfeca8$244b78d0$da0802d8@CityGuide.com> <200007130921.CAA00886@mass.osd.bsdi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <200007130921.CAA00886@mass.osd.bsdi.com>; from msmith@freebsd.org on Thu, Jul 13, 2000 at 02:21:47AM -0700
X-OS: FreeBSD 4.0-STABLE
X-PGP: finger wilko@freebsd.org
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Thu, Jul 13, 2000 at 02:21:47AM -0700, Mike Smith wrote:
> > I'm trying to install FreeBSD 4.0 on a DEC AlphaPC 164 LX. I've made two
> > floppies, but, since it doesn't automatically boot from the floppy, I'm not
> > sure what to put int the OS Selection Setup.
>
> You don't boot FreeBSD from AlphaBIOS. Go to the setup screen and change
> the OS to Unix, then save and power cycle the machine. When it comes
> back, insert the first floppy and say 'boot dva0' at the prompt.
Reading INSTALL.TXT is enlightening too..
--
Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try"
wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes Back
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Thu Jul 13 11: 8:51 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21])
by hub.freebsd.org (Postfix) with ESMTP id 26CFA37BFA2
for <freebsd-alpha@freebsd.org>; Thu, 13 Jul 2000 11:08:42 -0700 (PDT)
(envelope-from wkb@freebie.demon.nl)
Received: from [212.238.54.101] (helo=freebie.demon.nl)
by post.mail.nl.demon.net with smtp (Exim 3.14 #4)
id 13CnPY-00073p-00; Thu, 13 Jul 2000 18:08:36 +0000
Received: (from wkb@localhost)
by freebie.demon.nl (8.9.3/8.9.3) id TAA01077;
Thu, 13 Jul 2000 19:49:11 +0200 (CEST)
(envelope-from wkb)
Date: Thu, 13 Jul 2000 19:49:11 +0200
From: Wilko Bulte <wkb@freebie.demon.nl>
To: Andrew Gallatin <gallatin@cs.duke.edu>
Cc: Alec Wolman <wolman@cs.washington.edu>, freebsd-alpha@freebsd.org
Subject: Re: warning: received processor correctable error message
Message-ID: <20000713194911.D975@freebie.demon.nl>
Reply-To: wilko@freebsd.org
References: <gallatin@cs.duke.edu> <14701.9102.36017.419004@grasshopper.cs.duke.edu> <200007130212.TAA25730@miles.cs.washington.edu> <14701.10036.523075.203941@grasshopper.cs.duke.edu> <20000713082413.B4271@freebie.demon.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <20000713082413.B4271@freebie.demon.nl>; from wkb@freebie.demon.nl on Thu, Jul 13, 2000 at 08:24:13AM +0200
X-OS: FreeBSD 4.0-STABLE
X-PGP: finger wilko@freebsd.org
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Thu, Jul 13, 2000 at 08:24:13AM +0200, Wilko Bulte wrote:
> On Wed, Jul 12, 2000 at 10:21:53PM -0400, Andrew Gallatin wrote:
> >
> > Alec Wolman writes:
> > >
> > > If it is a memory error, will there be any way to detect which SIMM?
> >
> > I don't know.
>
> Yes there is. But not with FreeBSD AFAIK. DECevent used on the binary errlog
> of Tru64 UNIX gives you enough info, when combined with the service manuals
> of a machine, to determine which DIMM/SIMM is problematic.
In case somebody is interested in what it looks like on T64:
Jul 10 12:10:08 storage vmunix: Machine Check error corrected by processor
Jul 10 12:10:08 storage vmunix: Physical address of error ffffff000dde02ff
Corre
cted ECC Error in Memory during D-Cache fill
Jul 10 12:10:08 storage vmunix: Fill Syndrome = 0000000000000031
Jul 10 12:10:08 storage vmunix: Single Bit error in Quadword 0 at bit<14> in
a D
ata bit
Jul 10 12:10:08 storage vmunix: EI Address = ffffff000dde02ff
Jul 10 12:10:08 storage vmunix: EI Status = fffffff0c5ffffff
Jul 10 12:10:08 storage vmunix: Interrupt Status Reg =
00000001000000
00
Jul 10 12:10:08 storage vmunix: ECC Syndrome = 0000000000000000
Jul 10 12:10:08 storage vmunix: Memory Port 0 Status Reg =
000000
0000000000
Jul 10 12:10:08 storage vmunix: Memory Port 1 Status Reg =
000000
0000000000
Jul 10 12:10:08 storage vmunix: CIA Error Status =
00000000000000
00
Jul 10 12:10:08 storage vmunix: CIA Error Reg = 0000000000000000
--
Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try"
wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes Back
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Thu Jul 13 14:34:34 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from fw.brother.com.mx (via-lan-200.33-165-151.brother.com.mx [200.33.165.151])
by hub.freebsd.org (Postfix) with ESMTP id AE79137C6EC
for <freebsd-alpha@FreeBSD.ORG>; Thu, 13 Jul 2000 14:34:24 -0700 (PDT)
(envelope-from szapata@creatos.com.mx)
Received: by fw.brother.com.mx; id QAA18589; Thu, 13 Jul 2000 16:32:15 -0500 (CDT)
Received: from unknown(205.134.59.45) by fw.brother.com.mx via smap (V4.2)
id xma018564; Thu, 13 Jul 00 16:31:20 -0500
Mime-Version: 1.0
X-Sender: szapata@mail.creatos.com.mx
Message-Id: <p04320400b593e5c5fe34@[205.134.59.45]>
In-Reply-To: <20000711203908.B1457@freebie.demon.nl>
References: <396B3C49.6696EDE4@creatos.com.mx>
<20000711203908.B1457@freebie.demon.nl>
Date: Thu, 13 Jul 2000 16:33:00 -0500
To: freebsd-alpha@FreeBSD.ORG
From: Santiago Zapata <szapata@creatos.com.mx>
Subject: Re: newbie installation question on Alpha Server 1000
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
>On Tue, Jul 11, 2000 at 08:24:57AM -0700, Santiago Zapata wrote:
>
>> I am trying to install 4.0-RELEASE on an AlphaServer 1000.
>> I already downloaded the boot floppies, I even reach the initial
>> installation screen when I boot from the floppies but my hard drive is
>> not recognized
>
>What is that harddisk connected to? The onboard SCSI controller of the
>Alpha? What does the SRM console tell you when you type SHOW CONF
>and SHOW DEV at the >>> prompt?
>
>> I read about having to spin the hard drive to be recogized but I did not
>> find how. I also read in the HARDWARE.TXT file that the kernel needs
>> "options DEC_1000A" but I do not know how to do it at boot time
>
>You don't have to, the install kernels are compiled with the necessary
>support code (options FOO is a config/compile time thing).
>
>Another question: is it an AlphaServer 1000 or an AlphaServer 1000A (note
>the trailing A)
ARC Console V4.58
PALcode: VMS PALcode V5.56-7, OSF PALcode V1.45-12
Serial Rom: V2.8
Processor
DECchip(tm) 21064A-2 266 MHz
Memory
128 Meg of System Memory
Bank 0 = 64 Mbytes (16 MB Per Simm) Startting at 0x00000000
Bank 1 = 64 Mbytes (16 MB Per Simm) Startting at 0x04000000
Bank 2 = No Memory Detected
Bank 3 = No memory Detected
Slot Option
6 NCR 53C818 Hose 0, Bus 0, PCI
pka0.7.0.6.0 SCSI Bus ID7
dka0.0.0.6.0 RZ28M
dka400.4.0.6.0 RRD45
mka5000.5.0.6.0 TLZ07
7 Intel 82375 Bridge to hose 1, EISA
13 DECchip 21040-AA ewa0.0.3.0 08-00-2b-e5-ca-b7
slot Opion Hose 1 , EISA
dva0.0.0.0.1
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Thu Jul 13 14:42:35 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
by hub.freebsd.org (Postfix) with ESMTP id 5318D37BD35
for <freebsd-alpha@FreeBSD.ORG>; Thu, 13 Jul 2000 14:42:21 -0700 (PDT)
(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA07769;
Thu, 13 Jul 2000 17:42:19 -0400 (EDT)
Received: (from gallatin@localhost)
by grasshopper.cs.duke.edu (8.9.3/8.9.1) id RAA33194;
Thu, 13 Jul 2000 17:42:19 -0400 (EDT)
(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Thu, 13 Jul 2000 17:42:18 -0400 (EDT)
To: Santiago Zapata <szapata@creatos.com.mx>
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: newbie installation question on Alpha Server 1000
In-Reply-To: <p04320400b593e5c5fe34@[205.134.59.45]>
References: <396B3C49.6696EDE4@creatos.com.mx>
<20000711203908.B1457@freebie.demon.nl>
<p04320400b593e5c5fe34@[205.134.59.45]>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid
Message-ID: <14702.13975.727424.446303@grasshopper.cs.duke.edu>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Santiago Zapata writes:
> Slot Option
>
> 6 NCR 53C818 Hose 0, Bus 0, PCI
> pka0.7.0.6.0 SCSI Bus ID7
> dka0.0.0.6.0 RZ28M
> dka400.4.0.6.0 RRD45
> mka5000.5.0.6.0 TLZ07
>
This should work. Do you see a message like "ncr0: <ncr 53c810......" ??
Another thing to try is to make sure the disk is spun up. There
should be a jumper you can set on the rz28 to make it spin up at
power-on. It might be as simple as to say 'boot dka0' and ^C out of
it after the disk starts moving.
(I realize that FreeBSD is supposed to take care of this, but I seem
to remember another AS1000 owner complaining about this).
Drew
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Thu Jul 13 14:48:16 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from freebie.demon.nl (freebie.demon.nl [212.238.54.101])
by hub.freebsd.org (Postfix) with ESMTP id D39C937C5A3
for <freebsd-alpha@freebsd.org>; Thu, 13 Jul 2000 14:47:35 -0700 (PDT)
(envelope-from wkb@freebie.demon.nl)
Received: (from wkb@localhost)
by freebie.demon.nl (8.9.3/8.9.3) id XAA00576;
Thu, 13 Jul 2000 23:47:24 +0200 (CEST)
(envelope-from wkb)
Date: Thu, 13 Jul 2000 23:47:24 +0200
From: Wilko Bulte <wkb@freebie.demon.nl>
To: Andrew Gallatin <gallatin@cs.duke.edu>
Cc: Santiago Zapata <szapata@creatos.com.mx>,
freebsd-alpha@freebsd.org
Subject: Re: newbie installation question on Alpha Server 1000
Message-ID: <20000713234724.A562@freebie.demon.nl>
Reply-To: wilko@freebsd.org
References: <396B3C49.6696EDE4@creatos.com.mx> <20000711203908.B1457@freebie.demon.nl> <p04320400b593e5c5fe34@[205.134.59.45]> <14702.13975.727424.446303@grasshopper.cs.duke.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <14702.13975.727424.446303@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Thu, Jul 13, 2000 at 05:42:18PM -0400
X-OS: FreeBSD 4.0-STABLE
X-PGP: finger wilko@freebsd.org
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Thu, Jul 13, 2000 at 05:42:18PM -0400, Andrew Gallatin wrote:
>
> Santiago Zapata writes:
> > Slot Option
> >
> > 6 NCR 53C818 Hose 0, Bus 0, PCI
818? 810 I hope..
> > pka0.7.0.6.0 SCSI Bus ID7
> > dka0.0.0.6.0 RZ28M
> > dka400.4.0.6.0 RRD45
> > mka5000.5.0.6.0 TLZ07
> >
>
> This should work. Do you see a message like "ncr0: <ncr 53c810......" ??
>
> Another thing to try is to make sure the disk is spun up. There
> should be a jumper you can set on the rz28 to make it spin up at
> power-on. It might be as simple as to say 'boot dka0' and ^C out of
> it after the disk starts moving.
SHOW DEVICES will do the spinup for you. But as for the jumper: depends on
the RZ28x model. A RZ28M is a Seagate IIRC. In general the SRM should have
no problems spinning up the disk, otherwise T64 or VMS would also have a
problem booting ;-)
--
Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try"
wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes Back
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Thu Jul 13 17:24:45 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57])
by hub.freebsd.org (Postfix) with ESMTP
id 4065037B594; Thu, 13 Jul 2000 17:24:43 -0700 (PDT)
(envelope-from obrien@dragon.nuxi.com)
Received: (from obrien@localhost)
by dragon.nuxi.com (8.9.3/8.9.1) id RAA65710;
Thu, 13 Jul 2000 17:24:41 -0700 (PDT)
(envelope-from obrien)
Date: Thu, 13 Jul 2000 17:24:41 -0700
From: "David O'Brien" <obrien@freebsd.org>
To: wilko@freebsd.org
Cc: freebsd-alpha@freebsd.org
Subject: Re: unaligned access fault panic during boot?
Message-ID: <20000713172441.B65639@dragon.nuxi.com>
Reply-To: obrien@freebsd.org
References: <20000712231700.A2143@freebie.demon.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <20000712231700.A2143@freebie.demon.nl>; from wkb@freebie.demon.nl on Wed, Jul 12, 2000 at 11:17:00PM +0200
X-Operating-System: FreeBSD 5.0-CURRENT
Organization: The NUXI BSD group
X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A
X-Pgp-Rsa-Keyid: 1024/34F9F9D5
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Wed, Jul 12, 2000 at 11:17:00PM +0200, Wilko Bulte wrote:
> Using a freshly supped -current source tree (2 hours ago) I'm getting a
> panic on boot:
Are you still experiencing this? I was getting the same on a DS20 two
days ago.
--
-- David (obrien@FreeBSD.org)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Thu Jul 13 22:45:41 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
by hub.freebsd.org (Postfix) with ESMTP
id 91DF437BAD3; Thu, 13 Jul 2000 22:45:31 -0700 (PDT)
(envelope-from mjacob@feral.com)
Received: from beppo.feral.com (beppo [192.67.166.79])
by feral.com (8.9.3/8.9.3) with ESMTP id WAA12580;
Thu, 13 Jul 2000 22:45:22 -0700
Date: Thu, 13 Jul 2000 22:45:24 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: wilko@FreeBSD.ORG
Cc: Andrew Gallatin <gallatin@cs.duke.edu>,
Alec Wolman <wolman@cs.washington.edu>, freebsd-alpha@FreeBSD.ORG
Subject: Re: warning: received processor correctable error message
In-Reply-To: <20000713194911.D975@freebie.demon.nl>
Message-ID: <Pine.BSF.4.10.10007132241190.33645-100000@beppo.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
I did a bit of this kind of stuff for NetBSD-alpha for decoding the logout
frames and reporting errors.
Mostly this stuff is only important for doing SIMM replacement, and as such it
fell to the bottom of my list of important things to do.
But not quite true for the TurboLaser because you have to do some patchups
even for a 670 error because the I/O boards (KTLA, KFTH) can cause such errors
when they fill ram on the memory boards, and the PAL code for any particular
processor hasn't got the smarts or moxie to go out and then do the ECC scrub
it would do if it were the CPU causing the error- or at leat that's my
recollection.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Thu Jul 13 23:44:20 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57])
by hub.freebsd.org (Postfix) with ESMTP
id D44B937BBE3; Thu, 13 Jul 2000 23:44:16 -0700 (PDT)
(envelope-from ticso@cicely8.cicely.de)
Received: from mail.cicely.de (cicely.de [194.231.9.142])
by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e6E6iDU05392
(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK);
Fri, 14 Jul 2000 08:44:14 +0200 (MET DST)
Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10])
by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e6E6hXm20367;
Fri, 14 Jul 2000 08:43:34 +0200 (CEST)
Received: (from ticso@localhost)
by cicely8.cicely.de (8.9.3/8.9.2) id IAA08799;
Fri, 14 Jul 2000 08:43:33 +0200 (CEST)
(envelope-from ticso)
Date: Fri, 14 Jul 2000 08:43:33 +0200
From: Bernd Walter <ticso@cicely8.cicely.de>
To: freebsd-alpha@freebsd.org, Bill Paul <wpaul@freebsd.org>
Subject: fxp0 hangs on a PC164 using STABLE
Message-ID: <20000714084332.A8731@cicely8.cicely.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
From time to time the interface stops sending and receiving packets.
Sometimes an ifconfig down and up revives the connection otherwise
I need to reboot.
The link is still there.
Sending packets results in Buffer filled messages.
The host is running IPv4 and IPv6.
The card is fixed configured to 100/full.
STABLE is from 2000-07-08.
I know that the informations I gave here may be not enough.
Please feel free to ask me if you have an idea what is valueable.
--
B.Walter COSMO-Project http://www.cosmo-project.de
ticso@cicely.de Usergroup info@cosmo-project.de
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Thu Jul 13 23:54: 6 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
by hub.freebsd.org (Postfix) with ESMTP
id 000F237C0C4; Thu, 13 Jul 2000 23:54:03 -0700 (PDT)
(envelope-from mjacob@feral.com)
Received: from beppo.feral.com (beppo [192.67.166.79])
by feral.com (8.9.3/8.9.3) with ESMTP id XAA12835;
Thu, 13 Jul 2000 23:53:54 -0700
Date: Thu, 13 Jul 2000 23:53:56 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Bernd Walter <ticso@cicely8.cicely.de>
Cc: freebsd-alpha@FreeBSD.ORG, Bill Paul <wpaul@FreeBSD.ORG>
Subject: Re: fxp0 hangs on a PC164 using STABLE
In-Reply-To: <20000714084332.A8731@cicely8.cicely.de>
Message-ID: <Pine.BSF.4.10.10007132352490.33645-100000@beppo.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Fri, 14 Jul 2000, Bernd Walter wrote:
> >From time to time the interface stops sending and receiving packets.
> Sometimes an ifconfig down and up revives the connection otherwise
> I need to reboot.
> The link is still there.
> Sending packets results in Buffer filled messages.
> The host is running IPv4 and IPv6.
> The card is fixed configured to 100/full.
> STABLE is from 2000-07-08.
>
> I know that the informations I gave here may be not enough.
> Please feel free to ask me if you have an idea what is valueable.
>
This all very intersting. The last I saw on fxp on alpha was that Andrew
opened a bug against it not working (months ago) and dg never responded.
So, I'm surprised it works at all.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 0:15: 2 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from freebie.demon.nl (freebie.demon.nl [212.238.54.101])
by hub.freebsd.org (Postfix) with ESMTP
id 3E5E137C799; Fri, 14 Jul 2000 00:14:57 -0700 (PDT)
(envelope-from wkb@freebie.demon.nl)
Received: (from wkb@localhost)
by freebie.demon.nl (8.9.3/8.9.3) id JAA02707;
Fri, 14 Jul 2000 09:13:24 +0200 (CEST)
(envelope-from wkb)
Date: Fri, 14 Jul 2000 09:13:24 +0200
From: Wilko Bulte <wkb@freebie.demon.nl>
To: "David O'Brien" <obrien@freebsd.org>
Cc: wilko@freebsd.org, freebsd-alpha@freebsd.org
Subject: Re: unaligned access fault panic during boot?
Message-ID: <20000714091324.E1926@freebie.demon.nl>
Reply-To: wilko@freebsd.org
References: <20000712231700.A2143@freebie.demon.nl> <20000713172441.B65639@dragon.nuxi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <20000713172441.B65639@dragon.nuxi.com>; from obrien@freebsd.org on Thu, Jul 13, 2000 at 05:24:41PM -0700
X-OS: FreeBSD 4.0-STABLE
X-PGP: finger wilko@freebsd.org
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Thu, Jul 13, 2000 at 05:24:41PM -0700, David O'Brien wrote:
> On Wed, Jul 12, 2000 at 11:17:00PM +0200, Wilko Bulte wrote:
> > Using a freshly supped -current source tree (2 hours ago) I'm getting a
> > panic on boot:
>
> Are you still experiencing this? I was getting the same on a DS20 two
> days ago.
Yes I am :-(
I supped the latest -current as of yesterday evening. Built world using
my trusty kernel.works. Buildworld ran fine. Make installworld ran fine.
Building a kernel ran fine. Boot said 'kaboom'
Just guessing here: could this be related in some way with the *.hints
mechanism?
Any chance someone can provide me with a -current kernel (GENERIC one
*including* the vn device would be fine) to see if that works? I would
like to at least try a make release to have a stab at the Lynx testing.
[assuming the generated CD would not have the same problem ;-) ]
Wilko
--
Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try"
wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes Back
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 0:28:23 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51])
by hub.freebsd.org (Postfix) with ESMTP id 1AF2D37BC59
for <freebsd-alpha@freebsd.org>; Fri, 14 Jul 2000 00:28:21 -0700 (PDT)
(envelope-from msmith@mass.osd.bsdi.com)
Received: from mass.osd.bsdi.com (localhost [127.0.0.1])
by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id AAA01228;
Fri, 14 Jul 2000 00:36:52 -0700 (PDT)
(envelope-from msmith@mass.osd.bsdi.com)
Message-Id: <200007140736.AAA01228@mass.osd.bsdi.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: Bernd Walter <ticso@cicely8.cicely.de>
Cc: freebsd-alpha@freebsd.org
Subject: Re: fxp0 hangs on a PC164 using STABLE
In-reply-to: Your message of "Fri, 14 Jul 2000 08:43:33 +0200."
<20000714084332.A8731@cicely8.cicely.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 14 Jul 2000 00:36:52 -0700
From: Mike Smith <msmith@freebsd.org>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
fxp is not supported on the Alpha, and known to be unreliable there.
Contact the maintainer or use a different card. FWIW, this actually
sounds like an issue that's been seen on x86 as well.
> >From time to time the interface stops sending and receiving packets.
> Sometimes an ifconfig down and up revives the connection otherwise
> I need to reboot.
> The link is still there.
> Sending packets results in Buffer filled messages.
> The host is running IPv4 and IPv6.
> The card is fixed configured to 100/full.
> STABLE is from 2000-07-08.
>
> I know that the informations I gave here may be not enough.
> Please feel free to ask me if you have an idea what is valueable.
>
> --
> B.Walter COSMO-Project http://www.cosmo-project.de
> ticso@cicely.de Usergroup info@cosmo-project.de
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-alpha" in the body of the message
>
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 9:46:42 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57])
by hub.freebsd.org (Postfix) with ESMTP
id 2343737C9D6; Fri, 14 Jul 2000 09:46:31 -0700 (PDT)
(envelope-from ticso@cicely8.cicely.de)
Received: from mail.cicely.de (cicely.de [194.231.9.142])
by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e6EGkP814764
(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK);
Fri, 14 Jul 2000 18:46:27 +0200 (MET DST)
Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10])
by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e6EGjhm22294;
Fri, 14 Jul 2000 18:45:47 +0200 (CEST)
Received: (from ticso@localhost)
by cicely8.cicely.de (8.9.3/8.9.2) id SAA09334;
Fri, 14 Jul 2000 18:45:43 +0200 (CEST)
(envelope-from ticso)
Date: Fri, 14 Jul 2000 18:45:43 +0200
From: Bernd Walter <ticso@cicely8.cicely.de>
To: Mike Smith <msmith@freebsd.org>
Cc: freebsd-alpha@freebsd.org
Subject: Re: fxp0 hangs on a PC164 using STABLE
Message-ID: <20000714184542.A9315@cicely8.cicely.de>
References: <20000714084332.A8731@cicely8.cicely.de> <200007140736.AAA01228@mass.osd.bsdi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <200007140736.AAA01228@mass.osd.bsdi.com>; from msmith@freebsd.org on Fri, Jul 14, 2000 at 12:36:52AM -0700
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Fri, Jul 14, 2000 at 12:36:52AM -0700, Mike Smith wrote:
>
> fxp is not supported on the Alpha, and known to be unreliable there.
> Contact the maintainer or use a different card. FWIW, this actually
> sounds like an issue that's been seen on x86 as well.
Interesting as it's still (Rev 1.71.2.2) in GENERIC.
I've already organized an dc supported card.
--
B.Walter COSMO-Project http://www.cosmo-project.de
ticso@cicely.de Usergroup info@cosmo-project.de
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 10:32:53 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from implode.root.com (root.com [209.102.106.178])
by hub.freebsd.org (Postfix) with ESMTP
id 95BE737B7DF; Fri, 14 Jul 2000 10:32:49 -0700 (PDT)
(envelope-from dg@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
by implode.root.com (8.8.8/8.8.5) with ESMTP id KAA16976;
Fri, 14 Jul 2000 10:07:36 -0700 (PDT)
Message-Id: <200007141707.KAA16976@implode.root.com>
To: Mike Smith <msmith@FreeBSD.ORG>
Cc: Bernd Walter <ticso@cicely8.cicely.de>, freebsd-alpha@FreeBSD.ORG
Subject: Re: fxp0 hangs on a PC164 using STABLE
In-reply-to: Your message of "Fri, 14 Jul 2000 00:36:52 PDT."
<200007140736.AAA01228@mass.osd.bsdi.com>
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Fri, 14 Jul 2000 10:07:36 -0700
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
>fxp is not supported on the Alpha, and known to be unreliable there.
>Contact the maintainer or use a different card. FWIW, this actually
>sounds like an issue that's been seen on x86 as well.
It does? I've never heard of a bug report like this for x86 and in fact I'm
not aware of any bugs in the driver for x86.
It's true that I'm not providing support for the driver for use on the
Alpha. I don't have any Alpha's in production and don't have the time to
add one. This doesn't mean that someone else can't provide that support,
however, which is what has happend from time to time.
-DG
David Greenman
Co-founder, The FreeBSD Project - http://www.freebsd.org
Manufacturer of high-performance Internet servers - http://www.terasolutions.com
Pave the road of life with opportunities.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 10:40:13 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
by hub.freebsd.org (Postfix) with ESMTP
id D603937B666; Fri, 14 Jul 2000 10:40:08 -0700 (PDT)
(envelope-from mjacob@feral.com)
Received: from beppo.feral.com (beppo [192.67.166.79])
by feral.com (8.9.3/8.9.3) with ESMTP id KAA15242;
Fri, 14 Jul 2000 10:39:58 -0700
Date: Fri, 14 Jul 2000 10:40:00 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: David Greenman <dg@root.com>
Cc: Mike Smith <msmith@FreeBSD.ORG>,
Bernd Walter <ticso@cicely8.cicely.de>, freebsd-alpha@FreeBSD.ORG
Subject: Re: fxp0 hangs on a PC164 using STABLE
In-Reply-To: <200007141707.KAA16976@implode.root.com>
Message-ID: <Pine.BSF.4.10.10007141039420.34427-100000@beppo.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
> It's true that I'm not providing support for the driver for use on the
> Alpha. I don't have any Alpha's in production and don't have the time to
> add one. This doesn't mean that someone else can't provide that support,
> however, which is what has happend from time to time.
Can you clarify what 'provide' means?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 10:43:18 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from postal.blacksun.org (postal.blacksun.org [168.100.186.37])
by hub.freebsd.org (Postfix) with ESMTP
id 4759437C814; Fri, 14 Jul 2000 10:43:11 -0700 (PDT)
(envelope-from don@blacksun.org)
Received: from calis.blacksun.org (unknown [168.100.186.40])
by postal.blacksun.org (Postfix) with ESMTP
id 956A171641; Fri, 14 Jul 2000 13:43:23 -0400 (EDT)
Date: Fri, 14 Jul 2000 13:46:29 -0400 (EDT)
From: Don <don@blacksun.org>
To: David Greenman <dg@root.com>
Cc: Mike Smith <msmith@FreeBSD.ORG>,
Bernd Walter <ticso@cicely8.cicely.de>, freebsd-alpha@FreeBSD.ORG
Subject: Re: fxp0 hangs on a PC164 using STABLE
In-Reply-To: <200007141707.KAA16976@implode.root.com>
Message-ID: <Pine.BSF.4.05.10007141340320.48143-100000@calis.blacksun.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
> It does? I've never heard of a bug report like this for x86 and in fact I'm
> not aware of any bugs in the driver for x86.
I run about 25 systems that have Intel EtherExpress cards (82558 and
82559 chipsets) in them. All are running various FreeBSD releases (From
3.4 - various 4.0-STABLE variants). None of these boxes are in the
lsightest bit unstable. In fact, I have never seen more reliable systems
in my life.
-don
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 10:43:34 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20])
by hub.freebsd.org (Postfix) with ESMTP
id 8B04D37C903; Fri, 14 Jul 2000 10:43:30 -0700 (PDT)
(envelope-from wkb@freebie.demon.nl)
Received: from [212.238.54.101] (helo=freebie.demon.nl)
by post.mail.nl.demon.net with smtp (Exim 3.14 #2)
id 13D9Uj-0003n3-01; Fri, 14 Jul 2000 17:43:26 +0000
Received: (from wkb@localhost)
by freebie.demon.nl (8.9.3/8.9.3) id TAA01121;
Fri, 14 Jul 2000 19:19:10 +0200 (CEST)
(envelope-from wkb)
Date: Fri, 14 Jul 2000 19:19:10 +0200
From: Wilko Bulte <wkb@freebie.demon.nl>
To: Matthew Jacob <mjacob@feral.com>
Cc: Bernd Walter <ticso@cicely8.cicely.de>,
freebsd-alpha@freebsd.org, Bill Paul <wpaul@freebsd.org>
Subject: Re: fxp0 hangs on a PC164 using STABLE
Message-ID: <20000714191910.F346@freebie.demon.nl>
Reply-To: wilko@freebsd.org
References: <20000714084332.A8731@cicely8.cicely.de> <Pine.BSF.4.10.10007132352490.33645-100000@beppo.feral.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <Pine.BSF.4.10.10007132352490.33645-100000@beppo.feral.com>; from mjacob@feral.com on Thu, Jul 13, 2000 at 11:53:56PM -0700
X-OS: FreeBSD 4.0-STABLE
X-PGP: finger wilko@freebsd.org
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Thu, Jul 13, 2000 at 11:53:56PM -0700, Matthew Jacob wrote:
> On Fri, 14 Jul 2000, Bernd Walter wrote:
>
> > >From time to time the interface stops sending and receiving packets.
> > Sometimes an ifconfig down and up revives the connection otherwise
> > I need to reboot.
> > The link is still there.
> > Sending packets results in Buffer filled messages.
> > The host is running IPv4 and IPv6.
> > The card is fixed configured to 100/full.
> > STABLE is from 2000-07-08.
> >
> > I know that the informations I gave here may be not enough.
> > Please feel free to ask me if you have an idea what is valueable.
> >
>
> This all very intersting. The last I saw on fxp on alpha was that Andrew
> opened a bug against it not working (months ago) and dg never responded.
> So, I'm surprised it works at all.
For me that means that it must be removed from GENERIC and documented as
not working in HARDWARE.TXT for 4.1R
Objections?
--
Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try"
wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes Back
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 10:54:21 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
by hub.freebsd.org (Postfix) with ESMTP
id 47F3F37C649; Fri, 14 Jul 2000 10:54:18 -0700 (PDT)
(envelope-from mjacob@feral.com)
Received: from beppo.feral.com (beppo [192.67.166.79])
by feral.com (8.9.3/8.9.3) with ESMTP id KAA15342;
Fri, 14 Jul 2000 10:54:16 -0700
Date: Fri, 14 Jul 2000 10:54:18 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: wilko@freebsd.org
Cc: Bernd Walter <ticso@cicely8.cicely.de>,
freebsd-alpha@freebsd.org, Bill Paul <wpaul@freebsd.org>
Subject: Re: fxp0 hangs on a PC164 using STABLE
In-Reply-To: <20000714191910.F346@freebie.demon.nl>
Message-ID: <Pine.BSF.4.10.10007141054040.34427-100000@beppo.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
>
> For me that means that it must be removed from GENERIC and documented as
> not working in HARDWARE.TXT for 4.1R
>
> Objections?
None, unless you want to fix it :-)...
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 10:55: 9 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
by hub.freebsd.org (Postfix) with ESMTP
id CD24237C9DD; Fri, 14 Jul 2000 10:55:04 -0700 (PDT)
(envelope-from mjacob@feral.com)
Received: from beppo.feral.com (beppo [192.67.166.79])
by feral.com (8.9.3/8.9.3) with ESMTP id KAA15351;
Fri, 14 Jul 2000 10:54:58 -0700
Date: Fri, 14 Jul 2000 10:55:01 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Don <don@blacksun.org>
Cc: David Greenman <dg@root.com>, Mike Smith <msmith@FreeBSD.ORG>,
Bernd Walter <ticso@cicely8.cicely.de>, freebsd-alpha@FreeBSD.ORG
Subject: Re: fxp0 hangs on a PC164 using STABLE
In-Reply-To: <Pine.BSF.4.05.10007141340320.48143-100000@calis.blacksun.org>
Message-ID: <Pine.BSF.4.10.10007141054430.34427-100000@beppo.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Do these fxp cards run on Alpha boxes?
On Fri, 14 Jul 2000, Don wrote:
> > It does? I've never heard of a bug report like this for x86 and in fact I'm
> > not aware of any bugs in the driver for x86.
> I run about 25 systems that have Intel EtherExpress cards (82558 and
> 82559 chipsets) in them. All are running various FreeBSD releases (From
> 3.4 - various 4.0-STABLE variants). None of these boxes are in the
> lsightest bit unstable. In fact, I have never seen more reliable systems
> in my life.
>
> -don
>
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-alpha" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 10:59:40 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from postal.blacksun.org (postal.blacksun.org [168.100.186.37])
by hub.freebsd.org (Postfix) with ESMTP
id 7643537B51D; Fri, 14 Jul 2000 10:59:36 -0700 (PDT)
(envelope-from don@blacksun.org)
Received: from calis.blacksun.org (unknown [168.100.186.40])
by postal.blacksun.org (Postfix) with ESMTP
id A511E71641; Fri, 14 Jul 2000 13:59:48 -0400 (EDT)
Date: Fri, 14 Jul 2000 14:02:54 -0400 (EDT)
From: Don <don@blacksun.org>
To: Matthew Jacob <mjacob@feral.com>
Cc: David Greenman <dg@root.com>, Mike Smith <msmith@FreeBSD.ORG>,
Bernd Walter <ticso@cicely8.cicely.de>, freebsd-alpha@FreeBSD.ORG
Subject: Re: fxp0 hangs on a PC164 using STABLE
In-Reply-To: <Pine.BSF.4.10.10007141054430.34427-100000@beppo.feral.com>
Message-ID: <Pine.BSF.4.05.10007141359310.48207-100000@calis.blacksun.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
> Do these fxp cards run on Alpha boxes?
No I appologize. This was in response to the comment about instability on
x86 and was directed towards David.
I tried to install an 82558 in my alpha to no avail.
-don
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 11: 9:16 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from implode.root.com (root.com [209.102.106.178])
by hub.freebsd.org (Postfix) with ESMTP
id 5AAD337BB1D; Fri, 14 Jul 2000 11:09:09 -0700 (PDT)
(envelope-from dg@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
by implode.root.com (8.8.8/8.8.5) with ESMTP id KAA17205;
Fri, 14 Jul 2000 10:56:17 -0700 (PDT)
Message-Id: <200007141756.KAA17205@implode.root.com>
To: mjacob@feral.com
Cc: Mike Smith <msmith@FreeBSD.ORG>,
Bernd Walter <ticso@cicely8.cicely.de>, freebsd-alpha@FreeBSD.ORG
Subject: Re: fxp0 hangs on a PC164 using STABLE
In-reply-to: Your message of "Fri, 14 Jul 2000 10:40:00 PDT."
<Pine.BSF.4.10.10007141039420.34427-100000@beppo.feral.com>
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Fri, 14 Jul 2000 10:56:17 -0700
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
>> It's true that I'm not providing support for the driver for use on the
>> Alpha. I don't have any Alpha's in production and don't have the time to
>> add one. This doesn't mean that someone else can't provide that support,
>> however, which is what has happend from time to time.
>
>Can you clarify what 'provide' means?
"Providing support" to me means not only getting it working, but also
making sure that it continues to work over time and putting the effort in
to fix it if it should break.
-DG
David Greenman
Co-founder, The FreeBSD Project - http://www.freebsd.org
Manufacturer of high-performance Internet servers - http://www.terasolutions.com
Pave the road of life with opportunities.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 11:35:35 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
by hub.freebsd.org (Postfix) with ESMTP
id F118137BE45; Fri, 14 Jul 2000 11:35:29 -0700 (PDT)
(envelope-from mjacob@feral.com)
Received: from semuta.feral.com (semuta [192.67.166.70])
by feral.com (8.9.3/8.9.3) with ESMTP id LAA15562;
Fri, 14 Jul 2000 11:35:26 -0700
Date: Fri, 14 Jul 2000 11:33:14 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: David Greenman <dg@root.com>
Cc: Mike Smith <msmith@FreeBSD.ORG>,
Bernd Walter <ticso@cicely8.cicely.de>, freebsd-alpha@FreeBSD.ORG
Subject: Re: fxp0 hangs on a PC164 using STABLE
In-Reply-To: <200007141756.KAA17205@implode.root.com>
Message-ID: <Pine.BSF.4.05.10007141132330.5888-100000@semuta.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
> "Providing support" to me means not only getting it working, but also
> making sure that it continues to work over time and putting the effort in
> to fix it if it should break.
Well, this starts us diverging toward meta-issues.
I'm sorry you don't wish to support this on the alpha.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 11:43:41 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
by hub.freebsd.org (Postfix) with ESMTP
id 64C2937B8D0; Fri, 14 Jul 2000 11:43:36 -0700 (PDT)
(envelope-from mjacob@feral.com)
Received: from semuta.feral.com (semuta [192.67.166.70])
by feral.com (8.9.3/8.9.3) with ESMTP id LAA15600;
Fri, 14 Jul 2000 11:43:19 -0700
Date: Fri, 14 Jul 2000 11:41:07 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Don <don@blacksun.org>
Cc: David Greenman <dg@root.com>, Mike Smith <msmith@FreeBSD.ORG>,
Bernd Walter <ticso@cicely8.cicely.de>, freebsd-alpha@FreeBSD.ORG
Subject: Re: fxp0 hangs on a PC164 using STABLE
In-Reply-To: <Pine.BSF.4.05.10007141359310.48207-100000@calis.blacksun.org>
Message-ID: <Pine.BSF.4.05.10007141140520.5888-100000@semuta.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
> No I appologize.
No need to apologize. We'd love to see it working there.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 11:43:52 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
by hub.freebsd.org (Postfix) with ESMTP
id 22F8037B814; Fri, 14 Jul 2000 11:43:47 -0700 (PDT)
(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA24691;
Fri, 14 Jul 2000 14:43:44 -0400 (EDT)
Received: (from gallatin@localhost)
by grasshopper.cs.duke.edu (8.9.3/8.9.1) id OAA35006;
Fri, 14 Jul 2000 14:43:43 -0400 (EDT)
(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Fri, 14 Jul 2000 14:43:43 -0400 (EDT)
To: mjacob@feral.com
Cc: David Greenman <dg@root.com>, Mike Smith <msmith@FreeBSD.ORG>,
Bernd Walter <ticso@cicely8.cicely.de>, freebsd-alpha@FreeBSD.ORG
Subject: Re: fxp0 hangs on a PC164 using STABLE
In-Reply-To: <Pine.BSF.4.05.10007141132330.5888-100000@semuta.feral.com>
References: <200007141756.KAA17205@implode.root.com>
<Pine.BSF.4.05.10007141132330.5888-100000@semuta.feral.com>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid
Message-ID: <14703.24005.384580.704375@grasshopper.cs.duke.edu>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Matthew Jacob writes:
>
> > "Providing support" to me means not only getting it working, but also
> > making sure that it continues to work over time and putting the effort in
> > to fix it if it should break.
>
> Well, this starts us diverging toward meta-issues.
>
> I'm sorry you don't wish to support this on the alpha.
For what its worth, I just stole an fxp from an x86. I'm going to try
to getting working, but I make no promises.
I've just seen the interface lock under load. I need to setup another
box with a second interface and an xover cable to test against as I do
all my development over NFS & the fxp is not usable as primary
interface.
David: Is the fxp module unloadable, or will it crash the machine in
strange and mysterious ways upon unload, like most of the network
drivers do?
Drew
PS: Interesting trivia: Newer firmware supports booting over the fxp!
>>>show conf
API UP1000 598 MHz
SRM Console: A5.6-4.1-9
PALcode: OpenVMS PALcode V1.69-54, Tru64 UNIX PALcode V1.62-1
Processors
CPU 0 Alpha 21264A-8 598 MHz SROM Revision: V17.31
Bcache size: 2 MB
Core Logic
MEMORY
Array # Size Base Addr
------- ---------- ---------
2 128 MB 000000000
Total Bad Pages = 0
Total Good Memory = 128 MBytes
PCI Hose 00
Bus 00 Slot 01/0: 70071022
Bridge to Bus 2, PCI
Bus 00 Slot 07: Acer Labs M1543C
Bridge to Bus 1, ISA
Bus 00 Slot 09: DE500-BA Network Controller
ewa0.0.0.9.0 00-00-F8-07-B6-45
Bus 00 Slot 10: NCR 53C875
pka0.7.0.10.0 SCSI Bus ID 7
dka0.0.0.10.0 SEAGATE ST39140W
Bus 00 Slot 11: Intel 8255x Ethernet
eia0.0.0.11.0 00-A0-C9-8A-AC-AA
<...>
>>>show dev
dka0.0.0.10.0 DKA0 SEAGATE ST39140W 1498
dqa0.0.0.16.0 DQA0 Maxtor 9 0651U2 FA520S60
dqb0.0.1.16.0 DQB0 CD-ROM C DU4011 UY0A
dva0.0.0.0.0 DVA0
eia0.0.0.11.0 EIA0 00-A0-C9-8A-AC-AA
ewa0.0.0.9.0 EWA0 00-00-F8-07-B6-45
pka0.7.0.10.0 PKA0 SCSI Bus ID 7
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 11:45: 5 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
by hub.freebsd.org (Postfix) with ESMTP
id 309DE37BF6A; Fri, 14 Jul 2000 11:45:02 -0700 (PDT)
(envelope-from mjacob@feral.com)
Received: from semuta.feral.com (semuta [192.67.166.70])
by feral.com (8.9.3/8.9.3) with ESMTP id LAA15610;
Fri, 14 Jul 2000 11:44:50 -0700
Date: Fri, 14 Jul 2000 11:42:38 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Andrew Gallatin <gallatin@cs.duke.edu>
Cc: David Greenman <dg@root.com>, Mike Smith <msmith@FreeBSD.ORG>,
Bernd Walter <ticso@cicely8.cicely.de>, freebsd-alpha@FreeBSD.ORG
Subject: Re: fxp0 hangs on a PC164 using STABLE
In-Reply-To: <14703.24005.384580.704375@grasshopper.cs.duke.edu>
Message-ID: <Pine.BSF.4.05.10007141142150.5888-100000@semuta.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
ho-ho....! Like, "If SRM sees it, damn it, FreeBSD ought to drive it!" ?? :-)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 11:53:48 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57])
by hub.freebsd.org (Postfix) with ESMTP
id 4C05137B94B; Fri, 14 Jul 2000 11:53:39 -0700 (PDT)
(envelope-from ticso@cicely8.cicely.de)
Received: from mail.cicely.de (cicely.de [194.231.9.142])
by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e6EIrPi23234
(using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK);
Fri, 14 Jul 2000 20:53:27 +0200 (MET DST)
Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10])
by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e6EIqkm22693;
Fri, 14 Jul 2000 20:52:46 +0200 (CEST)
Received: (from ticso@localhost)
by cicely8.cicely.de (8.9.3/8.9.2) id UAA09429;
Fri, 14 Jul 2000 20:52:42 +0200 (CEST)
(envelope-from ticso)
Date: Fri, 14 Jul 2000 20:52:42 +0200
From: Bernd Walter <ticso@cicely8.cicely.de>
To: Don <don@blacksun.org>
Cc: Matthew Jacob <mjacob@feral.com>, David Greenman <dg@root.com>,
Mike Smith <msmith@FreeBSD.ORG>, freebsd-alpha@FreeBSD.ORG
Subject: Re: fxp0 hangs on a PC164 using STABLE
Message-ID: <20000714205242.B9315@cicely8.cicely.de>
References: <Pine.BSF.4.10.10007141054430.34427-100000@beppo.feral.com> <Pine.BSF.4.05.10007141359310.48207-100000@calis.blacksun.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <Pine.BSF.4.05.10007141359310.48207-100000@calis.blacksun.org>; from don@blacksun.org on Fri, Jul 14, 2000 at 02:02:54PM -0400
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Fri, Jul 14, 2000 at 02:02:54PM -0400, Don wrote:
> > Do these fxp cards run on Alpha boxes?
> No I appologize. This was in response to the comment about instability on
> x86 and was directed towards David.
See -current archives.
There were some Mails that mentioned this to happen when using IPv6.
Anyway I never was able to see that problem myself since 4.0-RELEASE
on x86.
--
B.Walter COSMO-Project http://www.cosmo-project.de
ticso@cicely.de Usergroup info@cosmo-project.de
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 12:19:17 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from implode.root.com (root.com [209.102.106.178])
by hub.freebsd.org (Postfix) with ESMTP
id EC6BB37C1A1; Fri, 14 Jul 2000 12:19:14 -0700 (PDT)
(envelope-from dg@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
by implode.root.com (8.8.8/8.8.5) with ESMTP id MAA17569;
Fri, 14 Jul 2000 12:06:41 -0700 (PDT)
Message-Id: <200007141906.MAA17569@implode.root.com>
To: mjacob@feral.com
Cc: Mike Smith <msmith@FreeBSD.ORG>,
Bernd Walter <ticso@cicely8.cicely.de>, freebsd-alpha@FreeBSD.ORG
Subject: Re: fxp0 hangs on a PC164 using STABLE
In-reply-to: Your message of "Fri, 14 Jul 2000 11:33:14 PDT."
<Pine.BSF.4.05.10007141132330.5888-100000@semuta.feral.com>
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Fri, 14 Jul 2000 12:06:41 -0700
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
>
>> "Providing support" to me means not only getting it working, but also
>> making sure that it continues to work over time and putting the effort in
>> to fix it if it should break.
>
>Well, this starts us diverging toward meta-issues.
>
>I'm sorry you don't wish to support this on the alpha.
Me too. With 500% of my time committed, I'm forced to realize my
limitations, however.
-DG
David Greenman
Co-founder, The FreeBSD Project - http://www.freebsd.org
Manufacturer of high-performance Internet servers - http://www.terasolutions.com
Pave the road of life with opportunities.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 12:21:20 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from implode.root.com (root.com [209.102.106.178])
by hub.freebsd.org (Postfix) with ESMTP
id 63D4C37B688; Fri, 14 Jul 2000 12:21:14 -0700 (PDT)
(envelope-from dg@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
by implode.root.com (8.8.8/8.8.5) with ESMTP id MAA17583;
Fri, 14 Jul 2000 12:08:08 -0700 (PDT)
Message-Id: <200007141908.MAA17583@implode.root.com>
To: Andrew Gallatin <gallatin@cs.duke.edu>
Cc: mjacob@feral.com, Mike Smith <msmith@FreeBSD.ORG>,
Bernd Walter <ticso@cicely8.cicely.de>, freebsd-alpha@FreeBSD.ORG
Subject: Re: fxp0 hangs on a PC164 using STABLE
In-reply-to: Your message of "Fri, 14 Jul 2000 14:43:43 EDT."
<14703.24005.384580.704375@grasshopper.cs.duke.edu>
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Fri, 14 Jul 2000 12:08:08 -0700
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
>David: Is the fxp module unloadable, or will it crash the machine in
>strange and mysterious ways upon unload, like most of the network
>drivers do?
I've never tried to make it dynamically (un)loadable.
-DG
David Greenman
Co-founder, The FreeBSD Project - http://www.freebsd.org
Manufacturer of high-performance Internet servers - http://www.terasolutions.com
Pave the road of life with opportunities.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 12:23: 9 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
by hub.freebsd.org (Postfix) with ESMTP
id E343937C565; Fri, 14 Jul 2000 12:23:06 -0700 (PDT)
(envelope-from mjacob@feral.com)
Received: from semuta.feral.com (semuta [192.67.166.70])
by feral.com (8.9.3/8.9.3) with ESMTP id MAA15851;
Fri, 14 Jul 2000 12:23:05 -0700
Date: Fri, 14 Jul 2000 12:20:53 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: David Greenman <dg@root.com>
Cc: Mike Smith <msmith@FreeBSD.ORG>,
Bernd Walter <ticso@cicely8.cicely.de>, freebsd-alpha@FreeBSD.ORG
Subject: Re: fxp0 hangs on a PC164 using STABLE
In-Reply-To: <200007141906.MAA17569@implode.root.com>
Message-ID: <Pine.BSF.4.05.10007141220150.5888-100000@semuta.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
> >I'm sorry you don't wish to support this on the alpha.
>
> Me too. With 500% of my time committed, I'm forced to realize my
> limitations, however.
What, only 500%? Jeez.. you're being *far* too easy on yourself... :-)
(1000a"Me Too")
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 12:23:48 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from implode.root.com (root.com [209.102.106.178])
by hub.freebsd.org (Postfix) with ESMTP
id 403E737C0E7; Fri, 14 Jul 2000 12:23:45 -0700 (PDT)
(envelope-from dg@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
by implode.root.com (8.8.8/8.8.5) with ESMTP id MAA17605;
Fri, 14 Jul 2000 12:10:46 -0700 (PDT)
Message-Id: <200007141910.MAA17605@implode.root.com>
To: Bernd Walter <ticso@cicely8.cicely.de>
Cc: Don <don@blacksun.org>, Matthew Jacob <mjacob@feral.com>,
Mike Smith <msmith@FreeBSD.ORG>, freebsd-alpha@FreeBSD.ORG
Subject: Re: fxp0 hangs on a PC164 using STABLE
In-reply-to: Your message of "Fri, 14 Jul 2000 20:52:42 +0200."
<20000714205242.B9315@cicely8.cicely.de>
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Fri, 14 Jul 2000 12:10:46 -0700
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
>On Fri, Jul 14, 2000 at 02:02:54PM -0400, Don wrote:
>> > Do these fxp cards run on Alpha boxes?
>> No I appologize. This was in response to the comment about instability on
>> x86 and was directed towards David.
>
>See -current archives.
>There were some Mails that mentioned this to happen when using IPv6.
>Anyway I never was able to see that problem myself since 4.0-RELEASE
>on x86.
I believe the issues related to IPv6 were solved long ago. They were caused
by some bad assumptions (in the IPv6 code) regarding driver startup
initialization. I don't believe that there were any intermittant problems,
however - it just didn't work at all with IPv6.
-DG
David Greenman
Co-founder, The FreeBSD Project - http://www.freebsd.org
Manufacturer of high-performance Internet servers - http://www.terasolutions.com
Pave the road of life with opportunities.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 13:31:50 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from front2.grolier.fr (front2.grolier.fr [194.158.96.52])
by hub.freebsd.org (Postfix) with ESMTP
id A3E1C37C6CF; Fri, 14 Jul 2000 13:31:43 -0700 (PDT)
(envelope-from groudier@club-internet.fr)
Received: from Guyancourt-1-234.club-internet.fr (Guyancourt-1-234.club-internet.fr [195.36.205.234])
by front2.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id WAA29945;
Fri, 14 Jul 2000 22:31:23 +0200 (MET DST)
Date: Fri, 14 Jul 2000 22:10:37 +0200 (CEST)
From: =?ISO-8859-1?Q?G=E9rard_Roudier?= <groudier@club-internet.fr>
X-Sender: groudier@linux.local
To: Andrew Gallatin <gallatin@cs.duke.edu>
Cc: mjacob@feral.com, David Greenman <dg@root.com>,
Mike Smith <msmith@FreeBSD.ORG>,
Bernd Walter <ticso@cicely8.cicely.de>, freebsd-alpha@FreeBSD.ORG
Subject: Re: fxp0 hangs on a PC164 using STABLE
In-Reply-To: <14703.24005.384580.704375@grasshopper.cs.duke.edu>
Message-ID: <Pine.LNX.4.10.10007142126001.3025-100000@linux.local>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
On Fri, 14 Jul 2000, Andrew Gallatin wrote:
> Matthew Jacob writes:
> >=20
> > > "Providing support" to me means not only getting it working, but =
also
> > > making sure that it continues to work over time and putting the effo=
rt in
> > > to fix it if it should break.
> >=20
> > Well, this starts us diverging toward meta-issues.
> >=20
> > I'm sorry you don't wish to support this on the alpha.
>=20
> For what its worth, I just stole an fxp from an x86. I'm going to try=20
> to getting working, but I make no promises.
I have no documentation about this chip, but last time I looked into the
code of this driver, I seem to understand that the device and CPU use some
list or queue in main memory. In such situation, software drivers must be
aware of what memory accesses are ATOMIC (also from BUS) and what are not.
They must also be aware that modern CPUs reorder LOADs and STOREs. The
only thing I saw that seem to deal with ordering is some 'volatile'. As
you know, 'volatile' is just some compiler optimization barrier and should
not be used any longer in drivers. We should instead use explicit compiler
barriers and explicit memory barriers when needed.
For example, imagine the following scenario:
Device that does the right thing from PCI BUS:
=09write USER DATA to memory
=09write STATUS DATA to memory
=09write COMPLETION FLAG to memory
(A)->=09perform a READ to flush posted writes
=09set INTERRUPT FLAG
C code ordering unaware:
LOOP:
=09read INTERRUPT FLAG from IO register
=09if not set RETURN
=09read COMPLETION=09FLAG from memory
=09read STATUS DATA
=09etc ...
=09goto LOOP
C code ordering aware:
LOOP:
=09read INTERRUPT FLAG from IO register
=09if not set RETURN
=09clear(write) INTERRUPT FLAG (if the read is not self-clearing)
(B)->=09perform a READ from BUS to flush posted writes
=09read COMPLETION=09FLAG from memory
(C)->=09MEMORY BARRIER
=09read STATUS DATA from memory
=09etc ...
=09goto LOOP
(A) and (B) posted write flushing prevents from losing interrupt condition
on bridges that donnot flush posted writes UPSTREAM, as on Alpha.
On bridges that also flushed posted write UPSTREAM, only (A) or (B) is=20
needed. Basically if the write that CLEARS the INTERRUPT FLAG is to long
delayed, it may just clear the INTERRUPT FLAG that address the NEXT
completion.
The MEMORY BARRIER protects against not desirable reordering of LOADS by
the CPU. Basically the CPU can read the STATUS DATA prior to the
COMPLETION FLAG from memory and then the C code may just have to deal with
stale STATUS DATA.
The above is an example. May-be it does not apply to the fxp driver.
I know that I am paranoid ;-), but it seems to me that numerous drivers
are not carefull enough about ordering.
G=E9rard.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 13:45:30 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20])
by hub.freebsd.org (Postfix) with ESMTP
id CA30237C0D6; Fri, 14 Jul 2000 13:45:25 -0700 (PDT)
(envelope-from wkb@freebie.demon.nl)
Received: from [212.238.54.101] (helo=freebie.demon.nl)
by post.mail.nl.demon.net with smtp (Exim 3.14 #2)
id 13DCKm-0005sg-00; Fri, 14 Jul 2000 20:45:21 +0000
Received: (from wkb@localhost)
by freebie.demon.nl (8.9.3/8.9.3) id WAA95165;
Fri, 14 Jul 2000 22:45:20 +0200 (CEST)
(envelope-from wkb)
Date: Fri, 14 Jul 2000 22:45:20 +0200
From: Wilko Bulte <wkb@freebie.demon.nl>
To: Andrew Gallatin <gallatin@cs.duke.edu>, obrien@freebsd.org
Cc: FreeBSD-alpha mailing list <freebsd-alpha@freebsd.org>
Subject: Re: unaligned access fault panic during boot?
Message-ID: <20000714224520.A91392@freebie.demon.nl>
Reply-To: wilko@freebsd.org
References: <14700.58027.671131.446614@grasshopper.cs.duke.edu> <Pine.BSF.4.05.10007121427430.2727-100000@semuta.feral.com> <20000712234044.C2459@freebie.demon.nl> <14700.58892.93749.263135@grasshopper.cs.duke.edu> <20000714223034.A39610@freebie.demon.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <20000714223034.A39610@freebie.demon.nl>; from wkb@freebie.demon.nl on Fri, Jul 14, 2000 at 10:30:34PM +0200
X-OS: FreeBSD 4.0-STABLE
X-PGP: finger wilko@freebsd.org
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
[forgot to cc -alpha]
OK... it still panics. But I noticed something during the make of the
kernel that I don't like:
miata#time make
cc -c -x assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls
-Wnested-e
xterns -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
-Wcast
-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../..
-I../../../include
-D_KERNEL -include opt_global.h -elf -mno-fp-regs -ffixed-8 -Wa,-mev56
../../
alpha/alpha/locore.s
../../alpha/alpha/locore.s: Assembler messages:
../../alpha/alpha/locore.s:216: Warning: Used $at without ".set noat"
../../alpha/alpha/locore.s:278: Warning: Used $at without ".set noat"
Could this be a problem?
--
Wilko Bulte http://www.freebsd.org "Do, or do not. There is no
try"
wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes
Back
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 13:58:22 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
by hub.freebsd.org (Postfix) with ESMTP
id 88DCD37BB98; Fri, 14 Jul 2000 13:58:18 -0700 (PDT)
(envelope-from mjacob@feral.com)
Received: from semuta.feral.com (semuta [192.67.166.70])
by feral.com (8.9.3/8.9.3) with ESMTP id NAA16298;
Fri, 14 Jul 2000 13:58:17 -0700
Date: Fri, 14 Jul 2000 13:56:05 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: wilko@FreeBSD.ORG
Cc: Andrew Gallatin <gallatin@cs.duke.edu>, obrien@FreeBSD.ORG,
FreeBSD-alpha mailing list <freebsd-alpha@FreeBSD.ORG>
Subject: Re: unaligned access fault panic during boot?
In-Reply-To: <20000714224520.A91392@freebie.demon.nl>
Message-ID: <Pine.BSF.4.05.10007141355450.5888-100000@semuta.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
Don't worry about it. It's a harmless bug in the gnu toolchain.
On Fri, 14 Jul 2000, Wilko Bulte wrote:
> [forgot to cc -alpha]
>
> OK... it still panics. But I noticed something during the make of the
> kernel that I don't like:
>
> miata#time make
> cc -c -x assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls
> -Wnested-e
> xterns -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
> -Wcast
> -qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../..
> -I../../../include
> -D_KERNEL -include opt_global.h -elf -mno-fp-regs -ffixed-8 -Wa,-mev56
> ../../
> alpha/alpha/locore.s
> ../../alpha/alpha/locore.s: Assembler messages:
> ../../alpha/alpha/locore.s:216: Warning: Used $at without ".set noat"
> ../../alpha/alpha/locore.s:278: Warning: Used $at without ".set noat"
>
> Could this be a problem?
>
> --
> Wilko Bulte http://www.freebsd.org "Do, or do not. There is no
> try"
> wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes
> Back
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-alpha" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 14:16:41 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51])
by hub.freebsd.org (Postfix) with ESMTP id 16FE937C55F
for <freebsd-alpha@FreeBSD.ORG>; Fri, 14 Jul 2000 14:16:39 -0700 (PDT)
(envelope-from msmith@mass.osd.bsdi.com)
Received: from mass.osd.bsdi.com (localhost [127.0.0.1])
by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id OAA05782;
Fri, 14 Jul 2000 14:25:05 -0700 (PDT)
(envelope-from msmith@mass.osd.bsdi.com)
Message-Id: <200007142125.OAA05782@mass.osd.bsdi.com>
X-Mailer: exmh version 2.1.1 10/15/1999
To: dg@root.com
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: fxp0 hangs on a PC164 using STABLE
In-reply-to: Your message of "Fri, 14 Jul 2000 10:07:36 PDT."
<200007141707.KAA16976@implode.root.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 14 Jul 2000 14:25:05 -0700
From: Mike Smith <msmith@freebsd.org>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
> >fxp is not supported on the Alpha, and known to be unreliable there.
> >Contact the maintainer or use a different card. FWIW, this actually
> >sounds like an issue that's been seen on x86 as well.
>
> It does? I've never heard of a bug report like this for x86 and in fact I'm
> not aware of any bugs in the driver for x86.
It's been described many times, actually. It sounds a lot like a bad
interaction between either the card or the driver and the hub/switch at
the other end, however it's shown up on a reasonably regular basis.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 14:23:35 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
by hub.freebsd.org (Postfix) with ESMTP
id 902FC37C755; Fri, 14 Jul 2000 14:23:30 -0700 (PDT)
(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id RAA27764;
Fri, 14 Jul 2000 17:23:22 -0400 (EDT)
Received: (from gallatin@localhost)
by grasshopper.cs.duke.edu (8.9.3/8.9.1) id RAA35266;
Fri, 14 Jul 2000 17:23:22 -0400 (EDT)
(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Fri, 14 Jul 2000 17:23:21 -0400 (EDT)
To: dg@root.com
Cc: mjacob@feral.com, David Greenman <dg@root.com>,
Mike Smith <msmith@FreeBSD.ORG>,
Bernd Walter <ticso@cicely8.cicely.de>, freebsd-alpha@FreeBSD.ORG
Subject: Re: fxp0 hangs on a PC164 using STABLE
In-Reply-To: <200007141908.MAA17583@implode.root.com>
References: <14703.24005.384580.704375@grasshopper.cs.duke.edu>
<200007141908.MAA17583@implode.root.com>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid
Message-ID: <14703.31808.282545.767536@grasshopper.cs.duke.edu>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
David Greenman writes:
> >David: Is the fxp module unloadable, or will it crash the machine in
> >strange and mysterious ways upon unload, like most of the network
> >drivers do?
>
It looks like its close to being unloadable, but it somehow clobers
the intr. of a device sharing the same irq. I'm not at all sure
that's the fxp driver's fault. Let's not worry about that for now.
As for the bug. I can duplicate it I run both the sender & receiver
fairly hard, like 2 100Mb/tcp connections running in opposite
directions. When I do this, it looks like the xmit side locks up but
the recv. side is at least partially OK. And I'm still getting stats
updates.
From looking at the fxp stats in a debugger, it looks like its still
getting packets (fxp_stats.rx_good is non-zero if I throw packets at
the box). There are no collisions, ierrors, underruns, or anything
else that looks at all suspicious. Just 128 packets waiting on
tx_queued.
If I call fxp_intr() from ddb, there's no improvement. I can bring
the interface back by running tcpdump.
At the top of fxp_stats_update(), you have a comment regarding how
expensive it is to get "_all_ of the statistics it maintains"
Does sc->fxp_stats include all of them, or are there others that
might shed some light on the problem?
Do any of the symptoms sound familiar?
Also, are there any docs on this thing that are available? I've
searched intel's web site & cannot seem to find anything..
Thanks,
Drew
------------------------------------------------------------------------------
Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin
Duke University Email: gallatin@cs.duke.edu
Department of Computer Science Phone: (919) 660-6590
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message
From owner-freebsd-alpha Fri Jul 14 15:47:35 2000
Delivered-To: freebsd-alpha@freebsd.org
Received: from implode.root.com (root.com [209.102.106.178])
by hub.freebsd.org (Postfix) with ESMTP
id CCCC837C00E; Fri, 14 Jul 2000 15:47:31 -0700 (PDT)
(envelope-from dg@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
by implode.root.com (8.8.8/8.8.5) with ESMTP id PAA18393;
Fri, 14 Jul 2000 15:35:27 -0700 (PDT)
Message-Id: <200007142235.PAA18393@implode.root.com>
To: Mike Smith <msmith@FreeBSD.ORG>
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: fxp0 hangs on a PC164 using STABLE
In-reply-to: Your message of "Fri, 14 Jul 2000 14:25:05 PDT."
<200007142125.OAA05782@mass.osd.bsdi.com>
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Fri, 14 Jul 2000 15:35:27 -0700
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
>> >fxp is not supported on the Alpha, and known to be unreliable there.
>> >Contact the maintainer or use a different card. FWIW, this actually
>> >sounds like an issue that's been seen on x86 as well.
>>
>> It does? I've never heard of a bug report like this for x86 and in fact I'm
>> not aware of any bugs in the driver for x86.
>
>It's been described many times, actually. It sounds a lot like a bad
>interaction between either the card or the driver and the hub/switch at
>the other end, however it's shown up on a reasonably regular basis.
There are some known issues with autonegotiation, which have very little to
do with the card or driver, but nothing that is intermittant and results in
the card wedging. Can you point me to the most recent report of the problem
you're talking about? Because I sure have no idea what you're refering to.
-DG
David Greenman
Co-founder, The FreeBSD Project - http://www.freebsd.org
Manufacturer of high-performance Internet servers - http://www.terasolutions.com
Pave the road of life with opportunities.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message