From owner-freebsd-alpha Sun Oct 17 4: 6:50 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id A5EB615260 for ; Sun, 17 Oct 1999 04:06:35 -0700 (PDT) (envelope-from bottemanne@capitolonline.nl) Received: from capitolonline.nl ([195.121.169.127]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA198E for ; Sun, 17 Oct 1999 13:06:31 +0200 Message-ID: <3809BC20.65270DB8@capitolonline.nl> Date: Sun, 17 Oct 1999 13:08:00 +0100 From: Aernoudt Bottemanne X-Mailer: Mozilla 4.04 [en] (OS/2; I) MIME-Version: 1.0 To: freebsd-alpha@FreeBSD.ORG Subject: ide zip drive support in PWS 433a Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Does anybody have a working ide zip drive ? I would like to use one in a Digital PWS 433a. (could not find it in supported list, and before buying it.....) Thanks, Aernoudt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Oct 17 6:26:48 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 630FA14E46 for ; Sun, 17 Oct 1999 06:26:42 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id PAA29388; Sun, 17 Oct 1999 15:17:18 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id PAA72027; Sun, 17 Oct 1999 15:14:25 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199910171314.PAA72027@yedi.iaf.nl> Subject: Re: hanging buildworld? In-Reply-To: from Doug Rabson at "Oct 16, 1999 7:43:21 pm" To: dfr@nlsystems.com (Doug Rabson) Date: Sun, 17 Oct 1999 15:14:25 +0200 (CEST) Cc: freebsd-alpha@freebsd.org X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Doug Rabson wrote ... > On Sat, 16 Oct 1999, Wilko Bulte wrote: > > > As Doug Rabson wrote ... > > > On Fri, 15 Oct 1999, Wilko Bulte wrote: > > > > The process sitting there is the one in 'objtrm' , cpp at pid 10569. > > > > The machine itself keeps running just fine. > > > > Has anybody else ever seen this? This is sort-of repeatable on my NoName. > > > I think other people have reported similar problems. There must be a place > > > in the VM/VFS where a counter is being updated without using the atomic > > > macros. I'll talk to Matt about it at the conference. > > > > OK, I'm not alone then :) It also happened a couple of times already that > > a process (in this case csh and once also vgrind) went into a infinite loop. > > This was on a different Alpha box BTW, but with the same -current src tree. > > Could this be a manifestation of the same basic cause? > > I got an 'objde1' hang today which is probably caused by the same thing. > I have a good idea of how to track this thing down but I probably won't > get to it until after FreeBSDCon. As for the csh/vgrind problem: looks that's been solved by manually 'make'ing and installing csh. I'm now rerunning buildworld on the machine that suffered from the looping csh. Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sun Oct 17 19: 0:38 1999 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 9000F14DE9; Sun, 17 Oct 1999 19:00:25 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grits.cs.duke.edu (grits.cs.duke.edu [152.3.145.36]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id WAA12740; Sun, 17 Oct 1999 22:00:23 -0400 (EDT) Received: (from gallatin@localhost) by grits.cs.duke.edu (8.9.3/8.9.1) id WAA35506; Sun, 17 Oct 1999 22:00:23 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Sun, 17 Oct 1999 22:00:23 -0400 (EDT) To: sos@freebsd.org Cc: alpha@freebsd.org, "Erik H. Bakke" Subject: workaround for ata driver woes on alpha X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14346.31193.248797.237477@grits.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org S=F8ren, There's a problem with the ata-driver on alphas. Under heavy disk load, the machine will complain "ad_timeout: lost disk contact - resetting" and then promptly panic & leave something like the following stack trace: panic: trap #0 0xfffffc0000386c2c in boot (howto=3D260) at ../../kern/kern_shutdow= n.c:278 278 savectx(&dumppcb); (kgdb) bt #0 0xfffffc0000386c2c in boot (howto=3D260) at ../../kern/kern_shutdow= n.c:278 #1 0xfffffc0000344530 in db_fncall (dummy1=3D0, dummy2=3D0, dummy3=3D0= , dummy4=3D0x0) at ../../ddb/db_command.c:532 #2 0xfffffc00003441a4 in db_command (last_cmdp=3D0xfffffc00005b1a60,=20= cmd_table=3D0x0, aux_cmd_tablep=3D0xfffffc00005d6990) at ../../ddb/db_command.c:333 #3 0xfffffc0000344320 in db_command_loop () at ../../ddb/db_command.c:= 455 #4 0xfffffc0000347ff8 in db_trap (type=3D0, code=3D0) at ../../ddb/db_= trap.c:71 #5 0xfffffc00005051c8 in kdb_trap (a0=3D1, a1=3D1, a2=3D9600, entry=3D= 3,=20 regs=3D0xfffffe0011955500) at ../../alpha/alpha/db_interface.c:194 #6 0xfffffc0000512d58 in trap (a0=3D1, a1=3D15, a2=3D9600, entry=3D3,=20= framep=3D0xfffffe0011955500) at ../../alpha/alpha/trap.c:285 #7 0xfffffc0000505ad0 in XentIF () at ../../alpha/alpha/exception.s:63= #8 0xfffffc000050538c in Debugger (msg=3D0x0) at ../../alpha/alpha/db_interface.c:256 #9 0xfffffc0000387354 in panic (fmt=3D0xfffffc00005a76fc "trap") at ../../kern/kern_shutdown.c:528 #10 0xfffffc00005131ec in trap (a0=3D40, a1=3D1, a2=3D0, entry=3D2,=20 framep=3D0xfffffe0011955740) at ../../alpha/alpha/trap.c:530 #11 0xfffffc0000505b2c in XentMM () at ../../alpha/alpha/exception.s:94= #12 0xfffffc0000523b04 in ad_transfer (request=3D0xfffffe00087e3c00) at ../../dev/ata/ata-disk.c:431 #13 0xfffffc0000521d38 in ata_start (scp=3D0xfffffe0008713400) at ../../dev/ata/ata-all.c:583 #14 0xfffffc0000522338 in ata_reinit (scp=3D0xfffffe0008713400) at ../../dev/ata/ata-all.c:716 #15 0xfffffc000052448c in ad_timeout (request=3D0xfffffe00087e3c00) at ../../dev/ata/ata-disk.c:648 #16 0xfffffc000039025c in softclock () at ../../kern/kern_timeout.c:131= #17 0xfffffc0000376d70 in hardclock (frame=3D0xfffffe00119559e0) at ../../kern/kern_clock.c:253 #18 0xfffffc000051564c in handleclock (arg=3D0xfffffe00119559e0) at ../../alpha/alpha/clock.c:266 #19 0xfffffc0000513e34 in interrupt (a0=3D0, a1=3D1536, a2=3D1844673967= 5668704635,=20 framep=3D0xfffffe00119559e0) at ../../alpha/alpha/interrupt.c:101 #20 0xfffffc0000505afc in XentInt () at ../../alpha/alpha/exception.s:7= 8 I admit to not understanding callouts, so you might want to take this theory with a grain of salt: I believe what is happening is that ad_timeout() gets called (quite prematurely) at spl0. While ad_timout() is executing, the interrupt comes in for the request in question. The interrupt handler frees the request that the ad_timeout() call chain is currently operating on (or otherwise messes with it). The request is then corrupted, and chaos (machine check, or a trap for an invalid access) ensues. I'm tempted to wrap ad_timeout() in splbio() but there is still a window when ad_callout() is being called that we'll be at spl0 (is this right, is it called at spl0? this is what I don't know..) Anyway, we see this on the alpha because the timeout is hardcoded to fire after 300 ticks. This is a little under 3 seconds on an x86 (typically hz<=3D128) but it is less than 1/3 of a second on an alpha (typically hz>=3D1024). The following patch levels the playing field &= seems to "fixe" the problem on alpha. (at least I'm now able to untar ports & then rm -rf the tree). Index: sys/dev/ata/ata-disk.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/dev/ata/ata-disk.c,v retrieving revision 1.31 diff -u -r1.31 ata-disk.c --- ata-disk.c 1999/10/10 18:08:36 1.31 +++ ata-disk.c 1999/10/18 01:13:48 @@ -417,7 +417,7 @@ if (request->donecount =3D=3D 0) { =20 /* start timeout for this transfer */ - request->timeout_handle =3D timeout((timeout_t*)ad_timeout, req= uest, 300); + request->timeout_handle =3D timeout((timeout_t*)ad_timeout, req= uest, 3*hz); =20 /* setup transfer parameters */ count =3D howmany(request->bytecount, DEV_BSIZE); Drew -----------------------------------------------------------------------= ------- Andrew Gallatin, Sr Systems Programmer=09http://www.cs.duke.edu/~gallat= in Duke University=09=09=09=09Email: gallatin@cs.duke.edu Department of Computer Science=09=09Phone: (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 Oct 18 3:50:47 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from post.bgnett.no (post.bgnett.no [194.54.96.133]) by hub.freebsd.org (Postfix) with ESMTP id 7C39D14FA0; Mon, 18 Oct 1999 03:50:36 -0700 (PDT) (envelope-from erik@habatech.no) Received: from bsdbox.habatech.no ([62.92.133.3]) by post.bgnett.no (8.8.8/8.8.8) with ESMTP id MAA16244; Mon, 18 Oct 1999 12:50:29 +0200 (CEST) (envelope-from erik@habatech.no) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <14346.31193.248797.237477@grits.cs.duke.edu> Date: Mon, 18 Oct 1999 12:50:12 +0200 (CEST) From: "Erik H. Bakke" To: Andrew Gallatin Subject: RE: workaround for ata driver woes on alpha Cc: alpha@freebsd.org, sos@freebsd.org Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The patch seems to work for me, just have to put it through the "make -j4 world" test. If it survives, it is probably healthy :) ===========================+================+=============================== Erik H. Bakke | | To be or not to be... Senior Consultant/Developer|erik@habatech.no| Is simply a question of Habatech AS | | binary logic ===========================+================+============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Oct 18 6:37: 9 1999 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 8693414BC5 for ; Mon, 18 Oct 1999 06:37:06 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grits.cs.duke.edu (grits.cs.duke.edu [152.3.145.36]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id JAA22066; Mon, 18 Oct 1999 09:37:04 -0400 (EDT) Received: (from gallatin@localhost) by grits.cs.duke.edu (8.9.3/8.9.1) id JAA54708; Mon, 18 Oct 1999 09:37:04 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 18 Oct 1999 09:37:04 -0400 (EDT) To: mjacob@feral.com Cc: alpha@freebsd.org Subject: Re: workaround for ata driver woes on alpha In-Reply-To: References: <14346.31193.248797.237477@grits.cs.duke.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14347.6330.820928.627692@grits.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob writes: > > actually, this happens right away for me w/o even heavy disk load. > > callouts should not be happening at spl0, should they? shouldn't they > happen at the lowest level that is *not* non-interrupt context? At any > rate, callouts have to always protect the resources they might share with > interrupts (whether via spls or locks) like any other shared resource > problem, no? > > -matt Sorry. spl0 was a typo. I'd meant to say softclock. Eg, ALPHA_PSL_IPL_SOFT. hardclock() calls (void)splsoftclock(); to set the ipl to ALPHA_PSL_IPL_SOFT just before calling softclock. Softclock itself itself goes to splhigh() while it processes the callouts. But just before it calls the timeout function it lowers the ipl back to ALPHA_PSL_IPL_SOFT: 130 splx(s); 131 c_func(c_arg); 132 s = splhigh(); According to alpha/include/alpha_cpu.h: #define ALPHA_PSL_IPL_0 0x0000 /* all interrupts enabled */ #define ALPHA_PSL_IPL_SOFT 0x0001 /* software ints disabled */ #define ALPHA_PSL_IPL_IO 0x0004 /* I/O dev ints disabled */ #define ALPHA_PSL_IPL_CLOCK 0x0005 /* clock ints disabled */ #define ALPHA_PSL_IPL_HIGH 0x0006 /* all but mchecks disabled */ So we should be open to device interrupts when the ad_timeout() routine is called. I'm pretty sure this is what is happening for the following reason: I bzero() the request structure in ad_interrupt() just prior to freeing it (around line 593 of ata-disk.c). Then at the top of ad_timeout() I print out some values from the request. When ad_timeout() is called, I see non-zero values for the request fields that I have printed, but my panic changes from a machine check to a memory access fault when attempting to deref a pointer in the request struct that was bzeroed. If, after the crash, I examine the fields that I'd printed out, they are now zero. However, all the fields are not zero -- request->retries == 1, for example. I got the crashdump via 'call boot(RB_NOSYNC|RB_DUMP)' in the debugger, so I do not think that sync'ing disks changed anything. I think there is a serious problem with the ad_timeout() function in the case where the request has actually completed & the timeout was too short. ad_timeout() has no way to know if the request it has been passed is still valid, or has been deallocated. Wrapping the function in splbio() will only narrow the race, not close it because we're still going to be at splsoftclock when the function is called. I think setting the timeout to a reasonable value is a good workaround, but I'm still concerned about very slow hardware.. 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 Oct 18 7:26:39 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id CA4A115175; Mon, 18 Oct 1999 07:26:36 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id HAA22024; Mon, 18 Oct 1999 07:26:34 -0700 Date: Mon, 18 Oct 1999 07:26:35 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin , sos@freebsd.org Cc: alpha@freebsd.org Subject: Re: workaround for ata driver woes on alpha In-Reply-To: <14347.6330.820928.627692@grits.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (I have not yet looked at the actual source...) > I think there is a serious problem with the ad_timeout() function in > the case where the request has actually completed & the timeout was > too short. ad_timeout() has no way to know if the request it has been > passed is still valid, or has been deallocated. Wrapping the function > in splbio() will only narrow the race, not close it because we're > still going to be at splsoftclock when the function is called. I > think setting the timeout to a reasonable value is a good workaround, > but I'm still concerned about very slow hardware.. No, lengthening the timeout, while possibly correct for trying to achieve the same length of timeout on alpha as in i386, will *never* solve window problems- it just makes them more infrequent which is, in fact, far more dangerous to an OS than the outright panic (why? Think about it- if you make a problem just *rare* instead of really going away, you curse the platform it occurs on with an aura of unreliabilty so that people are just too uneasy to depend on it...)..... (goes off and looks at source....) Yep. This is broken. The timeout can still run when a request has been deallocated. This whole area of the code needs to be rewritten/rethought. I wouldn't run it, even with the timeout extended, without that. I would recommend hanging requests off the softc in a list (if it's more than one per ata instance) or just as a pointer *which gets nulled if untimeout is called* so that splbio protection can offer mutex exclusion on the callout vs. the IDE interrupt thread looking through the currently active list. If ad_interrupt runs and calls untimeout on an already active callout it will make the callout thread not find anything to whine about (but only if the callout thread knows where to looK). You should note that this would still be problematic if there ever were identical request block pointers. Also, IMO, using a timeout per I/O request is a heavy load for a system unless you need the precise accuracy. I prefer a general periodic timer per device instance and timeout counts for all active commands for that device. Soren- this is your stuff isn't it- what have we misunderstood? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Oct 18 8:54: 7 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id 204E514C2B for ; Mon, 18 Oct 1999 08:53:51 -0700 (PDT) (envelope-from bottemanne@capitolonline.nl) Received: from capitolonline.nl ([195.121.168.129]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA4051; Mon, 18 Oct 1999 17:53:50 +0200 Message-ID: <380B50F8.4335FDB5@capitolonline.nl> Date: Mon, 18 Oct 1999 17:55:20 +0100 From: Aernoudt Bottemanne X-Mailer: Mozilla 4.04 [en] (OS/2; I) MIME-Version: 1.0 To: Andrew Gallatin Cc: alpha@freebsd.org Subject: cdrom and zip (both ide) problem References: <14346.31193.248797.237477@grits.cs.duke.edu> <14347.6330.820928.627692@grits.cs.duke.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, During system installation FreeBSD can not find the cdrom device (nor the zip drive). The srm console does have the devices (and for example I can upgrade the firmware from the ide cdrom drive....) Any suggestions on how to fix this ? Thanks, Aernoudt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Oct 18 9: 5:35 1999 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 65AD9150F1 for ; Mon, 18 Oct 1999 09:05:30 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grits.cs.duke.edu (grits.cs.duke.edu [152.3.145.36]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id MAA25845; Mon, 18 Oct 1999 12:05:27 -0400 (EDT) Received: (from gallatin@localhost) by grits.cs.duke.edu (8.9.3/8.9.1) id MAA58285; Mon, 18 Oct 1999 12:05:27 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 18 Oct 1999 12:05:27 -0400 (EDT) To: Aernoudt Bottemanne Cc: alpha@freebsd.org Subject: Re: cdrom and zip (both ide) problem In-Reply-To: <380B50F8.4335FDB5@capitolonline.nl> References: <14346.31193.248797.237477@grits.cs.duke.edu> <14347.6330.820928.627692@grits.cs.duke.edu> <380B50F8.4335FDB5@capitolonline.nl> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14347.17444.883642.500165@grits.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Aernoudt Bottemanne writes: > Hi, > > During system installation FreeBSD can not find the cdrom device (nor the zip > drive). > The srm console does have the devices (and for example I can upgrade the firmware > from > the ide cdrom drive....) > Any suggestions on how to fix this ? > > Thanks, > Aernoudt > Great. Answer enough questions & people start mailing right to you... ;-) Ide on alpha requires the new ata driver. In 4.0, we don't consider the ata driver mature enough to include in a GENERIC or installation kernel. Also, an install to an ide disk has never been tested (to the best of my knowledge). Once you install the system, you can re-build your kernel with the options: # ATA and ATAPI devices # This is work in progress, use at your own risk. # It currently reuses the majors of wd.c and friends. # It cannot co-exist with the old system in one kernel. # You only need one "controller ata0" for it to find all # PCI devices on modern machines. controller ata0 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives device atapifd0 # ATAPI floppy drives device atapist0 # ATAPI tape drives The kernel should then see your IDE devices. If you want to use -stable, you can give up now. IDE devices will not work on alpha in 3.x w/o signifigant effort. 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 Oct 18 10: 0:47 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id 8389F14CBB for ; Mon, 18 Oct 1999 10:00:43 -0700 (PDT) (envelope-from bottemanne@capitolonline.nl) Received: from capitolonline.nl ([195.121.169.135]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA11E9; Mon, 18 Oct 1999 19:00:41 +0200 Message-ID: <380B60A3.F742EBBF@capitolonline.nl> Date: Mon, 18 Oct 1999 19:02:11 +0100 From: Aernoudt Bottemanne X-Mailer: Mozilla 4.04 [en] (OS/2; I) MIME-Version: 1.0 To: Andrew Gallatin Cc: alpha@freebsd.org Subject: Re: cdrom and zip (both ide) problem References: <14346.31193.248797.237477@grits.cs.duke.edu> <14347.6330.820928.627692@grits.cs.duke.edu> <380B50F8.4335FDB5@capitolonline.nl> <14347.17444.883642.500165@grits.cs.duke.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Andrew, So it should work in 3.x current or 4.0 current ? Unfortunately every time after I install FreeBSD it does not boot at all..... The error message = "Kernel stack not valid" I had hoped to get the ide CD working, because I have to install over and over.... Andrew Gallatin wrote: > Aernoudt Bottemanne writes: > > Hi, > > > > During system installation FreeBSD can not find the cdrom device (nor the zip > > drive). > > The srm console does have the devices (and for example I can upgrade the firmware > > from > > the ide cdrom drive....) > > Any suggestions on how to fix this ? > > > > Thanks, > > Aernoudt > > > > Great. Answer enough questions & people start mailing right to > you... ;-) > > Ide on alpha requires the new ata driver. > > In 4.0, we don't consider the ata driver mature enough to include in a > GENERIC or installation kernel. Also, an install to an ide disk has > never been tested (to the best of my knowledge). Once you install the > system, you can re-build your kernel with the options: > > # ATA and ATAPI devices > # This is work in progress, use at your own risk. > # It currently reuses the majors of wd.c and friends. > # It cannot co-exist with the old system in one kernel. > # You only need one "controller ata0" for it to find all > # PCI devices on modern machines. > controller ata0 > device atadisk0 # ATA disk drives > device atapicd0 # ATAPI CDROM drives > device atapifd0 # ATAPI floppy drives > device atapist0 # ATAPI tape drives > > The kernel should then see your IDE devices. > > If you want to use -stable, you can give up now. IDE devices will not > work on alpha in 3.x w/o signifigant effort. > > 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 Oct 18 10:14:43 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from tuden.freebsd.dk (picasso.transbay.net [209.133.53.6]) by hub.freebsd.org (Postfix) with ESMTP id 8322D14EAE; Mon, 18 Oct 1999 10:14:40 -0700 (PDT) (envelope-from sos@tuden.freebsd.dk) Received: (from sos@localhost) by tuden.freebsd.dk (8.9.3/8.9.2) id TAA00441; Mon, 18 Oct 1999 19:14:11 +0200 (CEST) (envelope-from sos) From: Søren Schmidt Message-Id: <199910181714.TAA00441@tuden.freebsd.dk> Subject: Re: workaround for ata driver woes on alpha In-Reply-To: from Matthew Jacob at "Oct 18, 1999 07:26:35 am" To: mjacob@feral.com Date: Mon, 18 Oct 1999 19:14:09 +0200 (CEST) Cc: gallatin@cs.duke.edu (Andrew Gallatin), sos@freebsd.org, alpha@freebsd.org Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Matthew Jacob wrote: > No, lengthening the timeout, while possibly correct for trying to achieve > the same length of timeout on alpha as in i386, will *never* solve window > problems- it just makes them more infrequent which is, in fact, far more > dangerous to an OS than the outright panic (why? Think about it- if you > make a problem just *rare* instead of really going away, you curse the > platform it occurs on with an aura of unreliabilty so that people are just > too uneasy to depend on it...)..... Well, the problem is that I didn't use hz to get the right timeout (there the patch is correct) I missed that one sorry. There could be a window problem, but it is highly unlikely that an ATA disk is going to respond with an interrupt after the timeout happend, but its not impossible. > I would recommend hanging requests off the softc in a list (if it's more > than one per ata instance) or just as a pointer *which gets nulled if > untimeout is called* so that splbio protection can offer mutex exclusion > on the callout vs. the IDE interrupt thread looking through the currently > active list. If ad_interrupt runs and calls untimeout on an already > active callout it will make the callout thread not find anything to > whine about (but only if the callout thread knows where to looK). You > should note that this would still be problematic if there ever were > identical request block pointers. Also, IMO, using a timeout per I/O > request is a heavy load for a system unless you need the precise accuracy. > I prefer a general periodic timer per device instance and timeout counts > for all active commands for that device. > > Soren- this is your stuff isn't it- what have we misunderstood? This all needs more thought, I've just not had the time yet to do more about it. Hopefully when I return from FreeBSDCon I'm have a little more time for this... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Oct 18 10:36:17 1999 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 8F39314F71 for ; Mon, 18 Oct 1999 10:35:40 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grits.cs.duke.edu (grits.cs.duke.edu [152.3.145.36]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id NAA28211; Mon, 18 Oct 1999 13:35:33 -0400 (EDT) Received: (from gallatin@localhost) by grits.cs.duke.edu (8.9.3/8.9.1) id NAA62397; Mon, 18 Oct 1999 13:35:33 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 18 Oct 1999 13:35:32 -0400 (EDT) To: Aernoudt Bottemanne Cc: alpha@freebsd.org Subject: Re: cdrom and zip (both ide) problem In-Reply-To: <380B60A3.F742EBBF@capitolonline.nl> References: <14346.31193.248797.237477@grits.cs.duke.edu> <14347.6330.820928.627692@grits.cs.duke.edu> <380B50F8.4335FDB5@capitolonline.nl> <14347.17444.883642.500165@grits.cs.duke.edu> <380B60A3.F742EBBF@capitolonline.nl> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14347.23040.117724.254694@grits.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Aernoudt Bottemanne writes: > Hi Andrew, > > So it should work in 3.x current or 4.0 current ? It should work in 4.x, but NOT in 3.x. > Unfortunately every time after I install FreeBSD > it does not boot at all..... The error message = > > "Kernel stack not valid" Version of FreeBSD? Hardware description (show conf at SRM >> promp) ? Firmware revision? ------------------------------------------------------------------------------ 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 Oct 18 10:39:16 1999 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 2B74414E40; Mon, 18 Oct 1999 10:39:06 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grits.cs.duke.edu (grits.cs.duke.edu [152.3.145.36]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id NAA28320; Mon, 18 Oct 1999 13:38:58 -0400 (EDT) Received: (from gallatin@localhost) by grits.cs.duke.edu (8.9.3/8.9.1) id NAA62568; Mon, 18 Oct 1999 13:38:58 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Mon, 18 Oct 1999 13:38:57 -0400 (EDT) To: sos@freebsd.dk Cc: mjacob@feral.com, sos@freebsd.org, alpha@freebsd.org Subject: Re: workaround for ata driver woes on alpha In-Reply-To: <199910181714.TAA00441@tuden.freebsd.dk> References: <199910181714.TAA00441@tuden.freebsd.dk> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14347.23151.744866.110836@grits.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org S=F8ren Schmidt writes: >=20 > Well, the problem is that I didn't use hz to get the right timeout (= there > the patch is correct) I missed that one sorry. > There could be a window problem, but it is highly unlikely that an A= TA > disk is going to respond with an interrupt after the timeout happend= , > but its not impossible.=20 May I commit the hz fix? <...> > > Soren- this is your stuff isn't it- what have we misunderstood? >=20 > This all needs more thought, I've just not had the time yet to do > more about it. Hopefully when I return from FreeBSDCon I'm have a > little more time for this... We (a grad student here & I ) talked about this at lunch. We think we=20= might have a real fix. I'll pass it along after we test it. Drew -----------------------------------------------------------------------= ------- Andrew Gallatin, Sr Systems Programmer=09http://www.cs.duke.edu/~gallat= in Duke University=09=09=09=09Email: gallatin@cs.duke.edu Department of Computer Science=09=09Phone: (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 Oct 18 10:41:35 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7335E14F80; Mon, 18 Oct 1999 10:41:30 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id TAA99649; Mon, 18 Oct 1999 19:41:15 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199910181741.TAA99649@freebsd.dk> Subject: Re: workaround for ata driver woes on alpha In-Reply-To: <14347.23151.744866.110836@grits.cs.duke.edu> from Andrew Gallatin at "Oct 18, 1999 01:38:57 pm" To: gallatin@cs.duke.edu (Andrew Gallatin) Date: Mon, 18 Oct 1999 19:41:14 +0200 (CEST) Cc: mjacob@feral.com, sos@freebsd.org, alpha@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Andrew Gallatin wrote: > > Søren Schmidt writes: > > > > Well, the problem is that I didn't use hz to get the right timeout (there > > the patch is correct) I missed that one sorry. > > There could be a window problem, but it is highly unlikely that an ATA > > disk is going to respond with an interrupt after the timeout happend, > > but its not impossible. > > May I commit the hz fix? > Sure. > > > Soren- this is your stuff isn't it- what have we misunderstood? > > > > This all needs more thought, I've just not had the time yet to do > > more about it. Hopefully when I return from FreeBSDCon I'm have a > > little more time for this... > > We (a grad student here & I ) talked about this at lunch. We think we > might have a real fix. I'll pass it along after we test it. OK, I'll take a look at it, but no promises :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Oct 18 10:58:24 1999 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 3401815130; Mon, 18 Oct 1999 10:58:07 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grits.cs.duke.edu (grits.cs.duke.edu [152.3.145.36]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id NAA29026; Mon, 18 Oct 1999 13:58:03 -0400 (EDT) Received: (from gallatin@localhost) by grits.cs.duke.edu (8.9.3/8.9.1) id NAA64230; Mon, 18 Oct 1999 13:58:03 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Mon, 18 Oct 1999 13:58:03 -0400 (EDT) To: Soren Schmidt Cc: mjacob@feral.com, sos@FreeBSD.ORG, alpha@FreeBSD.ORG Subject: Re: workaround for ata driver woes on alpha In-Reply-To: <199910181741.TAA99649@freebsd.dk> References: <14347.23151.744866.110836@grits.cs.duke.edu> <199910181741.TAA99649@freebsd.dk> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14347.24351.390250.179176@grits.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Soren Schmidt writes: > It seems Andrew Gallatin wrote: > >=20 > > S=F8ren Schmidt writes: > > >=20 > > > Well, the problem is that I didn't use hz to get the right time= out (there > > > the patch is correct) I missed that one sorry. > > > There could be a window problem, but it is highly unlikely that= an ATA > > > disk is going to respond with an interrupt after the timeout ha= ppend, > > > but its not impossible.=20 > >=20 > > May I commit the hz fix? > >=20 >=20 > Sure. Ok, done. Thanks. > > > > Soren- this is your stuff isn't it- what have we misunderstoo= d? > > >=20 > > > This all needs more thought, I've just not had the time yet to = do > > > more about it. Hopefully when I return from FreeBSDCon I'm have= a > > > little more time for this... > >=20 > > We (a grad student here & I ) talked about this at lunch. We thin= k we=20 > > might have a real fix. I'll pass it along after we test it. >=20 > OK, I'll take a look at it, but no promises :) This is the same grad student (darrell Anderson) who gave you ad_dump(). -;) BTW -- I just talked to a collegue here who's getting screwed by ad_timeout() with a very slow disk on a pc. It sounds like it could be the same problem. Drew -----------------------------------------------------------------------= ------- Andrew Gallatin, Sr Systems Programmer=09http://www.cs.duke.edu/~gallat= in Duke University=09=09=09=09Email: gallatin@cs.duke.edu Department of Computer Science=09=09Phone: (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 Oct 18 10:59:25 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9D90114F94; Mon, 18 Oct 1999 10:59:22 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id KAA23314; Mon, 18 Oct 1999 10:59:11 -0700 Date: Mon, 18 Oct 1999 10:59:12 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: sos@freebsd.dk Cc: Andrew Gallatin , sos@FreeBSD.ORG, alpha@FreeBSD.ORG Subject: Re: workaround for ata driver woes on alpha In-Reply-To: <199910181714.TAA00441@tuden.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 18 Oct 1999, S=F8ren Schmidt wrote: > It seems Matthew Jacob wrote: > > No, lengthening the timeout, while possibly correct for trying to achie= ve > > the same length of timeout on alpha as in i386, will *never* solve wind= ow > > problems- it just makes them more infrequent which is, in fact, far mor= e > > dangerous to an OS than the outright panic (why? Think about it- if you > > make a problem just *rare* instead of really going away, you curse the > > platform it occurs on with an aura of unreliabilty so that people are j= ust > > too uneasy to depend on it...)..... >=20 > Well, the problem is that I didn't use hz to get the right timeout (there > the patch is correct) I missed that one sorry. > There could be a window problem, but it is highly unlikely that an ATA > disk is going to respond with an interrupt after the timeout happend, > but its not impossible.=20 >=20 A window is a window. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Oct 18 13:25:58 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 3DE9914BD8 for ; Mon, 18 Oct 1999 13:25:44 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA14240 for freebsd-alpha@freebsd.org; Mon, 18 Oct 1999 22:20:09 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA02837 for freebsd-alpha@freebsd.org; Mon, 18 Oct 1999 22:16:55 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199910182016.WAA02837@yedi.iaf.nl> Subject: Makefiles in alpha boot source To: freebsd-alpha@freebsd.org (FreeBSD-alpha mailing list) Date: Mon, 18 Oct 1999 22:15:40 +0200 (CEST) X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems I'm doing something very wrong, but I fail to see what. In my attempts to hack netbooting I need to build netboot from the sources (surprise). Netboot is not built by default: # $FreeBSD: src/sys/boot/alpha/Makefile,v 1.5 1999/09/09 01:28:26 mjacob Exp $ SUBDIR= libalpha SUBDIR+= boot1 loader cdboot .include The problem is that a make in the netboot subdirectory produces .o files in that directory, whereas (e.g.) cdboot puts it's .o files in /usr/obj The subsequent 'ld' has problems linking things in because it looks in the wrong place (see below). From looking at the respective makefiles I fail to understand why this happens. It's probably a .include or so hiding deep below. But where?? Appreciate any help here, Wilko ============ In netboot: alpine#make ld -o netboot.sym -M -e start -N -Ttext 0x20000000 start.o setdef0.o main.o conf.o dev_net.o bcache.o boot.o commands.o console.o devopen.o interp.o interp_backslash.o interp_parse.o load_aout.o load_elf.o ls.o misc.o module.o panic.o setdef1.o vers.o -lstand /usr/src/sys/boot/alpha/netboot/../libalpha/libalpha.a -lstand >/usr/src/sys/boot/alpha/netboot/netboot.list /usr/libexec/elf/ld: cannot open /usr/src/sys/boot/alpha/netboot/../libalpha/libalpha.a: No such file or directory *** Error code 1 Stop in /usr/src/sys/boot/alpha/netboot. alpine#cat Makefile # $NetBSD: Makefile,v 1.12 1998/02/19 14:18:36 drochner Exp $ BASE= netboot PROG= ${BASE} NOMAN= NEWVERSWHAT= "SRM net boot" alpha LOAD_ADDRESS= ${PRIMARY_LOAD_ADDRESS} CFLAGS+= -DLOADER_NET_SUPPORT .include <${.CURDIR}/../common/Makefile.common> alpine# ------------------- In cdboot: ld -o cdboot.sym -M -e start -N -Ttext 0x20000000 start.o setdef0.o main.o conf.o bcache.o boot.o commands.o console.o devopen.o interp.o interp_backslash.o interp_parse.o load_aout.o load_elf.o ls.o misc.o module.o panic.o setdef1.o vers.o -lstand /usr/obj/usr/src/sys/boot/alpha/cdboot/../libalpha/libalpha.a -lstand >/usr/obj/usr/src/sys/boot/alpha/cdboot/cdboot.list objcopy -O binary cdboot.sym cdboot alpine# # $FreeBSD: src/sys/boot/alpha/cdboot/Makefile,v 1.3 1999/09/03 19:42:14 m smith Exp $ BASE= cdboot PROG= ${BASE} NOMAN= NEWVERSWHAT= "SRM CD9660 boot" alpha LOAD_ADDRESS= ${PRIMARY_LOAD_ADDRESS} CFLAGS+= -DLOADER_CDROM_SUPPORT .include <${.CURDIR}/../common/Makefile.common> -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Oct 18 13:50:54 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id 94C1F15130 for ; Mon, 18 Oct 1999 13:50:45 -0700 (PDT) (envelope-from bottemanne@capitolonline.nl) Received: from capitolonline.nl ([195.121.170.112]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA31D for ; Mon, 18 Oct 1999 22:50:40 +0200 Message-ID: <380B968A.A8DEE538@capitolonline.nl> Date: Mon, 18 Oct 1999 22:52:11 +0100 From: Aernoudt Bottemanne X-Mailer: Mozilla 4.04 [en] (OS/2; I) MIME-Version: 1.0 To: "alpha@freebsd.org" Subject: boot problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, My PWS 433a does not boot FreeBSD. After/during installation no error messages are displayed (on terminal 2). However on (re)boot it has a kernel stack problem. (error no 2, PC = 0) So I guess, the installation does not register the partitions... : - ( Any tips ? Cheers, Aernoudt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Oct 18 13:52:39 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id 8695115130 for ; Mon, 18 Oct 1999 13:52:27 -0700 (PDT) (envelope-from bottemanne@capitolonline.nl) Received: from capitolonline.nl ([195.121.170.112]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA541 for ; Mon, 18 Oct 1999 22:52:26 +0200 Message-ID: <380B96F4.7DC23CE0@capitolonline.nl> Date: Mon, 18 Oct 1999 22:53:56 +0100 From: Aernoudt Bottemanne X-Mailer: Mozilla 4.04 [en] (OS/2; I) MIME-Version: 1.0 To: "freebsd-alpha@freebsd.org" Subject: boot problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, My PWS 433a does not boot FreeBSD. After/during installation no error messages are displayed (on terminal 2). However on (re)boot it has a kernel stack problem. (error no 2, PC=0) So I guess, the installation does not register the partitions... : - ( Any tips ? Cheers, Aernoudt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Oct 18 14: 2:38 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id 24B8214EFE for ; Mon, 18 Oct 1999 14:02:31 -0700 (PDT) (envelope-from bottemanne@capitolonline.nl) Received: from capitolonline.nl ([195.121.170.112]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA72C3; Mon, 18 Oct 1999 23:02:27 +0200 Message-ID: <380B9943.946D5365@capitolonline.nl> Date: Mon, 18 Oct 1999 23:03:47 +0100 From: Aernoudt Bottemanne X-Mailer: Mozilla 4.04 [en] (OS/2; I) MIME-Version: 1.0 To: Andrew Gallatin Cc: "freebsd-alpha@freebsd.org" Subject: Re: cdrom and zip (both ide) problem References: <14346.31193.248797.237477@grits.cs.duke.edu> <14347.6330.820928.627692@grits.cs.duke.edu> <380B50F8.4335FDB5@capitolonline.nl> <14347.17444.883642.500165@grits.cs.duke.edu> <380B60A3.F742EBBF@capitolonline.nl> <14347.23040.117724.254694@grits.cs.duke.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org PWS 433a, Digital SRM V 7.0-10 ARC 5.68 srom 5.90 128MB, 21142 network controller, isp 1040 scsi controller 2 * 4.5 GB scsi, plex scsi cdrom, iomega scsi zip, matrox millennium II 4MB pci, DEC chip 21164 Andrew Gallatin wrote: > Aernoudt Bottemanne writes: > > Hi Andrew, > > > > So it should work in 3.x current or 4.0 current ? > > It should work in 4.x, but NOT in 3.x. > > > Unfortunately every time after I install FreeBSD > > it does not boot at all..... The error message = > > > > "Kernel stack not valid" > > Version of FreeBSD? Hardware description (show conf at SRM >> promp) ? > Firmware revision? > > ------------------------------------------------------------------------------ > 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 Mon Oct 18 15:13:17 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 27BE4151B0 for ; Mon, 18 Oct 1999 15:11:13 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA19562 for freebsd-alpha@freebsd.org; Mon, 18 Oct 1999 23:57:20 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA44046 for freebsd-alpha@freebsd.org; Tue, 19 Oct 1999 00:01:01 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199910182201.AAA44046@yedi.iaf.nl> Subject: Xfree / Mach64 on Alpha? To: freebsd-alpha@freebsd.org (FreeBSD-alpha mailing list) Date: Tue, 19 Oct 1999 00:01:01 +0200 (CEST) X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wanting to demo a FreeBSD/alpha machine at the upcoming NLUUG conference I just threw a ATI Mach64 PCI (WinTurbo) card into my Alpine box. The machine is at -current. It seems the Xfree contained on the 3.3 cdrom is not completely happy: (**) FontPath set to "/usr/X11R6/lib/X11/fonts/local/,/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/" (--) Mach64: PCI: Mach64 CX rev 1, Aperture @ 0x81000000, Sparse I/O @ 0x02ec *** None of the configured devices were detected.*** As this is my first Xfree attempt on the Alpha I wonder what the aperture etc is supposed to indicate. Looks like it is having troubles probing the card. TNX, -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Oct 18 15:52:30 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id E169914CA0 for ; Mon, 18 Oct 1999 15:52:24 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40337>; Tue, 19 Oct 1999 08:47:57 +1000 Content-return: prohibited Date: Tue, 19 Oct 1999 08:52:10 +1000 From: Peter Jeremy Subject: Netbooting a Multia with FreeBSD To: freebsd-alpha@FreeBSD.ORG, multia-users@explode.unsw.edu.au Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct19.084757est.40337@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [Please note lists in any replies] I am trying to netboot FreeBSD 3.2-RELEASE (that being the latest binaries I have to hand) onto a Multia with SRM 3.8.3 (the latest). I got around the `boot device name does not contain ethernet address' error by patching the MAC address into the netboot binary and it now happily loads and executes netboot. My problem is that netboot seems unable to accept the DHCP or RARP responses returned to its requests. It just cycles between DHCP and RARP requests until it times out. I've tried the FreeBSD-current bootps (which wouldn't respond because the Multia is sending DHCPDISCOVER requests), WIDE dhcp-1.4.0p6 (which doesn't seem to respond, though that may be a configuration problem) and ISC dhcp-1.0pl2. With the ISC dhcp in debug mode, I get the following: BOOTREQUEST from 08:00:2b:e4:41:77 via ed0 BOOTREPLY for 139.188.20.243 to pc0802 (08:00:2b:e4:41:77) via ed0 DHCPDISCOVER from 08:00:2b:e4:41:77 via ed0 DHCPOFFER on 139.188.20.243 to 08:00:2b:e4:41:77 via ed0 DHCPDISCOVER from 08:00:2b:e4:41:77 via ed0 DHCPOFFER on 139.188.20.243 to 08:00:2b:e4:41:77 via ed0 DHCPDISCOVER from 08:00:2b:e4:41:77 via ed0 DHCPOFFER on 139.188.20.243 to 08:00:2b:e4:41:77 via ed0 DHCPDISCOVER from 08:00:2b:e4:41:77 via ed0 DHCPOFFER on 139.188.20.243 to 08:00:2b:e4:41:77 via ed0 Looking at tcpdump output, I see: 08:16:05.169896 pc0802 Broadcast ip 590: 0.0.0.0.bootpc > 255.255.255.255.bootps: vend-rfc1048 T53:1 08:16:05.171978 0:0:c0:57:99:47 pc0802 ip 354: gsmx07.alcatel.com.au.bootps > 255.255.255.255.bootpc: Y:pc0802 S:gsmx07.alcatel.com.au file "/tftpboot/netboot vend-rfc1048 T53:2 T54:4145331339 T51:3232235520 T58:1616117760 T59:2828206080 SM:255.255.240.0 DG:aalr01.alcatel.com.au NS:pc1762,mfg1.cim.alcatel.com.au DN:"alcatel.com.au" T28:4280269963 [tos 0x10] 08:16:07.174232 pc0802 Broadcast ip 590: 0.0.0.0.bootpc > 255.255.255.255.bootps: secs:2 vend-rfc1048 T53:1 08:16:07.176040 0:0:c0:57:99:47 pc0802 ip 354: gsmx07.alcatel.com.au.bootps > 255.255.255.255.bootpc: secs:2 Y:pc0802 S:gsmx07.alcatel.com.au file "/tftpboot/netboot vend-rfc1048 T53:2 T54:4145331339 T51:3232235520 T58:1616117760 T59:2828206080 SM:255.255.240.0 DG:aalr01.alcatel.com.au NS:pc1762,mfg1.cim.alcatel.com.au DN:"alcatel.com.au" T28:4280269963 [tos 0x10] 08:16:11.182971 pc0802 Broadcast ip 590: 0.0.0.0.bootpc > 255.255.255.255.bootps: secs:6 vend-rfc1048 T53:1 08:16:11.184891 0:0:c0:57:99:47 pc0802 ip 354: gsmx07.alcatel.com.au.bootps > 255.255.255.255.bootpc: secs:6 Y:pc0802 S:gsmx07.alcatel.com.au file "/tftpboot/netboot vend-rfc1048 T53:2 T54:4145331339 T51:3232235520 T58:1616117760 T59:2828206080 SM:255.255.240.0 DG:aalr01.alcatel.com.au NS:pc1762,mfg1.cim.alcatel.com.au DN:"alcatel.com.au" T28:4280269963 [tos 0x10] 08:16:19.199791 pc0802 Broadcast ip 590: 0.0.0.0.bootpc > 255.255.255.255.bootps: secs:14 vend-rfc1048 T53:1 08:16:19.201615 0:0:c0:57:99:47 pc0802 ip 354: gsmx07.alcatel.com.au.bootps > 255.255.255.255.bootpc: secs:14 Y:pc0802 S:gsmx07.alcatel.com.au file "/tftpboot/netboot vend-rfc1048 T53:2 T54:4145331339 T51:3232235520 T58:1616117760 T59:2828206080 SM:255.255.240.0 DG:aalr01.alcatel.com.au NS:pc1762,mfg1.cim.alcatel.com.au DN:"alcatel.com.au" T28:4280269963 [tos 0x10] 08:16:35.277774 pc0802 Broadcast rarp 60: rarp who-is pc0802 tell pc0802 08:16:35.278792 0:0:c0:57:99:47 pc0802 rarp 42: rarp reply pc0802 at pc0802 08:16:36.320410 pc0802 Broadcast rarp 60: rarp who-is pc0802 tell pc0802 08:16:36.321164 0:0:c0:57:99:47 pc0802 rarp 42: rarp reply pc0802 at pc0802 08:16:39.584397 pc0802 Broadcast rarp 60: rarp who-is pc0802 tell pc0802 08:16:39.585399 0:0:c0:57:99:47 pc0802 rarp 42: rarp reply pc0802 at pc0802 08:16:47.600612 pc0802 Broadcast rarp 60: rarp who-is pc0802 tell pc0802 08:16:47.601577 0:0:c0:57:99:47 pc0802 rarp 42: rarp reply pc0802 at pc0802 All of which looks correct. Does anyone have any suggestions? Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Mon Oct 18 18:22:37 1999 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 E122515697 for ; Mon, 18 Oct 1999 18:22:33 -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.1/8.9.1) with ESMTP id VAA10475; Mon, 18 Oct 1999 21:21:26 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id VAA01075; Mon, 18 Oct 1999 21:20:55 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 18 Oct 1999 21:20:55 -0400 (EDT) To: Aernoudt Bottemanne Cc: freebsd-alpha@freebsd.org Subject: Re: boot problem In-Reply-To: <380B96F4.7DC23CE0@capitolonline.nl> References: <380B96F4.7DC23CE0@capitolonline.nl> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14347.50800.846953.454319@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Aernoudt Bottemanne writes: > Hi, > > My PWS 433a does not boot FreeBSD. After/during installation no error > messages are displayed (on terminal 2). > However on (re)boot it has a kernel stack problem. (error no 2, PC=0) > So I guess, the installation does not register the partitions... : - ( > Again, please provide a little more context. a) what version of FreeBSD are you booting? Where did you get it? b) what hardware is in your computer. Please at least take the time to copy "show dev". show conf would be nice to see too. c) what device are you booting from? What did you type to boot the computer? d) what does the computer say after you attempt to boot it? Please include more than just the last line. ------------------------------------------------------------------------------ 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 Oct 18 18:49: 6 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from dingo.cdrom.com (picasso.transbay.net [209.133.53.6]) by hub.freebsd.org (Postfix) with ESMTP id 9EA7115776 for ; Mon, 18 Oct 1999 18:49:05 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id SAA00461; Mon, 18 Oct 1999 18:41:04 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199910190141.SAA00461@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Wilko Bulte Cc: freebsd-alpha@freebsd.org (FreeBSD-alpha mailing list) Subject: Re: Makefiles in alpha boot source In-reply-to: Your message of "Mon, 18 Oct 1999 22:15:40 +0200." <199910182016.WAA02837@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Oct 1999 18:41:04 -0700 From: Mike Smith Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > The problem is that a make in the netboot subdirectory produces .o files > in that directory, whereas (e.g.) cdboot puts it's .o files in /usr/obj > The subsequent 'ld' has problems linking things in because it looks in > the wrong place (see below). Either 'make obj' or 'make cleandir' in /sys/boot. Take your pick. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 19 0:15:25 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id 53EF5160C2; Tue, 19 Oct 1999 00:15:18 -0700 (PDT) (envelope-from bottemanne@capitolonline.nl) Received: from capitolonline.nl ([195.121.168.73]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA2E2F; Tue, 19 Oct 1999 09:15:17 +0200 Message-ID: <380C28EE.235CE418@capitolonline.nl> Date: Tue, 19 Oct 1999 09:16:47 +0100 From: Aernoudt Bottemanne X-Mailer: Mozilla 4.04 [en] (OS/2; I) MIME-Version: 1.0 To: Andrew Gallatin , a.bottemanne@nl.ibm.com Cc: freebsd-alpha@freebsd.org, "alpha@freebsd.org" Subject: Re: boot problem References: <380B96F4.7DC23CE0@capitolonline.nl> <14347.50800.846953.454319@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Andrew, There seems to go a lot wrong... Yesterday I sent the show conf.... But I have not seem my message appearing on the mailing list too, anyway I hope you receive this one ! > Again, please provide a little more context. > > a) what version of FreeBSD are you booting? Where did you get it? > Version 3.3 release, from CD-rom > b) what hardware is in your computer. Please at least take the time > to copy "show dev". show conf would be nice to see too. > Digital PWS 433a(u) DEC chip 21164A-2, 433 Mhz Matrox Millennium II 4MB, 128MB ram, Qlogic 1040B scsi controller, plextor scsi cdrom, iomega scsi zip drive, 2 * 4,5 GB scsi disk (UW) dkc0 Quantum XP34550 dkc100 scsi disk: RZ1CC-BA dkc400 iomega zip 100 dkc500 plextor scsi CD PX-40TS dva0 floppy ewa0 (network card, DECchip 21142 Network Controller) pkc0 scsi bus id 7 pqa0 pci ide pqb0 pci ide SRM V7.0-10 ARC 5.68 Pal VMS V1.20-14, OSF pal V1.22-17 SROM v5.90 > c) what device are you booting from? What did you type to boot the > computer? > During installation dva0, after that dkc0 (the first scsi disk) > d) what does the computer say after you attempt to boot it? Please > include more than just the last line. > halted cpu 0halt code=2 Kernel stack not valid halt PC=0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 19 0:15:34 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id 53EF5160C2; Tue, 19 Oct 1999 00:15:18 -0700 (PDT) (envelope-from bottemanne@capitolonline.nl) Received: from capitolonline.nl ([195.121.168.73]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA2E2F; Tue, 19 Oct 1999 09:15:17 +0200 Message-ID: <380C28EE.235CE418@capitolonline.nl> Date: Tue, 19 Oct 1999 09:16:47 +0100 From: Aernoudt Bottemanne X-Mailer: Mozilla 4.04 [en] (OS/2; I) MIME-Version: 1.0 To: Andrew Gallatin , a.bottemanne@nl.ibm.com Cc: freebsd-alpha@freebsd.org, "alpha@freebsd.org" Subject: Re: boot problem References: <380B96F4.7DC23CE0@capitolonline.nl> <14347.50800.846953.454319@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Andrew, There seems to go a lot wrong... Yesterday I sent the show conf.... But I have not seem my message appearing on the mailing list too, anyway I hope you receive this one ! > Again, please provide a little more context. > > a) what version of FreeBSD are you booting? Where did you get it? > Version 3.3 release, from CD-rom > b) what hardware is in your computer. Please at least take the time > to copy "show dev". show conf would be nice to see too. > Digital PWS 433a(u) DEC chip 21164A-2, 433 Mhz Matrox Millennium II 4MB, 128MB ram, Qlogic 1040B scsi controller, plextor scsi cdrom, iomega scsi zip drive, 2 * 4,5 GB scsi disk (UW) dkc0 Quantum XP34550 dkc100 scsi disk: RZ1CC-BA dkc400 iomega zip 100 dkc500 plextor scsi CD PX-40TS dva0 floppy ewa0 (network card, DECchip 21142 Network Controller) pkc0 scsi bus id 7 pqa0 pci ide pqb0 pci ide SRM V7.0-10 ARC 5.68 Pal VMS V1.20-14, OSF pal V1.22-17 SROM v5.90 > c) what device are you booting from? What did you type to boot the > computer? > During installation dva0, after that dkc0 (the first scsi disk) > d) what does the computer say after you attempt to boot it? Please > include more than just the last line. > halted cpu 0halt code=2 Kernel stack not valid halt PC=0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 19 0:32:46 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from post.bgnett.no (post.bgnett.no [194.54.96.133]) by hub.freebsd.org (Postfix) with ESMTP id 096481616D; Tue, 19 Oct 1999 00:32:40 -0700 (PDT) (envelope-from erik@habatech.no) Received: from bsdbox.habatech.no ([62.92.133.3]) by post.bgnett.no (8.8.8/8.8.8) with ESMTP id JAA21551; Tue, 19 Oct 1999 09:32:36 +0200 (CEST) (envelope-from erik@habatech.no) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199910181741.TAA99649@freebsd.dk> Date: Tue, 19 Oct 1999 09:32:19 +0200 (CEST) From: "Erik H. Bakke" To: Soren Schmidt Subject: Re: workaround for ata driver woes on alpha Cc: alpha@FreeBSD.ORG, sos@FreeBSD.ORG, mjacob@feral.com, (Andrew Gallatin) Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 18-Oct-99 Soren Schmidt wrote: > It seems Andrew Gallatin wrote: >> >> We (a grad student here & I ) talked about this at lunch. We think we >> might have a real fix. I'll pass it along after we test it. > > OK, I'll take a look at it, but no promises :) > I can give it a shot as well, as I have some 2 weeks of instability to compare against. ===========================+================+=============================== Erik H. Bakke | | To be or not to be... Senior Consultant/Developer|erik@habatech.no| Is simply a question of Habatech AS | | binary logic ===========================+================+============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 19 4:43:23 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id C811A167F1 for ; Tue, 19 Oct 1999 04:43:20 -0700 (PDT) (envelope-from bottemanne@capitolonline.nl) Received: from capitolonline.nl ([195.121.168.225]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA17F2 for ; Tue, 19 Oct 1999 13:43:19 +0200 Message-ID: <380C67C1.757DEB72@capitolonline.nl> Date: Tue, 19 Oct 1999 13:44:49 +0100 From: Aernoudt Bottemanne X-Mailer: Mozilla 4.04 [en] (OS/2; I) MIME-Version: 1.0 To: "freebsd-alpha@freebsd.org" Subject: netscape on Alpha ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Probably a stupid question, but why isn't there a netscape in the packages ? In linux (on alpha) there is Netscape 4.7.... (also for Gimp ?!) Cheers, Aernoudt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 19 6:23: 4 1999 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 25EC916F84 for ; Tue, 19 Oct 1999 06:22: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.1/8.9.1) with ESMTP id JAA21711; Tue, 19 Oct 1999 09:22:46 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id JAA01988; Tue, 19 Oct 1999 09:22:16 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 19 Oct 1999 09:22:16 -0400 (EDT) To: Aernoudt Bottemanne Cc: a.bottemanne@nl.ibm.com, "alpha@freebsd.org" Subject: Re: boot problem In-Reply-To: <380C28EE.235CE418@capitolonline.nl> References: <380B96F4.7DC23CE0@capitolonline.nl> <14347.50800.846953.454319@grasshopper.cs.duke.edu> <380C28EE.235CE418@capitolonline.nl> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14348.28566.539891.950288@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Aernoudt Bottemanne writes: > > d) what does the computer say after you attempt to boot it? Please > > include more than just the last line. > > > > halted cpu 0halt code=2 > Kernel stack not valid halt > PC=0 > What do you see before this? Anything like: CPU 0 booting resetting all I/O buses (boot dka0.0.0.6.1 -flags a) block 0 of dka0.0.0.6.1 is a valid boot block reading 14 blocks from dka0.0.0.6.1 bootstrap code read in base = 1ac000, image_start = 0, image_bytes = 1c00 initializing HWRPB at 2000 initializing page table at 27ff0000 initializing machine state setting affinity to the primary CPU jumping to bootstrap code Console: SRM firmware console VMS PAL rev: 0x1001100010130 OSF PAL rev: 0x100100002012c Switch to OSF PAL code succeeded. FreeBSD/alpha SRM disk boot, Revision 0.1 (root@boil.cs.duke.edu, Mon Aug 16 18:17:10 EDT 1999) Memory: 655360 k > autoboot 3 Hit [Enter] to boot immediately, or any other key for command prompt. At which point in the above process does the machine halt? 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 Oct 19 6:32:16 1999 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 6511F16FCA for ; Tue, 19 Oct 1999 06:32:14 -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.1/8.9.1) with ESMTP id JAA21873; Tue, 19 Oct 1999 09:32:13 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id JAA02013; Tue, 19 Oct 1999 09:31:43 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 19 Oct 1999 09:31:42 -0400 (EDT) To: Aernoudt Bottemanne Cc: "freebsd-alpha@freebsd.org" Subject: Re: netscape on Alpha ? In-Reply-To: <380C67C1.757DEB72@capitolonline.nl> References: <380C67C1.757DEB72@capitolonline.nl> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14348.29026.782416.493520@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Aernoudt Bottemanne writes: > Probably a stupid question, but why isn't there a netscape in the > packages ? > In linux (on alpha) there is Netscape 4.7.... > Where does one get a native Netscape 4.7 for linux? If there actually is one, it would be very exciting. If you're talking about the OSF (aka Digital UNIX, aka Tru64 UNIX) version of Netscape we can also run that in compat mode using http://www.freebsd.org/~gallatin/osf1.tar.gz on -current (warning -- this still needs to be updated past the signal changes, I've done this in my local tree but haven't tested it very much). In both systems (BSD & Linux) you need to have Digital shared libs. Unless your system is licensed for OSF1, it is illegal to use these libs. ------------------------------------------------------------------------------ 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 Oct 19 7:50:32 1999 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 1516714A13 for ; Tue, 19 Oct 1999 07:50:23 -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.1/8.9.1) with ESMTP id KAA23677; Tue, 19 Oct 1999 10:50:22 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id KAA02172; Tue, 19 Oct 1999 10:49:52 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 19 Oct 1999 10:49:52 -0400 (EDT) To: a.bottemanne@nl.ibm.com Cc: freebsd-alpha@freebsd.org Subject: Re: boot problem In-Reply-To: <8025680F.00504FF6.00@d06mta01.portsmouth.uk.ibm.com> References: <8025680F.00504FF6.00@d06mta01.portsmouth.uk.ibm.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14348.33521.475516.220514@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org a.bottemanne@nl.ibm.com writes: > > > Hi Andrew, > > > This is what I see: (text chaged from your exampke, to the output on my screen) > > (boot dkc0.0.0.1010.0 -flags 0) > block 0 of dka0.0.0.1010.0 is a valid boot block > reading 15 blocks from dkc0.0.0.1010.0 > bootstrap code read in > base = 1f0000, image_start = 0, image_bytes = 1e00 > initializing HWRPB at 2000 > initializing page table at 1e2000 > initializing machine state > setting affinity to the primary CPU > jumping to bootstrap code > > halted CPU 0 > > halt code = 2 > kernel stack not valid halt > PC = 0 > > > Thats it.... then the world stops ! > > Aernoudt > Thank you. Now we can start making helpful suggestions. Can you please boot into the installation, enter fixit mode, and verify that /boot/loader is present on the disk. You should be able to mount /dev/da0a to verify that. BTW, I've never even *seen* a 3.3 CD-ROM, much less used one. Does anybody out there know if sysinstall is really broken enough to forget to put the loader on the disk? 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 Oct 19 8:28: 8 1999 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 90BE31743E for ; Tue, 19 Oct 1999 08:28:06 -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.1/8.9.1) with ESMTP id LAA24814; Tue, 19 Oct 1999 11:28:05 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id LAA02274; Tue, 19 Oct 1999 11:27:35 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 19 Oct 1999 11:27:35 -0400 (EDT) To: Aernoudt Bottemanne Cc: alpha@freebsd.org Subject: Re: boot problem In-Reply-To: <380C9ACA.70E4B3F2@capitolonline.nl> References: <8025680F.00504FF6.00@d06mta01.portsmouth.uk.ibm.com> <14348.33521.475516.220514@grasshopper.cs.duke.edu> <380C9ACA.70E4B3F2@capitolonline.nl> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14348.36045.923918.956413@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Aernoudt Bottemanne writes: > Andrew, > > No: ls, mount, cat etc etc etc. How do I check if loader is there without this ? No idea. Again, I have never, ever even seen a 3.3-release cd. Maybe somebody else who has can be of more help to you. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 19 8:28:48 1999 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 7D14017445 for ; Tue, 19 Oct 1999 08:28:19 -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.1/8.9.1) with ESMTP id LAA24823; Tue, 19 Oct 1999 11:28:18 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id LAA02274; Tue, 19 Oct 1999 11:27:35 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 19 Oct 1999 11:27:35 -0400 (EDT) To: Aernoudt Bottemanne Cc: alpha@freebsd.org Subject: Re: boot problem In-Reply-To: <380C9ACA.70E4B3F2@capitolonline.nl> References: <8025680F.00504FF6.00@d06mta01.portsmouth.uk.ibm.com> <14348.33521.475516.220514@grasshopper.cs.duke.edu> <380C9ACA.70E4B3F2@capitolonline.nl> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14348.36045.923918.956413@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Aernoudt Bottemanne writes: > Andrew, > > No: ls, mount, cat etc etc etc. How do I check if loader is there without this ? No idea. Again, I have never, ever even seen a 3.3-release cd. Maybe somebody else who has can be of more help to you. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 19 9:58:33 1999 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 76FB2176E6 for ; Tue, 19 Oct 1999 09:58: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.1/8.9.1) with ESMTP id MAA26852; Tue, 19 Oct 1999 12:58:29 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id MAA02471; Tue, 19 Oct 1999 12:57:59 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 19 Oct 1999 12:57:59 -0400 (EDT) To: a.bottemanne@nl.ibm.com Cc: freebsd-alpha@freebsd.org Subject: Re: boot problem In-Reply-To: <8025680F.005C49AA.00@d06mta01.portsmouth.uk.ibm.com> References: <8025680F.005C49AA.00@d06mta01.portsmouth.uk.ibm.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14348.41506.592472.516811@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org a.bottemanne@nl.ibm.com writes: > > > Andrew, > > Tried again (after a new installation again) and it is present (the > /boot/loader) > it is a file with a lot of smilies on the bottom) > Hope this is usefull information to get the stuff up and running.... > Please keep the mailing list in the cc line. Try also doing 'disklabel -B da0' Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 19 10: 2:48 1999 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 254CD176F5; Tue, 19 Oct 1999 10:02:45 -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.1/8.9.1) with ESMTP id NAA26984; Tue, 19 Oct 1999 13:02:45 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id NAA02481; Tue, 19 Oct 1999 13:02:14 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Tue, 19 Oct 1999 13:02:14 -0400 (EDT) To: sos@freebsd.org Cc: freebsd-alpha@freebsd.org Subject: ata busmaster i/o port on alpha X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14348.40785.536064.278837@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org S=F8ren, I'm trying to get the on-board IDE controllers in some AlphaServer DS10 machines working well w/FreeBSD-current. They use the Acer AladdinV IDE controller in combination with a FUJITSU MPD3108AT ATA-4 disk. The problem is with where the "Bios" (aka the SRM console) puts the busmaster address: <12:45pm>opal/root:~#pciconf -r 'pci0:13:0' 0x20 0x00010111 When you read the bus master address you mask off the upper 16 bits entirely and we see the address as 0x110 where as it should really be=20= 0x10110. When this happens, the disk is of course unusable. After 5 retries, I see I/O errors when I try to access the disk. If I apply the following patch, DMA works: Index: ata-all.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v retrieving revision 1.28 diff -u -r1.28 ata-all.c --- ata-all.c=091999/10/16 09:00:49=091.28 +++ ata-all.c=091999/10/19 16:51:36 @@ -262,9 +262,9 @@ =09irq1 =3D 14; }=20 else { -=09iobase_1 =3D pci_read_config(dev, 0x10, 4) & 0xfffc; -=09altiobase_1 =3D pci_read_config(dev, 0x14, 4) & 0xfffc; -=09bmaddr_1 =3D pci_read_config(dev, 0x20, 4) & 0xfffc; +=09iobase_1 =3D pci_read_config(dev, 0x10, 4) & 0xfffffffc; +=09altiobase_1 =3D pci_read_config(dev, 0x14, 4) & 0xfffffffc; +=09bmaddr_1 =3D pci_read_config(dev, 0x20, 4) & 0xfffffffc; =09irq1 =3D pci_read_config(dev, PCI_INTERRUPT_REG, 4) & 0xff; } =20 @@ -274,9 +274,9 @@ =09irq2 =3D 15; } else { -=09iobase_2 =3D pci_read_config(dev, 0x18, 4) & 0xfffc; -=09altiobase_2 =3D pci_read_config(dev, 0x1c, 4) & 0xfffc; -=09bmaddr_2 =3D (pci_read_config(dev, 0x20, 4) & 0xfffc) + ATA_BM_OFFS= ET1; +=09iobase_2 =3D pci_read_config(dev, 0x18, 4) & 0xfffffffc; +=09altiobase_2 =3D pci_read_config(dev, 0x1c, 4) & 0xfffffffc; +=09bmaddr_2 =3D (pci_read_config(dev, 0x20, 4) & 0xfffffffc) + ATA_BM_= OFFSET1; =09irq2 =3D pci_read_config(dev, PCI_INTERRUPT_REG, 4) & 0xff; } =20 @@ -285,7 +285,7 @@ =09/* is busmastering support turned on ? */ =09if ((pci_read_config(dev, PCI_COMMAND_STATUS_REG, 4) & 5) =3D=3D 5)= { =09 /* is there a valid port range to connect to ? */ -=09 if ((bmaddr_1 =3D pci_read_config(dev, 0x20, 4) & 0xfffc)) { +=09 if ((bmaddr_1 =3D pci_read_config(dev, 0x20, 4) & 0xfffffffc)) = { =09=09bmaddr_2 =3D bmaddr_1 + ATA_BM_OFFSET1; =09=09printf("ata-pci%d: Busmastering DMA supported\n", unit); =09 } And works pretty well, at that: -------Sequential Output-------- ---Sequential Input-- --= Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --= Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /= sec %CPU 1024 9235 91.9 9160 12.0 4111 6.6 6617 98.7 14360 14.5 12= 2.2 1.2 So, my question: Is are you loosing the upper 16 bits for a reason, or is it valid to look at the upper 16 bits on all platforms? Thanks, Drew -----------------------------------------------------------------------= ------- Andrew Gallatin, Sr Systems Programmer=09http://www.cs.duke.edu/~gallat= in Duke University=09=09=09=09Email: gallatin@cs.duke.edu Department of Computer Science=09=09Phone: (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 Oct 19 11:39:21 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 8AEB31777A for ; Tue, 19 Oct 1999 11:39:14 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA14741; Tue, 19 Oct 1999 20:14:38 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id TAA00732; Tue, 19 Oct 1999 19:49:49 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199910191749.TAA00732@yedi.iaf.nl> Subject: Re: Makefiles in alpha boot source In-Reply-To: <199910190141.SAA00461@dingo.cdrom.com> from Mike Smith at "Oct 18, 1999 6:41: 4 pm" To: mike@smith.net.au (Mike Smith) Date: Tue, 19 Oct 1999 19:49:49 +0200 (CEST) Cc: freebsd-alpha@freebsd.org X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Mike Smith wrote ... > > > > The problem is that a make in the netboot subdirectory produces .o files > > in that directory, whereas (e.g.) cdboot puts it's .o files in /usr/obj > > The subsequent 'ld' has problems linking things in because it looks in > > the wrong place (see below). > > Either 'make obj' or 'make cleandir' in /sys/boot. Take your pick. I am stunned.. Excellent, thank you! :-) -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 19 13:58:36 1999 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 DC83A14DCE; Tue, 19 Oct 1999 13:58:26 -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.1/8.9.1) with ESMTP id QAA02928; Tue, 19 Oct 1999 16:58:18 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id QAA02929; Tue, 19 Oct 1999 16:57:48 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 19 Oct 1999 16:57:48 -0400 (EDT) To: "Erik H. Bakke" Cc: Soren Schmidt , alpha@FreeBSD.ORG, sos@FreeBSD.ORG, mjacob@feral.com Subject: Re: workaround for ata driver woes on alpha In-Reply-To: References: <199910181741.TAA99649@freebsd.dk> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14348.55807.415236.565105@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Erik H. Bakke writes: > > On 18-Oct-99 Soren Schmidt wrote: > > It seems Andrew Gallatin wrote: > >> > >> We (a grad student here & I ) talked about this at lunch. We think we > >> might have a real fix. I'll pass it along after we test it. > > > > OK, I'll take a look at it, but no promises :) > > > I can give it a shot as well, as I have some 2 weeks of instability to compare > against. I finally got around to testing it & it seems to work. The appended patch is courtesy of Darrell Anderson (anderson@cs.duke.edu). I believe Matt's suggestion is probably the real fix. Also, we've seen this problem (albeit rarely) on PCs under extreme load as well. (450MHz PIII, 2 promise cards, 4 22GB IBM Deskstar drive as each channel's primary master, sinking data to/from a gigabit link to a number of clients) ------------------------------------------------------------------------------ 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 Index: ata-disk.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/ata-disk.c,v retrieving revision 1.32 diff -u -c -r1.32 ata-disk.c cvs diff: conflicting specifications of output style *** ata-disk.c 1999/10/18 17:55:38 1.32 --- ata-disk.c 1999/10/19 20:51:36 *************** *** 511,516 **** --- 511,527 ---- struct ad_softc *adp = request->device; int32_t dma_stat = 0; + /* + * watch for a race where ad_interrupt is called after ad_timeout + * has allready been committed to run. if that's the case, abort + * and let ad_timeout deal with reissuing the request. + */ + if (request->timeout_handle.callout && + !callout_pending(request->timeout_handle.callout)) { + printf("ad_interrupt: ad_timeout/ad_interrupt race detected. aborting.\n"); + return ATA_OP_CONTINUES; + } + /* finish DMA transfer */ if (request->flags & AR_F_DMA_USED) dma_stat = ata_dmadone(adp->controller); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 19 13:58:45 1999 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 0996A17CED; Tue, 19 Oct 1999 13:58:26 -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.1/8.9.1) with ESMTP id QAA02929; Tue, 19 Oct 1999 16:58:19 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id QAA02929; Tue, 19 Oct 1999 16:57:48 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 19 Oct 1999 16:57:48 -0400 (EDT) To: "Erik H. Bakke" Cc: Soren Schmidt , alpha@FreeBSD.ORG, sos@FreeBSD.ORG, mjacob@feral.com Subject: Re: workaround for ata driver woes on alpha In-Reply-To: References: <199910181741.TAA99649@freebsd.dk> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14348.55807.415236.565105@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Erik H. Bakke writes: > > On 18-Oct-99 Soren Schmidt wrote: > > It seems Andrew Gallatin wrote: > >> > >> We (a grad student here & I ) talked about this at lunch. We think we > >> might have a real fix. I'll pass it along after we test it. > > > > OK, I'll take a look at it, but no promises :) > > > I can give it a shot as well, as I have some 2 weeks of instability to compare > against. I finally got around to testing it & it seems to work. The appended patch is courtesy of Darrell Anderson (anderson@cs.duke.edu). I believe Matt's suggestion is probably the real fix. Also, we've seen this problem (albeit rarely) on PCs under extreme load as well. (450MHz PIII, 2 promise cards, 4 22GB IBM Deskstar drive as each channel's primary master, sinking data to/from a gigabit link to a number of clients) ------------------------------------------------------------------------------ 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 Index: ata-disk.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/ata-disk.c,v retrieving revision 1.32 diff -u -c -r1.32 ata-disk.c cvs diff: conflicting specifications of output style *** ata-disk.c 1999/10/18 17:55:38 1.32 --- ata-disk.c 1999/10/19 20:51:36 *************** *** 511,516 **** --- 511,527 ---- struct ad_softc *adp = request->device; int32_t dma_stat = 0; + /* + * watch for a race where ad_interrupt is called after ad_timeout + * has allready been committed to run. if that's the case, abort + * and let ad_timeout deal with reissuing the request. + */ + if (request->timeout_handle.callout && + !callout_pending(request->timeout_handle.callout)) { + printf("ad_interrupt: ad_timeout/ad_interrupt race detected. aborting.\n"); + return ATA_OP_CONTINUES; + } + /* finish DMA transfer */ if (request->flags & AR_F_DMA_USED) dma_stat = ata_dmadone(adp->controller); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 19 15:19: 1 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 96E1E17EED for ; Tue, 19 Oct 1999 15:18:54 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40355>; Wed, 20 Oct 1999 08:14:24 +1000 Content-return: prohibited Date: Wed, 20 Oct 1999 08:18:48 +1000 From: Peter Jeremy Subject: Re: boot problem In-reply-to: <14348.33521.475516.220514@grasshopper.cs.duke.edu> To: Andrew Gallatin Cc: freebsd-alpha@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct20.081424est.40355@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii References: <8025680F.00504FF6.00@d06mta01.portsmouth.uk.ibm.com> <14348.33521.475516.220514@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 1999-Oct-20 00:49:52 +1000, Andrew Gallatin wrote: >BTW, I've never even *seen* a 3.3 CD-ROM, much less used one. Does >anybody out there know if sysinstall is really broken enough to forget >to put the loader on the disk? There's no Alpha installation on the Walnut Creek 3.3 CD-ROM's. I thought I'd seen a comment on disk1 or disk2 stating that it was left off due to lack of space (but could be found on the FTP site), but can't find it now :-(. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Tue Oct 19 15:26:36 1999 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 4E70E17F04 for ; Tue, 19 Oct 1999 15:26:29 -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.1/8.9.1) with ESMTP id SAA04787; Tue, 19 Oct 1999 18:26:28 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id SAA03076; Tue, 19 Oct 1999 18:25:58 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 19 Oct 1999 18:25:58 -0400 (EDT) To: peter.jeremy@alcatel.com.au Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: boot problem In-Reply-To: <99Oct20.081424est.40355@border.alcanet.com.au> References: <8025680F.00504FF6.00@d06mta01.portsmouth.uk.ibm.com> <14348.33521.475516.220514@grasshopper.cs.duke.edu> <99Oct20.081424est.40355@border.alcanet.com.au> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14348.61400.698033.324875@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter Jeremy writes: > On 1999-Oct-20 00:49:52 +1000, Andrew Gallatin wrote: > >BTW, I've never even *seen* a 3.3 CD-ROM, much less used one. Does > >anybody out there know if sysinstall is really broken enough to forget > >to put the loader on the disk? > > There's no Alpha installation on the Walnut Creek 3.3 CD-ROM's. I > thought I'd seen a comment on disk1 or disk2 stating that it was left > off due to lack of space (but could be found on the FTP site), but > can't find it now :-(. > > Peter Well, now. That would certainly explain why the loader doesn't work. ------------------------------------------------------------------------------ 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 Oct 19 19:17:18 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from excalibar.sabrecross.com (excalibar.sabrecross.com [216.18.170.1]) by hub.freebsd.org (Postfix) with ESMTP id 1DD7518587 for ; Tue, 19 Oct 1999 19:17:15 -0700 (PDT) (envelope-from rickm@sabrecross.com) Received: from excalibar.sabrecross.com (excalibar.sabrecross.com [216.18.170.1]) by excalibar.sabrecross.com (8.9.3/8.9.3) with ESMTP id TAA07243; Tue, 19 Oct 1999 19:16:08 -0700 (PDT) Date: Tue, 19 Oct 1999 19:16:08 -0700 (PDT) From: Rick McGee To: peter.jeremy@alcatel.com.au Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: boot problem In-Reply-To: <99Oct20.081424est.40355@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org try: ftp.freebsd.org FreeBSD/releases/alpha/3.3-RELEASE www.cheapbytes.com usually has a cd or you can do a 3.2 release and then use sysinstall to upgrade. Still gotta make the floppies for 3.2 though. Another option is use the old CDR and burn it to disk. Use a high speed lan and do the install over the net. Rick On Wed, 20 Oct 1999, Peter Jeremy wrote: > On 1999-Oct-20 00:49:52 +1000, Andrew Gallatin wrote: > >BTW, I've never even *seen* a 3.3 CD-ROM, much less used one. Does > >anybody out there know if sysinstall is really broken enough to forget > >to put the loader on the disk? > > There's no Alpha installation on the Walnut Creek 3.3 CD-ROM's. I > thought I'd seen a comment on disk1 or disk2 stating that it was left > off due to lack of space (but could be found on the FTP site), but > can't find it now :-(. > > Peter > > > 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 Oct 20 1: 4:12 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (Postfix) with ESMTP id C4C49174A9 for ; Wed, 20 Oct 1999 01:03:52 -0700 (PDT) (envelope-from bottemanne@capitolonline.nl) Received: from capitolonline.nl ([195.121.168.14]) by smtp02.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA63F2; Wed, 20 Oct 1999 10:03:48 +0200 Message-ID: <380D85CE.D69F9319@capitolonline.nl> Date: Wed, 20 Oct 1999 10:05:18 +0100 From: Aernoudt Bottemanne X-Mailer: Mozilla 4.04 [en] (OS/2; I) MIME-Version: 1.0 To: Andrew Gallatin Cc: peter.jeremy@alcatel.com.au, freebsd-alpha@FreeBSD.ORG Subject: Re: boot problem References: <8025680F.00504FF6.00@d06mta01.portsmouth.uk.ibm.com> <14348.33521.475516.220514@grasshopper.cs.duke.edu> <99Oct20.081424est.40355@border.alcanet.com.au> <14348.61400.698033.324875@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Not True ! On the 2nd disk is the installation for Alpha. From now on eg further releases it will be a seperate distribution. Besides, there is a loader on the disk in /boot....... Why is does not work is something else. I still hope someone is able to help me out on this. The installation guide (in Complete FreeBSD) was written using a PWS433au, the same as I have, so it should be possible to get it up and running Andrew Gallatin wrote: > Peter Jeremy writes: > > On 1999-Oct-20 00:49:52 +1000, Andrew Gallatin wrote: > > >BTW, I've never even *seen* a 3.3 CD-ROM, much less used one. Does > > >anybody out there know if sysinstall is really broken enough to forget > > >to put the loader on the disk? > > > > There's no Alpha installation on the Walnut Creek 3.3 CD-ROM's. I > > thought I'd seen a comment on disk1 or disk2 stating that it was left > > off due to lack of space (but could be found on the FTP site), but > > can't find it now :-(. > > > > Peter > > Well, now. That would certainly explain why the loader doesn't work. > > ------------------------------------------------------------------------------ > 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 Oct 20 2: 1:17 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id B473E1B092 for ; Wed, 20 Oct 1999 02:00:55 -0700 (PDT) (envelope-from bottemanne@capitolonline.nl) Received: from capitolonline.nl ([195.121.168.129]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA66B7 for ; Wed, 20 Oct 1999 11:00:47 +0200 Message-ID: <380D930B.6C664F23@capitolonline.nl> Date: Wed, 20 Oct 1999 11:01:48 +0100 From: Aernoudt Bottemanne X-Mailer: Mozilla 4.04 [en] (OS/2; I) MIME-Version: 1.0 To: "freebsd-alpha@freebsd.org" Subject: Re: boot problem References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just installed with release 3.2 Unfortunately the same problem (the same error message too) Still the halt on code 2 : - ( How th f*** is this possible ?! Both 3.2 and 3.3 have this problem onnmy Alpha, which is totally scsi, so it should work normally..... Aernoudt Rick McGee wrote: > try: ftp.freebsd.org FreeBSD/releases/alpha/3.3-RELEASE > > www.cheapbytes.com usually has a cd or you can do a 3.2 release and then > use sysinstall to upgrade. Still gotta make the floppies for 3.2 > though. > > Another option is use the old CDR and burn it to disk. > Use a high speed lan and do the install over the net. > > Rick > > On Wed, 20 Oct 1999, Peter Jeremy wrote: > > > On 1999-Oct-20 00:49:52 +1000, Andrew Gallatin wrote: > > >BTW, I've never even *seen* a 3.3 CD-ROM, much less used one. Does > > >anybody out there know if sysinstall is really broken enough to forget > > >to put the loader on the disk? > > > > There's no Alpha installation on the Walnut Creek 3.3 CD-ROM's. I > > thought I'd seen a comment on disk1 or disk2 stating that it was left > > off due to lack of space (but could be found on the FTP site), but > > can't find it now :-(. > > > > Peter > > > > > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Oct 20 8:57:52 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 0D4C914A21; Wed, 20 Oct 1999 08:57:47 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id RAA53649; Wed, 20 Oct 1999 17:57:31 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199910201557.RAA53649@freebsd.dk> Subject: Re: workaround for ata driver woes on alpha In-Reply-To: <14348.55807.415236.565105@grasshopper.cs.duke.edu> from Andrew Gallatin at "Oct 19, 1999 04:57:48 pm" To: gallatin@cs.duke.edu (Andrew Gallatin) Date: Wed, 20 Oct 1999 17:57:31 +0200 (CEST) Cc: erik@habatech.no (Erik H. Bakke), alpha@FreeBSD.ORG, sos@FreeBSD.ORG, mjacob@feral.com X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It seems Andrew Gallatin wrote: > > I finally got around to testing it & it seems to work. The appended > patch is courtesy of Darrell Anderson (anderson@cs.duke.edu). > > I believe Matt's suggestion is probably the real fix. > > Also, we've seen this problem (albeit rarely) on PCs under extreme > load as well. (450MHz PIII, 2 promise cards, 4 22GB IBM Deskstar drive as each > channel's primary master, sinking data to/from a gigabit link to a > number of clients) OK, I'll take a look at it, I'm currently buzy at freebsdcon, so it might be a couble of days until then, but anyhow I have a number of other fixes that I need to test in my lab back home too... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Wed Oct 20 21:36:43 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from sstar.com (sstar.com [209.102.160.1]) by hub.freebsd.org (Postfix) with ESMTP id 23B7D14C31 for ; Wed, 20 Oct 1999 21:36:41 -0700 (PDT) (envelope-from king@sstar.com) Received: from MAROON ([134.132.228.8]) by sstar.com with ESMTP (IPAD 2.5s/64) id 1607500; Wed, 20 Oct 1999 23:36:24 -0500 Message-Id: <4.2.0.58.19991020233619.00afcaf0@mail.sstar.com> X-Sender: king@mail.sstar.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Wed, 20 Oct 1999 23:36:23 -0500 To: alpha@freebsd.org From: Jim King Subject: No tun interface Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have pseudo-device tun 1 in my kernel config, but 'ifconfig -a' doesn't show a tun0 interface. What's going on? Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Oct 21 1:32:22 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from post.bgnett.no (post.bgnett.no [194.54.96.133]) by hub.freebsd.org (Postfix) with ESMTP id F0A7914BB8 for ; Thu, 21 Oct 1999 01:32:06 -0700 (PDT) (envelope-from erik@habatech.no) Received: from bsdbox.habatech.no ([62.92.133.3]) by post.bgnett.no (8.8.8/8.8.8) with ESMTP id KAA03467 for ; Thu, 21 Oct 1999 10:31:57 +0200 (CEST) (envelope-from erik@habatech.no) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199910201557.RAA53649@freebsd.dk> Date: Thu, 21 Oct 1999 10:31:44 +0200 (CEST) From: "Erik H. Bakke" To: freebsd-alpha@freebsd.org Subject: Re: workaround for ata driver woes on alpha Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 20-Oct-99 Soren Schmidt wrote: > It seems Andrew Gallatin wrote: >> >> I finally got around to testing it & it seems to work. The appended >> patch is courtesy of Darrell Anderson (anderson@cs.duke.edu). >> >> I believe Matt's suggestion is probably the real fix. >> >> Also, we've seen this problem (albeit rarely) on PCs under extreme >> load as well. (450MHz PIII, 2 promise cards, 4 22GB IBM Deskstar drive as >> each >> channel's primary master, sinking data to/from a gigabit link to a >> number of clients) > > OK, I'll take a look at it, I'm currently buzy at freebsdcon, so it might > be a couble of days until then, but anyhow I have a number of other > fixes that I need to test in my lab back home too... > Also, the patch has been tested on my 164SX for a couple of days, under heavy disk load, and it seems to be quite stable. ===========================+================+=============================== Erik H. Bakke | | To be or not to be... Senior Consultant/Developer|erik@habatech.no| Is simply a question of Habatech AS | | binary logic ===========================+================+============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Oct 21 11:10:21 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 399C614F78 for ; Thu, 21 Oct 1999 11:10:18 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id LAA10601 for ; Thu, 21 Oct 1999 11:10:17 -0700 Date: Thu, 21 Oct 1999 11:10:19 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: alpha@freebsd.org Subject: builds: another odd one... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org build doesn't make it through 'coz vgrind hangs (?) 601 ?? Is 0:00.02 /bin/sh -c $HOME/bin/Nightly-FreeBSD-Build 603 ?? I 0:00.01 /bin/sh /home/mjacob/bin/Nightly-FreeBSD-Build 605 ?? I 0:00.02 sh ./DOMAKE buildworld 606 ?? I 0:00.03 make buildworld 609 ?? I 0:00.00 /bin/sh -ec cd /usr/src; make -f Makefile.inc0 -m /u 610 ?? I 0:00.03 make -f Makefile.inc0 -m /usr/src/share/mk buildworld 613 ?? I 0:00.00 /bin/sh -ec cd /usr/src; make -m /usr/src/share/mk - 614 ?? I 0:00.13 make -m /usr/src/share/mk -f Makefile.inc1 buildworld 18314 ?? I 0:00.03 /usr/obj/usr/src/tmp/usr/bin/make all SUBDIR_CHANGE D 18318 ?? I 0:00.01 /bin/sh -ec for entry in colldef dict doc examples in 18343 ?? I 0:00.03 /usr/obj/usr/src/tmp/usr/bin/make all SUBDIR_CHANGE D 18347 ?? I 0:00.01 /bin/sh -ec for entry in psd smm usd papers ; do (if 19562 ?? I 0:00.03 /usr/obj/usr/src/tmp/usr/bin/make all SUBDIR_CHANGE D 19566 ?? I 0:00.01 /bin/sh -ec for entry in beyond4.3 diskperf fsinterfa 19603 ?? I 0:00.04 /usr/obj/usr/src/tmp/usr/bin/make all SUBDIR_CHANGE D 19609 ?? I 0:00.00 /bin/sh -ec vgrind -f < /usr/src/share/doc/papers/ker 19610 ?? R 240:37.19 /bin/csh -f /usr/obj/usr/src/tmp/usr/bin/vgrind -f 19611 ?? Z 0:00.00 (vfontedpr) 19612 ?? Z 0:00.00 (cat) 19769 ?? Ss 0:00.10 rlogind 97901 ?? I 0:00.00 /bin/sh -ec cd /usr/src; PATH=/usr/obj/usr/src/tmp/sb 97902 ?? I 0:00.08 /usr/obj/usr/src/tmp/usr/bin/make DESTDIR -f Makefile 97905 ?? I 0:00.02 /bin/sh -ec for entry in share/info include lib bin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Oct 21 13: 1:19 1999 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 E9A0C14F55 for ; Thu, 21 Oct 1999 13:01:16 -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.1/8.9.1) with ESMTP id QAA27401; Thu, 21 Oct 1999 16:01:14 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id QAA07830; Thu, 21 Oct 1999 16:00:43 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 21 Oct 1999 16:00:43 -0400 (EDT) To: mjacob@feral.com Cc: alpha@freebsd.org Subject: Re: builds: another odd one... In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14351.28348.956818.294338@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Weird. If anything, I'd expect an objtrm hang, not a job spinning around, soaking up cpu. I just built the world with a fresh tree using make -j4. This was a tree checked out of a cvs repo cvsupped around 4am EDT. ------------------------------------------------------------------------------ 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 Thu Oct 21 13:57:47 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id AE19614FDC for ; Thu, 21 Oct 1999 13:57:43 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id NAA11519; Thu, 21 Oct 1999 13:57:35 -0700 Date: Thu, 21 Oct 1999 13:57:33 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: alpha@FreeBSD.ORG Subject: Re: builds: another odd one... In-Reply-To: <14351.28348.956818.294338@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, I installed vgrind by hand and restarted. We'll see.... On Thu, 21 Oct 1999, Andrew Gallatin wrote: > > Weird. If anything, I'd expect an objtrm hang, not a job spinning > around, soaking up cpu. > > I just built the world with a fresh tree using make -j4. This was a > tree checked out of a cvs repo cvsupped around 4am EDT. > > ------------------------------------------------------------------------------ > 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 Thu Oct 21 14:24: 4 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id A274C14FC7 for ; Thu, 21 Oct 1999 14:24:01 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40324>; Fri, 22 Oct 1999 07:19:20 +1000 Content-return: prohibited Date: Fri, 22 Oct 1999 07:23:50 +1000 From: Peter Jeremy Subject: Alpha vs i386 filesystems To: alpha@FreeBSD.ORG Reply-To: peter.jeremy@alcatel.com.au Message-Id: <99Oct22.071920est.40324@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0pre3i Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has anyone ever tried building an Alpha boot disk (SCSI HD) on an i386 box? I presume the partition tables and UFS formats are identical, so the approach would be: - add disk to i386 system as `dangerously dedicated' (ie no slice table) - partition disk normally - install Alpha bootloaders with `disklabel -B', explicitly specifying the boot1 and boot2 from the Alpha release. - newfs partitions as wanted and copy Alpha release files into them. - move disk from i386 to Alpha and boot it. [I'm looking at this approach because I can't get netboot to work. I intend to write a separate missive, probably in -current, about my experiences trying to cross-compile netboot]. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Oct 21 18:40:23 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id B123B14D0F; Thu, 21 Oct 1999 18:40:21 -0700 (PDT) (envelope-from tlambert@usr07.primenet.com) Received: (from daemon@localhost) by smtp02.primenet.com (8.8.8/8.8.8) id SAA12988; Thu, 21 Oct 1999 18:40:17 -0700 (MST) Received: from usr07.primenet.com(206.165.6.207) via SMTP by smtp02.primenet.com, id smtpd012978; Thu Oct 21 18:40:10 1999 Received: (from tlambert@localhost) by usr07.primenet.com (8.8.5/8.8.5) id SAA05716; Thu, 21 Oct 1999 18:40:08 -0700 (MST) From: Terry Lambert Message-Id: <199910220140.SAA05716@usr07.primenet.com> Subject: Re: ata busmaster i/o port on alpha To: gallatin@cs.duke.edu (Andrew Gallatin) Date: Fri, 22 Oct 1999 01:40:08 +0000 (GMT) Cc: sos@FreeBSD.ORG, freebsd-alpha@FreeBSD.ORG In-Reply-To: <14348.40785.536064.278837@grasshopper.cs.duke.edu> from "Andrew Gallatin" at Oct 19, 99 01:02:14 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by usr07.primenet.com id SAA05716 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > S=F8ren, >=20 > I'm trying to get the on-board IDE controllers in some AlphaServer > DS10 machines working well w/FreeBSD-current. They use the Acer > AladdinV IDE controller in combination with a FUJITSU MPD3108AT ATA-4 > disk. >=20 > The problem is with where the "Bios" (aka the SRM console) puts the > busmaster address: >=20 > <12:45pm>opal/root:~#pciconf -r 'pci0:13:0' 0x20 > 0x00010111 >=20 > When you read the bus master address you mask off the upper 16 bits > entirely and we see the address as 0x110 where as it should really be=20 > 0x10110. When this happens, the disk is of course unusable. After > 5 retries, I see I/O errors when I try to access the disk. >=20 > If I apply the following patch, DMA works: [ ... ] > So, my question: Is are you loosing the upper 16 bits for a reason, > or is it valid to look at the upper 16 bits on all platforms? It's truly cool to see that there are people with more Alpha knowledge than x86 knowledge who are FreeBSD junkies. 8-). This masking is a bit of historical arcanum dating back to the IBM PC AT. On x86, the I/O address space wraps. Some code depends on this behaviour. This masking should probably be done in a (platform changeable) macro, in any case. The reason for making it a macro is to allow the macro to be used in the PnP case, when the (unwrapped) address space has been exhausted. A bigger address space may be a problem, if the ISA interface only connects 16 bits (yes, some PC's do this!). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Oct 21 19: 0:17 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from sstar.com (sstar.com [209.102.160.1]) by hub.freebsd.org (Postfix) with ESMTP id 2AA3814D0F for ; Thu, 21 Oct 1999 19:00:14 -0700 (PDT) (envelope-from king@sstar.com) Received: from MAROON ([134.132.228.8]) by sstar.com with ESMTP (IPAD 2.5s/64) id 2170600; Thu, 21 Oct 1999 21:00:11 -0500 Message-Id: <4.2.0.58.19991021205744.01706ca8@mail.sstar.com> X-Sender: king@mail.sstar.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Thu, 21 Oct 1999 21:00:10 -0500 To: Terry Lambert , gallatin@cs.duke.edu (Andrew Gallatin) From: Jim King Subject: Re: ata busmaster i/o port on alpha Cc: freebsd-alpha@FreeBSD.ORG In-Reply-To: <199910220140.SAA05716@usr07.primenet.com> References: <14348.40785.536064.278837@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 01:40 AM 10/22/1999 +0000, Terry Lambert wrote: > > S=F8ren, > > > > I'm trying to get the on-board IDE controllers in some AlphaServer > > DS10 machines working well w/FreeBSD-current. They use the Acer > > AladdinV IDE controller in combination with a FUJITSU MPD3108AT ATA-4 > > disk. > > > > The problem is with where the "Bios" (aka the SRM console) puts the > > busmaster address: > > > > <12:45pm>opal/root:~#pciconf -r 'pci0:13:0' 0x20 > > 0x00010111 > > > > When you read the bus master address you mask off the upper 16 bits > > entirely and we see the address as 0x110 where as it should really be > > 0x10110. When this happens, the disk is of course unusable. After > > 5 retries, I see I/O errors when I try to access the disk. > > > > If I apply the following patch, DMA works: > >[ ... ] > > > So, my question: Is are you loosing the upper 16 bits for a reason, > > or is it valid to look at the upper 16 bits on all platforms? > >It's truly cool to see that there are people with more Alpha >knowledge than x86 knowledge who are FreeBSD junkies. 8-). > >This masking is a bit of historical arcanum dating back to the >IBM PC AT. > >On x86, the I/O address space wraps. Some code depends on this >behaviour. > >This masking should probably be done in a (platform changeable) >macro, in any case. > >The reason for making it a macro is to allow the macro to be used >in the PnP case, when the (unwrapped) address space has been >exhausted. > >A bigger address space may be a problem, if the ISA interface >only connects 16 bits (yes, some PC's do this!). And of course, just to get really arcane and off topic, let's not forget=20 that the original IBM PC speced that I/O cards were to only pay attention=20 to the lower *10* bits of the I/O space, which is why all those ISA cards=20 try to cram into 0x3ff and below. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Thu Oct 21 19:23: 3 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.cybcon.com (mail.cybcon.com [216.190.188.5]) by hub.freebsd.org (Postfix) with ESMTP id 758B214D69; Thu, 21 Oct 1999 19:22:59 -0700 (PDT) (envelope-from wwoods@cybcon.com) Received: from freebsd.cybcon.com (william@pm3b-40.cybcon.com [205.147.75.105]) by mail.cybcon.com (8.9.0/8.9.0) with SMTP id TAA06662; Thu, 21 Oct 1999 19:22:51 -0700 (PDT) From: william woods Reply-To: wwoods@cybcon.com To: freebsd-current@freebsd.org Subject: Re: snapshots..... Date: Thu, 21 Oct 1999 19:21:28 -0700 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: In-Reply-To: Cc: freebsd-alpha@freebsd.org MIME-Version: 1.0 Message-Id: <99102119224101.00309@freebsd.cybcon.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ahh...that is the X86 -current, not the Alpha current...how often are alpha -currents made? On Thu, 21 Oct 1999, you wrote: > current.freebsd.org > > Pull down the file > > ftp://current.freebsd.org/pub/FreeBSD/snapshots/19991012.tar > > (or something similar) > > It is a tar file (created on the fly) and will contain everything you > need for an installation. Drop the files kern.flp and mfsroot.flp in > ./floppies/ on a floppy reboot and choose as the media 'file system' > > Hope this helps. > > Nick > > > On Thu, 21 Oct 1999, william woods wrote: > > > Where is the best place to get -current snapshots from? I am > > running 4.0-19990915-CURRENT FreeBSD 4.0-19990915-CURRENT #0: > > Mon Oct 18 19:00:56 PDT 1999 and was wondering to get the latest snaps.... > > > > William > > > > --BEGIN GEEK CODE BLOCK----- > > Version: 3.1 > > GIT d++ s+:+ a C+++ UB+++ P+ L++ E- W++ N+ o+ K- w > > O- M-- V PS-- PE++ Y+ PGP t+ 5+ X R- tv- b++ DI+ D > > G e++ h---- r+++ y++++ > > ------END GEEK CODE BLOCK------ > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > -- William Woods FreeBSD 3.3-Stable -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GIT d++ s+:+ a C+++ UB+++ P+ L++ E- W++ N+ o+ K- w O- M-- V PS-- PE++ Y+ PGP t+ 5+ X R- tv- b++ DI+ D G e++ h---- r+++ y++++ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Oct 22 2:14:23 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.217.82.22]) by hub.freebsd.org (Postfix) with ESMTP id 0AD0814BF4 for ; Fri, 22 Oct 1999 02:14:17 -0700 (PDT) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id KAA80857; Fri, 22 Oct 1999 10:14:06 +0100 (BST) (envelope-from geoffb) Date: Fri, 22 Oct 1999 10:14:06 +0100 From: Geoff Buckingham To: peter.jeremy@alcatel.com.au Cc: alpha@FreeBSD.ORG Subject: Re: Alpha vs i386 filesystems Message-ID: <19991022101406.C78625@chuggalug.clues.com> References: <99Oct22.071920est.40324@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <99Oct22.071920est.40324@border.alcanet.com.au>; from Peter Jeremy on Fri, Oct 22, 1999 at 07:23:50AM +1000 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Oct 22, 1999 at 07:23:50AM +1000, Peter Jeremy wrote: > Has anyone ever tried building an Alpha boot disk (SCSI HD) on an i386 > box? > > I presume the partition tables and UFS formats are identical, so the > approach would be: > - add disk to i386 system as `dangerously dedicated' (ie no slice table) > - partition disk normally > - install Alpha bootloaders with `disklabel -B', explicitly specifying > the boot1 and boot2 from the Alpha release. > - newfs partitions as wanted and copy Alpha release files into them. > - move disk from i386 to Alpha and boot it. > > [I'm looking at this approach because I can't get netboot to work. > I intend to write a separate missive, probably in -current, about > my experiences trying to cross-compile netboot]. I had trouble booting from floppies to install on the alpha and eventually dd'd the 2.88MB boot.flp floppy image onto a scsi disk in a PC and then transfered this to the alpha and installed from that. So the process you describe above should work, but isn't required. -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Oct 22 5:28:20 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from sstar.com (sstar.com [209.102.160.1]) by hub.freebsd.org (Postfix) with ESMTP id 0687014BE9 for ; Fri, 22 Oct 1999 05:28:12 -0700 (PDT) (envelope-from king@sstar.com) Received: from MAROON ([134.132.228.8]) by sstar.com with ESMTP (IPAD 2.5s/64) id 2434800; Fri, 22 Oct 1999 07:28:09 -0500 Message-Id: <4.2.0.58.19991022072631.01708a80@mail.sstar.com> X-Sender: king@mail.sstar.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Fri, 22 Oct 1999 07:28:09 -0500 To: Geoff Buckingham , peter.jeremy@alcatel.com.au From: Jim King Subject: Re: Alpha vs i386 filesystems Cc: alpha@FreeBSD.ORG In-Reply-To: <19991022101406.C78625@chuggalug.clues.com> References: <99Oct22.071920est.40324@border.alcanet.com.au> <99Oct22.071920est.40324@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 10:14 AM 10/22/1999 +0100, Geoff Buckingham wrote: >On Fri, Oct 22, 1999 at 07:23:50AM +1000, Peter Jeremy wrote: > > Has anyone ever tried building an Alpha boot disk (SCSI HD) on an i386 > > box? > > > > I presume the partition tables and UFS formats are identical, so the > > approach would be: > > - add disk to i386 system as `dangerously dedicated' (ie no slice table) > > - partition disk normally > > - install Alpha bootloaders with `disklabel -B', explicitly specifying > > the boot1 and boot2 from the Alpha release. > > - newfs partitions as wanted and copy Alpha release files into them. > > - move disk from i386 to Alpha and boot it. > > > > [I'm looking at this approach because I can't get netboot to work. > > I intend to write a separate missive, probably in -current, about > > my experiences trying to cross-compile netboot]. > >I had trouble booting from floppies to install on the alpha and eventually >dd'd the 2.88MB boot.flp floppy image onto a scsi disk in a PC and then >transfered this to the alpha and installed from that. So the process >you describe above should work, but isn't required. I did something similar: I dd'ed the 2.88 MB boot.flp image onto a Zip disk and booted my Alpha from a SCSI Zip drive. Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Oct 22 6: 1:34 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from bsd.santhia.alpcom.it (bsd.santhia.alpcom.it [194.243.65.214]) by hub.freebsd.org (Postfix) with ESMTP id 26C6714F1C for ; Fri, 22 Oct 1999 06:01:20 -0700 (PDT) (envelope-from chr.ang@biella.alpcom.it) Received: from biella.alpcom.it (chris.biella.alpcom.it [194.243.65.7]) by bsd.santhia.alpcom.it (8.8.8/8.8.8) with ESMTP id PAA11060 for ; Fri, 22 Oct 1999 15:11:05 +0200 (CEST) Message-ID: <3810608E.AD53B4AE@biella.alpcom.it> Date: Fri, 22 Oct 1999 15:03:11 +0200 From: Cristian Angelini Reply-To: chr.ang@biella.alpcom.it X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: alpha@freebsd.org Subject: Alphaserver 1000 4/233 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, I just powered off my last non-freebsd server here, an old Alphaserver with osf/1 that they bought here when they opened this ISP. My first idea was to scratch OSF/1 and install Freebsd over it, to play a bit in an enviroment that I know better - we have 4 servers with Freebsd and one with Pico, and 10+ installations around our small county. While I had to fight a bit with our floppy drive - we never used that and I even discovered it was disconnected :( - I succeded at booting the two floppies. It panic-ed just before starting, stating that architecture was not supported - I was waiting that, since I didn't read our server in the supported hardware list. I'm wondering if this architecture will be added in the future or not, since hardware is relatively old ... Well it's not an important machine here now, but I'd like to use it since it costed them a lot .... Sincerely, C.Angelini To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Fri Oct 22 7:36:17 1999 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 B418014C1D for ; Fri, 22 Oct 1999 07:36: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.1/8.9.1) with ESMTP id KAA16603; Fri, 22 Oct 1999 10:35:59 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id KAA01337; Fri, 22 Oct 1999 10:35:29 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 22 Oct 1999 10:35:29 -0400 (EDT) To: Terry Lambert Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: ata busmaster i/o port on alpha In-Reply-To: <199910220140.SAA05716@usr07.primenet.com> References: <14348.40785.536064.278837@grasshopper.cs.duke.edu> <199910220140.SAA05716@usr07.primenet.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14352.29097.552059.840074@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Terry Lambert writes: > > > So, my question: Is are you loosing the upper 16 bits for a reason, > > or is it valid to look at the upper 16 bits on all platforms? > > It's truly cool to see that there are people with more Alpha > knowledge than x86 knowledge who are FreeBSD junkies. 8-). Yep. I fully admit that I don't really know how a PC works. I know a hell of a lot more about alphas. > This masking is a bit of historical arcanum dating back to the > IBM PC AT. > > On x86, the I/O address space wraps. Some code depends on this > behaviour. > > This masking should probably be done in a (platform changeable) > macro, in any case. I thought that might be the case, OK, a macro sounds like the right thing to do then. Thanks for the explanation. 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 Fri Oct 22 17: 3:37 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id 4615F14FDE for ; Fri, 22 Oct 1999 17:03:19 -0700 (PDT) (envelope-from bottemanne@capitolonline.nl) Received: from capitolonline.nl ([195.121.169.125]) by smtp05.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA4DBF for ; Sat, 23 Oct 1999 02:03:17 +0200 Message-ID: <381109B0.2CA10860@capitolonline.nl> Date: Sat, 23 Oct 1999 02:04:48 +0100 From: Aernoudt Bottemanne X-Mailer: Mozilla 4.04 [en] (OS/2; I) MIME-Version: 1.0 To: "freebsd-alpha@freebsd.org" Subject: de0 problems in current Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, After upgrading the system to current, form 3.3, my network card does not work anymore. During boot the error message says that it can not map an interrupt. It did work before on 3.3 and no hardware changes were applied. Does anybody have an idea why it stopped working ? Thanks Aernoudt PWS433au, with onboard DEC Ethernet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Oct 23 14: 8:17 1999 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 6EE3714E5A for ; Sat, 23 Oct 1999 14:08:06 -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.1/8.9.1) with ESMTP id RAA14237; Sat, 23 Oct 1999 17:08:05 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id RAA11698; Sat, 23 Oct 1999 17:07:35 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 23 Oct 1999 17:07:35 -0400 (EDT) To: dfr@nlsystems.com Cc: alpha@freebsd.org Subject: small fix for irq mappig probelm X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14354.8792.767477.900314@grasshopper.cs.duke.edu> Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug, When using a kernel built after your recent changes to pci.c, alpha PCI devices with intline==0 fail to map their interrupt. This typically happens with the on-board tulip in a miata: de0: irq 0 at device 3.0 on pci0 pci_map_int: can't allocate interrupt The appended patch fixes it, but I am unsure it is correct. Can you approve it? 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 Index: sys/pci/pci.c =================================================================== RCS file: /home/ncvs/src/sys/pci/pci.c,v retrieving revision 1.123 diff -u -r1.123 pci.c --- pci.c 1999/10/17 06:48:47 1.123 +++ pci.c 1999/10/23 20:56:52 @@ -1045,7 +1045,7 @@ (unsigned int) base, ln2size); } } - if (cfg->intline) + if (cfg->intpin) resource_list_add(rl, SYS_RES_IRQ, 0, cfg->intline, cfg->intline, 1); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message From owner-freebsd-alpha Sat Oct 23 14:11:56 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (Postfix) with ESMTP id 0792D14E5A for ; Sat, 23 Oct 1999 14:11:53 -0700 (PDT) (envelope-from bottemanne@capitolonline.nl) Received: from capitolonline.nl ([195.121.168.199]) by smtp01.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA699C for ; Sat, 23 Oct 1999 23:11:51 +0200 Message-ID: <38123302.D8A39378@capitolonline.nl> Date: Sat, 23 Oct 1999 23:13:23 +0100 From: Aernoudt Bottemanne X-Mailer: Mozilla 4.04 [en] (OS/2; I) MIME-Version: 1.0 To: "freebsd-alpha@freebsd.org" Subject: boot errors after upgrading to current: cvsupped yesterday Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, After upgrading my PWS 433au to current yesterday, the deo adapter does not get an interrupt. Also some other messages: *************************************************************************************** Unrecognized boot flag '0'. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Mon May 17 01:41:18 CEST 1999 root@princess.capitolonline.nl:/usr/src/sys/compile/PRINCESS Digital Personal Workstation (Miata) Digital Personal WorkStation 433au, 432MHz 8192 byte page size, 1 processor. CPU: EV56 (21164A) major=7 minor=0 extensions=0x1 OSF PAL rev: 0x1000000020116 real memory = 132177920 (129080K bytes) avail memory = 123650048 (120752K bytes) Preloaded elf kernel "kernel" at 0xfffffc00005ec000. cia0: Pyxis, pass 1 cia0: extended capabilities: 1 cia0: WARNING: Pyxis pass 1 DMA bug; no bets... pcib0: <2117x PCI host bus adapter> on cia0 pci0: on pcib0 de0: irq 0 at device 3.0 on pci0 pci_map_int: can't allocate interrupt de0: couldn't map interrupt chip0: irq 1 at device 4.0 on pci0 isab0: at device 7.0 on pci0 isa0: on isab0 pcib1: at device 8.0 on pci0 pci1: on pcib1 isp0: irq 20 at device 10.0 on pci1 isp0: interrupting at CIA irq 20 isp0: Ultra Mode Capable vga-pci0: irq 8 at device 12.0 on pci0 mcclock0: at port 0x70-0x71 on isa0 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio0: interrupting at ISA irq 4 sio1: reserved for low-level i/o fdc0: interrupting at ISA irq 6 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd0: interrupting at ISA irq 1 psm0: irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0 psm0: interrupting at ISA irq 12 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> struct nfssvc_sock bloated (> 256bytes) Try reducing NFS_UIDHASHSIZ struct nfsuid bloated (> 128bytes) Try unionizing the nu_nickname and nu_flag fields Timecounter "alpha" frequency 433215332 Hz Waiting 10 seconds for SCSI devices to settle isp0: driver initiated bus reset of bus 0 Creating DISK da0 Creating DISK da1 Creating DISK da2 Creating DISK cd0 da0 at isp0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4095MB (8388314 512 byte sectors: 255H 63S/T 522C) da1 at isp0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4091MB (8380080 512 byte sectors: 255H 63S/T 521C) cd0 at isp0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [326562 x 2048 byte records] da2 at isp0 bus 0 target 4 lun 0 da2: Removable Direct Access SCSI-2 device da2: 3.300MB/s transfers da2: 96MB (196608 512 byte sectors: 64H 32S/T 96C) *************************************************************************************** Cheers, Aernoudt "FreeBSD: with patented Gates-Be-Gone(TM) gets rid of blue screens in a flash! It forks! It blits! Look at those fantastic pixels! It surfs the web! You could even host an ISP with it!" Unix: the solution to the W2K problem To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message