freefall hangs w/ nfs
It looks on the face of it that AMD is hanging. Perhaps this is preventing the system from clearing out buffers and causing lockups on other mounts. AMD could also be causing a deadlock to occur in the buffer cache (for the same reason loopback mounts can cause deadlocks). The next time this happens, if the person rebooting freefall can get a kernel dump (and have a corresponding debug kernel) I may be able to track it down for sure. Fixing it is another problem, though. Loopback deadlocks are a big problem under 3.x. Essentially what occurs under 3.x is that the buffer cache runs out of buffers (or buffer space) during a client op and tries to synchronously flush unrelated dirty buffers to clear out some room. It may flush a write of a client side buffer which runs an rpc to an nfsd running on the same machine (i.e. via a loopback mount) which then turns around and tries to allocate a new buffer to issue it's filesystem write, which may in turn also run out of buffers or buffer space and attempt to flush another unrelated dirty buffer which could be another client-side buffer. But at that point nfsd is locked up in getnewbuf(), so the result is a deadlock that locks up the NFS node entirely (and might NOT lockup the rest of the machine). Under 3.x this is a big problem due to the synchronous flush recursion in getnewbuf(). Under 4.x this is not as big a problem because flushing is asynchronized by the buf_daemon. I've been trying to find a solution to the problem for 3.x. I have a few ideas. I think we can add a flag to the mount structure that getnewbuf() would set when synchronously flushing a buffer. The flag would prevent another getnewbuf() call (say one called from nfsd) from trying to flush buffers from the same client mount, preventing a deadlock. I have to setup a 3.x box and reproduce the deadlock before I can test the fix, though, and that will take a bit of time. -Matt Oct 15 06:18:08 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 15 06:44:49 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 15 16:29:50 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 15 16:37:26 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 15 22:46:08 freefall shutdown: reboot by jdp: Rebooting to unstick NFS Oct 21 03:10:15 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 21 03:34:24 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 21 04:38:39 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 21 04:46:56 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 21 11:56:01 freefall shutdown: reboot by jdp: Rebooting to clear filesystem related hangs Oct 22 04:23:41 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 22 04:56:57 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 22 16:40:55 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 22 17:52:34 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 23 00:36:56 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 23 02:45:57 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 23 04:16:57 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 23 04:46:56 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 23 14:44:22 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 23 14:51:53 freefall /kernel: nfs server pid173@freefall:/host: not responding Oct 23 15:35:55 freefall amd[24839]: /host: mount (amfs_auto_cont): Stale NFS file handle Oct 23 15:35:55 freefall /kernel: nfs server pid173@freefall:/host: is alive again Oct 23 15:38:40 freefall amd[25003]: /host: mount (amfs_auto_cont): Stale NFS file handle Oct 23 15:44:05 freefall shutdown: reboot by unfurl: To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Are we going to fix -current's ed driver anytime soon?
I've added the hack for NCARD = 0 to if_ed_isa.c On Sat, 23 Oct 1999, Jordan K. Hubbard wrote: > >From current.freebsd.org's release build log: > > linking BOOTMFS > if_ed_isa.o: In function `ed_isa_probe': > if_ed_isa.o(.text+0x45): undefined reference to `ed_probe_WD80x3' > if_ed_isa.o(.text+0x54): undefined reference to `ed_release_resources' > if_ed_isa.o(.text+0x5a): undefined reference to `ed_probe_3Com' > if_ed_isa.o(.text+0x69): undefined reference to `ed_release_resources' > if_ed_isa.o(.text+0x6f): undefined reference to `ed_probe_Novell' > if_ed_isa.o(.text+0x7e): undefined reference to `ed_release_resources' > > It's time to either fix this or back out the changes which broke it. > If nobody finds the time to do the former in the next 48 hours, I'll > do the latter myself. > > - Jordan > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NOTE NOTE NOTE:Re: does anybody but me (..vgrinds forever...)
As Matthew Jacob wrote ... > > On Sat, 23 Oct 1999, Matthew Dillon wrote: > > > :It really is vgring hanging on a file: > > : > > :vgrind -f < /usr/src/share/doc/papers/kernmalloc/appendix.t > appendix.ms > > : > > :A plain vgrind -f on this file also hangs. Anyone have a clue on this? > > : > > :This happens for me on an alpha. > > : > > :-matt > > > > The vgrind command above does not hang on my PIII test box. It takes > > about a second to run. I tried both an old binary and a new binary of > > vgrind. Both worked. > > > > I recommend compiling vgrind up w/ full debugging and attaching a > > debugger to it to see what is up. > > > Not an executable... but I finally figured it out... Pipes possibly broken > as set up by csh- csh was an old (Oct 1) csh. Until I updated csh from the > current build tree, what actually was happening was vfontedpr was piping > to 'cat -' and this was hanging. Wierd city, but all better now I > believe... possibly related to the signal changes(?) I've seen the same (see the list archives) on alpha a week or 2 back. Solved by manually making and installing csh. W/ -- | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sio working
On 23-Oct-99 Warner Losh wrote: > In message <[EMAIL PROTECTED]> Will Andrews > writes: >: I will be your guinea pig, if you like. :-) > > Grab the current patches from > http://www.freebsd.org/~imp/pccard-snap.patch > but read my other posting about the warnings and such. As of yet, I haven't tested your code. I will be, in a few. I took the opportunity to go over the patch first. I noticed a little discrepancy in ep_pccard_identify, where the switch() does not offer a default: case. You should put something like that in there and call the card "Unknown 3Com card" or somesuch. Same for ep_pccard_card_attach(). That's all I can manage from a quick skim of your code. Well, I'm gonna test out this kernel patch. (after safely backing up sys/). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trek73
> Did anyone bother to look at /usr/src/games/trek/main.c: trek != trek73. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trek73
> > No. Make it a port. Policy, remember? 8) > > I guess the anti-bloatists would have a point on this one... > > I would not object to a port. It certainly eliminates the > bike shed arguments over it. Did anyone bother to look at /usr/src/games/trek/main.c: ** C version by Eric P. Allman 5/76 (U.C. Berkeley) with help ** from Jeff Poskanzer and Pete Rubinstein. ** ... This is the original UCB BSD version of trek as has been shipping since the BSD 2.x days -- Rod Grimes - KD7CAX - (RWG25)[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trek73
> No. Make it a port. Policy, remember? 8) I guess the anti-bloatists would have a point on this one... I would not object to a port. It certainly eliminates the bike shed arguments over it. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trek73
> > I guess the real question is: /usr/games or /usr/ports? I don't care > > which, but I would personally prefer /usr/games because it really is > > an old-time berkeley program. > > Perhaps we should ask Kirk... ;) No. Make it a port. Policy, remember? 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trek73
On Sat, 23 Oct 1999, Matthew Dillon wrote: > I found a copy of the C version of trek73 in my Amiga archives. This > is the trek73 originally written in HP-2000 Basic that was rewritten > by Dave Pare and Chris Williams in C and seriously enhanced by a bunch > of people including me in my early college years circa 1985. > > I don't think any of the authors would mind if it went into /usr/games, > but tracking them down is close to impossible since ucbvax no longer > exists. If nobody knows different, I would like to clean it up (fairly > easy since it's already in C) and commit it in. > > I've included the docs below. Remembering from ancient history, didn't this make the rounds to just about anyone who wanted to learn code? I think it was even in a DEC games book. I think putting this into games is safe, but there's another trek in games already ... I haven't played trek in a looong time, is this one better in some way than the one already there? If it doesn't get into /usr/games, anyhow, it can certainly go into ports. Chuck Robey| Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770| I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trek73
> I guess the real question is: /usr/games or /usr/ports? I don't care > which, but I would personally prefer /usr/games because it really is > an old-time berkeley program. Perhaps we should ask Kirk... ;) - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trek73
: :> I don't think any of the authors would mind if it went into /usr/games, : :I certainly wouldn't. It would be an old game returning home to the :Berkeley world, and I also used to play it a lot on the HP-2000. : :The 'ol HP 2000 access, now that brings back memories... Did you know :I once wrote an entire multi-user BBS (emeryville's HP-BBS) in HP :basic? But I digress.. :) : :- Jordan Heh, I think I heard about that BBS but the only HP 2000 I ever used was the one Berkeley High had. Oh, and LHS had one too - though that might have been a higher powered model. I guess the real question is: /usr/games or /usr/ports? I don't care which, but I would personally prefer /usr/games because it really is an old-time berkeley program. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: trek73
> I don't think any of the authors would mind if it went into /usr/games, I certainly wouldn't. It would be an old game returning home to the Berkeley world, and I also used to play it a lot on the HP-2000. The 'ol HP 2000 access, now that brings back memories... Did you know I once wrote an entire multi-user BBS (emeryville's HP-BBS) in HP basic? But I digress.. :) - Jordan > but tracking them down is close to impossible since ucbvax no longer > exists. If nobody knows different, I would like to clean it up (fairly > easy since it's already in C) and commit it in. > > I've included the docs below. > > -Matt > > > > > Originally written (in HP-2000 BASIC) by > William K. Char, Perry Lee, and Dan Gee > > Rewritten in C by > Dave Pare (sdcsvax!sdamos!mr-frog) > and > Christopher Williams (ucbvax!ucbmerlin!williams) > > Corrected, Completed, and Enhanced by > Jeff Okamoto(ucbvax!okamoto) > Peter Yee (ucbvax!yee) > Matt Dillon (ucbvax!dillon) > Dave Sharnoff (ucbvax!ucbcory!muir) > and > Joel Duisman(ucbvax!duisman) > > >T R E K 7 3 > A Star Trek(R) Battle Simulation > > Trek73 is a computer-simulated battle based on the famous > Star Trek television series and the game Star Fleet Battles. Via > computer terminal, you can clash with enemy battle cruisers, such > as Klingon D-7's and Romulan Sparrowhawks, and use the same stra- > tegies that Captain Kirk has used. Like Kirk, you control a > Federation vessel similar to the Enterprise; a computer program > directs the enemy. Victory can fall into several categories: > > Decisive Victory -- You completely destroy or cripple the > attacking force. > > Tactical Victory -- You out-maneuver the enemy using high- > speed escapes, corbomite bluffs, `play dead' tactics; or the > enemy surrenders. > > Moral Victory -- You surrender or self-destruct and destroy > each other. > > All distances are measured in megameters, one million meters > (abbreviated `M'). Speed is expressed in `warp factors'. Each > warp factor equals 100M per second. All angles are expressed in > common degrees from zero to 360, measured counter-clockwise from > the x-axis, similar to reading a protractor. Only two dimensions > are used. > > Play is as follows: > > 1. You issue one of a number of commands (fire phasers, > change course, launch antimatter pods, surrender, etc.) by typing > the appropriate code number into the keyboard; > > 2. The enemy, under programmed instructions, issues a simi- > lar command; > > 3. Both your commands are executed (phasers are fired, > probes are launched, damages are assessed, courses changed, etc.) > while the vessels move through space; > > 4. Unless certain end-game conditions are met (you destroy > the enemy, the enemy destroys you, your out-maneuver the enemy, > you both destroy each other, or one party surrenders) the above > steps are repeated. > > __ > Star Trek is a registered trademark of Paramount > Pictures. > Although technically incorrect, it does save the player > from having to compute cube roots. > This saves the player from having to work out problems > in spherical geometry. > > > > >- 1 - > > > > > > STAR TREK > > > Appendix 1 displays certain weapon and shield angles. > > Appendix 2 depicts the Enterprise's power circuits. > > Appendix 3 lists certain weapon and vessel specifications. > > Appendix 4 lists initial deployment of resources. > > >CODE COMMAND > === > >1Fire Phasers >2Fire Photon Torpedos >3Lock Phasers Onto Target >4Lock Tubes Onto Target >5Manually Rotate Phasers >6Manually Rotate Tubes >7*Phaser Status >8*Tube Status >9Load/Unload Torpedo Tubes >10 Launch Antimatter Probe > >11 Probe Control (Detonate, Direct, Lock) >12 *Position Report >13 *Position Display >14 Pursue An Enemy Vessel >15 Run From An Enemy Vessel >16 Manually Change Course And Speed >17 *Damage Report >18 Scan Enemy (Damage Report Of Enemy) >19 Alter Power Distribution >
Re: trek73
a port? On Sat, 23 Oct 1999, Matthew Dillon wrote: > I found a copy of the C version of trek73 in my Amiga archives. This > is the trek73 originally written in HP-2000 Basic that was rewritten > by Dave Pare and Chris Williams in C and seriously enhanced by a bunch > of people including me in my early college years circa 1985. > > I don't think any of the authors would mind if it went into /usr/games, > but tracking them down is close to impossible since ucbvax no longer > exists. If nobody knows different, I would like to clean it up (fairly > easy since it's already in C) and commit it in. > > I've included the docs below. > > -Matt > > > > > Originally written (in HP-2000 BASIC) by > William K. Char, Perry Lee, and Dan Gee > > Rewritten in C by > Dave Pare (sdcsvax!sdamos!mr-frog) > and > Christopher Williams (ucbvax!ucbmerlin!williams) > > Corrected, Completed, and Enhanced by > Jeff Okamoto(ucbvax!okamoto) > Peter Yee (ucbvax!yee) > Matt Dillon (ucbvax!dillon) > Dave Sharnoff (ucbvax!ucbcory!muir) > and > Joel Duisman(ucbvax!duisman) > > >T R E K 7 3 > A Star Trek(R) Battle Simulation > > Trek73 is a computer-simulated battle based on the famous > Star Trek television series and the game Star Fleet Battles. Via > computer terminal, you can clash with enemy battle cruisers, such > as Klingon D-7's and Romulan Sparrowhawks, and use the same stra- > tegies that Captain Kirk has used. Like Kirk, you control a > Federation vessel similar to the Enterprise; a computer program > directs the enemy. Victory can fall into several categories: > > Decisive Victory -- You completely destroy or cripple the > attacking force. > > Tactical Victory -- You out-maneuver the enemy using high- > speed escapes, corbomite bluffs, `play dead' tactics; or the > enemy surrenders. > > Moral Victory -- You surrender or self-destruct and destroy > each other. > > All distances are measured in megameters, one million meters > (abbreviated `M'). Speed is expressed in `warp factors'. Each > warp factor equals 100M per second. All angles are expressed in > common degrees from zero to 360, measured counter-clockwise from > the x-axis, similar to reading a protractor. Only two dimensions > are used. > > Play is as follows: > > 1. You issue one of a number of commands (fire phasers, > change course, launch antimatter pods, surrender, etc.) by typing > the appropriate code number into the keyboard; > > 2. The enemy, under programmed instructions, issues a simi- > lar command; > > 3. Both your commands are executed (phasers are fired, > probes are launched, damages are assessed, courses changed, etc.) > while the vessels move through space; > > 4. Unless certain end-game conditions are met (you destroy > the enemy, the enemy destroys you, your out-maneuver the enemy, > you both destroy each other, or one party surrenders) the above > steps are repeated. > > __ > Star Trek is a registered trademark of Paramount > Pictures. > Although technically incorrect, it does save the player > from having to compute cube roots. > This saves the player from having to work out problems > in spherical geometry. > > > > >- 1 - > > > > > > STAR TREK > > > Appendix 1 displays certain weapon and shield angles. > > Appendix 2 depicts the Enterprise's power circuits. > > Appendix 3 lists certain weapon and vessel specifications. > > Appendix 4 lists initial deployment of resources. > > >CODE COMMAND > === > >1Fire Phasers >2Fire Photon Torpedos >3Lock Phasers Onto Target >4Lock Tubes Onto Target >5Manually Rotate Phasers >6Manually Rotate Tubes >7*Phaser Status >8*Tube Status >9Load/Unload Torpedo Tubes >10 Launch Antimatter Probe > >11 Probe Control (Detonate, Direct, Lock) >12 *Position Report >13 *Position Display >14 Pursue An Enemy Vessel >15 Run From An Enemy Vessel >16 Manually Change Course And Speed >17 *Damage Report >18 Scan Enemy (Damage Report Of Enemy) >
trek73
I found a copy of the C version of trek73 in my Amiga archives. This
is the trek73 originally written in HP-2000 Basic that was rewritten
by Dave Pare and Chris Williams in C and seriously enhanced by a bunch
of people including me in my early college years circa 1985.
I don't think any of the authors would mind if it went into /usr/games,
but tracking them down is close to impossible since ucbvax no longer
exists. If nobody knows different, I would like to clean it up (fairly
easy since it's already in C) and commit it in.
I've included the docs below.
-Matt
Originally written (in HP-2000 BASIC) by
William K. Char, Perry Lee, and Dan Gee
Rewritten in C by
Dave Pare (sdcsvax!sdamos!mr-frog)
and
Christopher Williams (ucbvax!ucbmerlin!williams)
Corrected, Completed, and Enhanced by
Jeff Okamoto(ucbvax!okamoto)
Peter Yee (ucbvax!yee)
Matt Dillon (ucbvax!dillon)
Dave Sharnoff (ucbvax!ucbcory!muir)
and
Joel Duisman(ucbvax!duisman)
T R E K 7 3
A Star Trek(R) Battle Simulation
Trek73 is a computer-simulated battle based on the famous
Star Trek television series and the game Star Fleet Battles. Via
computer terminal, you can clash with enemy battle cruisers, such
as Klingon D-7's and Romulan Sparrowhawks, and use the same stra-
tegies that Captain Kirk has used. Like Kirk, you control a
Federation vessel similar to the Enterprise; a computer program
directs the enemy. Victory can fall into several categories:
Decisive Victory -- You completely destroy or cripple the
attacking force.
Tactical Victory -- You out-maneuver the enemy using high-
speed escapes, corbomite bluffs, `play dead' tactics; or the
enemy surrenders.
Moral Victory -- You surrender or self-destruct and destroy
each other.
All distances are measured in megameters, one million meters
(abbreviated `M'). Speed is expressed in `warp factors'. Each
warp factor equals 100M per second. All angles are expressed in
common degrees from zero to 360, measured counter-clockwise from
the x-axis, similar to reading a protractor. Only two dimensions
are used.
Play is as follows:
1. You issue one of a number of commands (fire phasers,
change course, launch antimatter pods, surrender, etc.) by typing
the appropriate code number into the keyboard;
2. The enemy, under programmed instructions, issues a simi-
lar command;
3. Both your commands are executed (phasers are fired,
probes are launched, damages are assessed, courses changed, etc.)
while the vessels move through space;
4. Unless certain end-game conditions are met (you destroy
the enemy, the enemy destroys you, your out-maneuver the enemy,
you both destroy each other, or one party surrenders) the above
steps are repeated.
__
Star Trek is a registered trademark of Paramount
Pictures.
Although technically incorrect, it does save the player
from having to compute cube roots.
This saves the player from having to work out problems
in spherical geometry.
- 1 -
STAR TREK
Appendix 1 displays certain weapon and shield angles.
Appendix 2 depicts the Enterprise's power circuits.
Appendix 3 lists certain weapon and vessel specifications.
Appendix 4 lists initial deployment of resources.
CODE COMMAND
===
1Fire Phasers
2Fire Photon Torpedos
3Lock Phasers Onto Target
4Lock Tubes Onto Target
5Manually Rotate Phasers
6Manually Rotate Tubes
7*Phaser Status
8*Tube Status
9Load/Unload Torpedo Tubes
10 Launch Antimatter Probe
11 Probe Control (Detonate, Direct, Lock)
12 *Position Report
13 *Position Display
14 Pursue An Enemy Vessel
15 Run From An Enemy Vessel
16 Manually Change Course And Speed
17 *Damage Report
18 Scan Enemy (Damage Report Of Enemy)
19 Alter Power Distribution
20 Alter Torpedo And Phaser Firing Parameters
21 Jettison Engineering
22 Detonate Engineering
23 Attempt Defenseless Ruse
24 Attempt Corbomite Bluff(s)
25 Surrender
make release failure -- ed0 in PCCARD
Hi, Make release has been failing for awhile now and I just started to take a look at it. If I remove 'ed0' from i386/conf/PCCARD then the BOOTMFS kernel for pccard links correctly. With ed0 present, the following link errors occur: linking BOOTMFS if_ed_isa.o: In function `ed_isa_probe': if_ed_isa.o(.text+0x45): undefined reference to `ed_probe_WD80x3' if_ed_isa.o(.text+0x54): undefined reference to `ed_release_resources' if_ed_isa.o(.text+0x5a): undefined reference to `ed_probe_3Com' if_ed_isa.o(.text+0x69): undefined reference to `ed_release_resources' if_ed_isa.o(.text+0x6f): undefined reference to `ed_probe_Novell' if_ed_isa.o(.text+0x7e): undefined reference to `ed_release_resources' if_ed_isa.o(.text+0x84): undefined reference to `ed_probe_HP_pclanp' if_ed_isa.o(.text+0x93): undefined reference to `ed_release_resources' if_ed_isa.o(.text+0xa4): undefined reference to `ed_alloc_irq' if_ed_isa.o(.text+0xaf): undefined reference to `ed_release_resources' if_ed_isa.o: In function `ed_isa_attach': if_ed_isa.o(.text+0xef): undefined reference to `ed_alloc_port' if_ed_isa.o(.text+0x109): undefined reference to `ed_alloc_memory' if_ed_isa.o(.text+0x11a): undefined reference to `ed_alloc_irq' if_ed_isa.o(.text+0x127): undefined reference to `edintr' if_ed_isa.o(.text+0x152): undefined reference to `ed_attach' if_ed_isa.o(.text+0x15a): undefined reference to `ed_release_resources' *** Error code 1 The above functions are found in a few places: dev/ed/if_ed.c i386/isa/if_ed pc98/pc98/if_ed.c Ok, pc98 isn't used here... I'm not sure about the 1st two.. However, it appears that in dev/ed/if_ed.c, 'ed_probe_Novell' is defined and globally visible... but, in i386/isa/if_ed.c, 'ed_probe_Novell' is declared static... I don't know if this is the problem, but it's a difference... I'm continuing to look into this. If anyone has any comments, please let me know. Thanks, John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: NOTE NOTE NOTE:Re: does anybody but me (..vgrinds forever...)
:Not an executable... but I finally figured it out... Pipes possibly broken :as set up by csh- csh was an old (Oct 1) csh. Until I updated csh from the :current build tree, what actually was happening was vfontedpr was piping :to 'cat -' and this was hanging. Wierd city, but all better now I :believe... possibly related to the signal changes(?) : :-matt Weird. I did fix a few pipe bugs a number of weeks ago but this sounds like something different. -Matt Matthew Dillon <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
NOTE NOTE NOTE:Re: does anybody but me (..vgrinds forever...)
On Sat, 23 Oct 1999, Matthew Dillon wrote: > :It really is vgring hanging on a file: > : > :vgrind -f < /usr/src/share/doc/papers/kernmalloc/appendix.t > appendix.ms > : > :A plain vgrind -f on this file also hangs. Anyone have a clue on this? > : > :This happens for me on an alpha. > : > :-matt > > The vgrind command above does not hang on my PIII test box. It takes > about a second to run. I tried both an old binary and a new binary of > vgrind. Both worked. > > I recommend compiling vgrind up w/ full debugging and attaching a > debugger to it to see what is up. Not an executable... but I finally figured it out... Pipes possibly broken as set up by csh- csh was an old (Oct 1) csh. Until I updated csh from the current build tree, what actually was happening was vfontedpr was piping to 'cat -' and this was hanging. Wierd city, but all better now I believe... possibly related to the signal changes(?) -matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CVSUP ?
NFS on freefall. is hosed.. it needs to be rebooted but no root types are around.. now where are those script kiddies when you need them! On Sat, 23 Oct 1999, Mike Smith wrote: > > It's hosed. There are several emails in -hackers on this. so we're just > > waiting for a human to go fix it. > > Someone or something has broken cvsupd on freefall. Until jdp gets back > from FreeBSD Con (or someone gives him connectivity there, since we had > to pack up the terminal room), there's not going to be any more updates. > > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] > \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CVSUP ?
On Sat, Oct 23, 1999 at 01:44:28PM -0700, Mike Smith wrote: > > It's hosed. There are several emails in -hackers on this. so we're just > > waiting for a human to go fix it. > > Someone or something has broken cvsupd on freefall. Until jdp gets back > from FreeBSD Con (or someone gives him connectivity there, since we had > to pack up the terminal room), there's not going to be any more updates. After we did some more playing on freefall, it looks more like an NFS problem. "ls -l /" hangs on nfsrcv, just like cvsupd is doing right now. -- Mike Pritchard [EMAIL PROTECTED] or [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CVSUP ?
> It's hosed. There are several emails in -hackers on this. so we're just > waiting for a human to go fix it. Someone or something has broken cvsupd on freefall. Until jdp gets back from FreeBSD Con (or someone gives him connectivity there, since we had to pack up the terminal room), there's not going to be any more updates. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CVSUP ?
It's hosed. There are several emails in -hackers on this. so we're just waiting for a human to go fix it. On Sat, 23 Oct 1999, Mike Tancsa wrote: > > Is there something up with the cvsup servers or is my repository hosed? I > havent seen any updates in over a day. How do I go about checking if > something is messed up on my end ? > > ---Mike > ** > Mike Tancsa, Network Admin* [EMAIL PROTECTED] > Sentex Communications Corp, * http://www.sentex.net/mike > Cambridge, Ontario* 01.519.651.3400 > Canada* > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
CVSUP ?
Is there something up with the cvsup servers or is my repository hosed? I havent seen any updates in over a day. How do I go about checking if something is messed up on my end ? ---Mike ** Mike Tancsa, Network Admin* [EMAIL PROTECTED] Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario* 01.519.651.3400 Canada* To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sio working
In message <[EMAIL PROTECTED]> Will Andrews writes: : I will be your guinea pig, if you like. :-) Grab the current patches from http://www.freebsd.org/~imp/pccard-snap.patch but read my other posting about the warnings and such. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: does anybody but me have this problem (vgrind grinds forever...)
On Sat, 23 Oct 1999, Matthew Dillon wrote: > :It really is vgring hanging on a file: > : > :vgrind -f < /usr/src/share/doc/papers/kernmalloc/appendix.t > appendix.ms > : > :A plain vgrind -f on this file also hangs. Anyone have a clue on this? > : > :This happens for me on an alpha. > : > :-matt > > The vgrind command above does not hang on my PIII test box. It takes > about a second to run. I tried both an old binary and a new binary of > vgrind. Both worked. > > I recommend compiling vgrind up w/ full debugging and attaching a > debugger to it to see what is up. Sigh. Yes. > > test3:/tmp# vgrind -f < /usr/src/share/doc/papers/kernmalloc/appendix.t > appendix.ms > test3:/tmp# md5 /usr/src/share/doc/papers/kernmalloc/appendix.t > MD5 (/usr/src/share/doc/papers/kernmalloc/appendix.t) = >bd78df7b99cbaddae3cf952b6898fe1d > > -Matt > Matthew Dillon > <[EMAIL PROTECTED]> > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: sio working
On 23-Oct-99 Warner Losh wrote: > OK. I managed to get sio and ep working on the plane back from > FreeBSDCon'99. There are some problems with card eject at the moment, > but will be committing things to the tree shortly. I will be your guinea pig, if you like. :-) -- Will Andrews <[EMAIL PROTECTED]> GCS/E/S @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? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: does anybody but me have this problem (vgrind grinds forever...)
:It really is vgring hanging on a file: : :vgrind -f < /usr/src/share/doc/papers/kernmalloc/appendix.t > appendix.ms : :A plain vgrind -f on this file also hangs. Anyone have a clue on this? : :This happens for me on an alpha. : :-matt The vgrind command above does not hang on my PIII test box. It takes about a second to run. I tried both an old binary and a new binary of vgrind. Both worked. I recommend compiling vgrind up w/ full debugging and attaching a debugger to it to see what is up. test3:/tmp# vgrind -f < /usr/src/share/doc/papers/kernmalloc/appendix.t > appendix.ms test3:/tmp# md5 /usr/src/share/doc/papers/kernmalloc/appendix.t MD5 (/usr/src/share/doc/papers/kernmalloc/appendix.t) = bd78df7b99cbaddae3cf952b6898fe1d -Matt Matthew Dillon <[EMAIL PROTECTED]> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
does anybody but me have this problem (vgrind grinds forever...)
853 ?? Is 0:00.02 /bin/sh -c $HOME/bin/Nightly-FreeBSD-Build 855 ?? I 0:00.01 /bin/sh /home/mjacob/bin/Nightly-FreeBSD-Build 857 ?? I 0:00.02 sh ./DOMAKE buildworld 858 ?? I 0:00.03 make buildworld 861 ?? I 0:00.00 /bin/sh -ec cd /usr/src; make -f Makefile.inc0 -m /u 862 ?? I 0:00.03 make -f Makefile.inc0 -m /usr/src/share/mk buildworld 865 ?? I 0:00.00 /bin/sh -ec cd /usr/src; make -m /usr/src/share/mk - 866 ?? I 0:00.13 make -m /usr/src/share/mk -f Makefile.inc1 buildworld 1268 ?? I 0:00.00 /bin/sh -ec cd /usr/src; PATH=/usr/obj/usr/src/tmp/sb 1269 ?? I 0:00.08 /usr/obj/usr/src/tmp/usr/bin/make DESTDIR -f Makefile 1272 ?? I 0:00.01 /bin/sh -ec for entry in share/info include lib bin 21573 ?? I 0:00.03 /usr/obj/usr/src/tmp/usr/bin/make all SUBDIR_CHANGE D 21577 ?? I 0:00.01 /bin/sh -ec for entry in colldef dict doc examples in 21602 ?? I 0:00.03 /usr/obj/usr/src/tmp/usr/bin/make all SUBDIR_CHANGE D 21606 ?? I 0:00.01 /bin/sh -ec for entry in psd smm usd papers ; do (if 22824 ?? I 0:00.03 /usr/obj/usr/src/tmp/usr/bin/make all SUBDIR_CHANGE D 22828 ?? I 0:00.01 /bin/sh -ec for entry in beyond4.3 diskperf fsinterfa 22865 ?? I 0:00.04 /usr/obj/usr/src/tmp/usr/bin/make all SUBDIR_CHANGE D 22871 ?? I 0:00.00 /bin/sh -ec vgrind -f < /usr/src/share/doc/papers/ker 22872 ?? R 81:53.05 /bin/csh -f /usr/obj/usr/src/tmp/usr/bin/vgrind -f 22873 ?? Z 0:00.00 (vfontedpr) 22874 ?? Z 0:00.00 (cat) It really is vgring hanging on a file: vgrind -f < /usr/src/share/doc/papers/kernmalloc/appendix.t > appendix.ms A plain vgrind -f on this file also hangs. Anyone have a clue on this? This happens for me on an alpha. -matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall tweak
> Suppose I need to install on a bunch of machines. What I'd do, is > install once, get all the pieces/ports/customizations right and then > make a tarball of the system. To install the next machine, I'd use > sysinstall to partition and label the new machine and then just nfs > mount the machine with the tarball, unroll it and just fix rc.conf as > necessary. But when you go this way, there are no commands available > available at the holographic shell. Could this be fixed by letting > the commands be linked/copied into the chroot env? Um. But the chroot directory, e.g. where all your filesystems are mounted, is where you're also supposed to extract the bits or you'd be attempting to whap this NFS-mounted tarball onto your MFS. :) This question doesn't quite make sense to me, I'm afraid. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Are we going to fix -current's ed driver anytime soon?
>From current.freebsd.org's release build log: linking BOOTMFS if_ed_isa.o: In function `ed_isa_probe': if_ed_isa.o(.text+0x45): undefined reference to `ed_probe_WD80x3' if_ed_isa.o(.text+0x54): undefined reference to `ed_release_resources' if_ed_isa.o(.text+0x5a): undefined reference to `ed_probe_3Com' if_ed_isa.o(.text+0x69): undefined reference to `ed_release_resources' if_ed_isa.o(.text+0x6f): undefined reference to `ed_probe_Novell' if_ed_isa.o(.text+0x7e): undefined reference to `ed_release_resources' It's time to either fix this or back out the changes which broke it. If nobody finds the time to do the former in the next 48 hours, I'll do the latter myself. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata driver and mounting CDROMs, missing tape drives
Today Bryan Liesner wrote: > I've been having trouble mounting my ATAPI CDROM using the new ATA drivers > And here are my /dev entries: > > brw-r- 1 root operator 19, 0 Oct 22 01:34 /dev/acd0a > brw-r- 1 root operator 19, 2 Oct 22 01:34 /dev/acd0c > brw-r- 1 root operator 19, 8 Oct 22 01:34 /dev/acd1a > brw-r- 1 root operator 19, 10 Oct 22 01:34 /dev/acd1c > > They look like block devices to me! They sure are but the major number has changed, it should be 31. Make sure you've got an up to date MAKEDEV and remake the devices. -- Jack O'NeillSystems Administrator / Systems Analyst [EMAIL PROTECTED] Crystal Wind Communications, Inc. Finger [EMAIL PROTECTED] for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Massive pccard disruptions to continue
On Sat, 23 Oct 1999, Warner Losh wrote: > To summarize the changes, I killed the legacy PCCARD_MODULE macro and > all things associated with it. It is not longer emulated, even in the > slightest. Everything is done via newbus. This kills lots and lots > lines and makes it possible for newbus attachments, and only newbus > attachments. Also, pccardd no longer sets the unit number, so the > unit numbers have changed. The ep driver is hit by this since it > checks against NEP (this should be fixed, btw) in places. Send your changes to me. I've been rewriting if_ep. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata driver and mounting CDROMs, missing tape drives
Quoting Bryan Liesner ([EMAIL PROTECTED]): > I've been having trouble mounting my ATAPI CDROM using the new ATA drivers > When I do a: > > %mount /cdrom, the system complains: %mount_cd9660 /cdrom or %mount -t cd9660 /cdrom #:^) -- bush doctor harder than the rest ... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ata driver and mounting CDROMs, missing tape drives
I've been having trouble mounting my ATAPI CDROM using the new ATA drivers When I do a: %mount /cdrom, the system complains: cd9660: Block device required This is my fstab entry: /dev/acd0a /cdrom cd9660 ro,noauto 0 0 And here is the relevant part of my kernel config: controller ata0 device atadisk0 device atapicd0 device atapist0 And here are my /dev entries: brw-r- 1 root operator 19, 0 Oct 22 01:34 /dev/acd0a brw-r- 1 root operator 19, 2 Oct 22 01:34 /dev/acd0c brw-r- 1 root operator 19, 8 Oct 22 01:34 /dev/acd1a brw-r- 1 root operator 19, 10 Oct 22 01:34 /dev/acd1c They look like block devices to me! I have the CDROM configured as master, and a HP Travan 8G tape drive as slave. The dmesg shows only the CDROM, and the kernel doesn't see the tape drive at all, although the dmesg says there are two devices on the channel. Here is the last dmesg: 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: Fri Oct 22 00:01:27 EDT 1999 [EMAIL PROTECTED]:/usr/src/sys/compile/GRAVY Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 249414302 Hz CPU: Cyrix 6x86MX (249.41-MHz 686-class CPU) Origin = "CyrixInstead" Id = 0x601 Stepping = 1 DIR=0x1353 Features=0x80a135 real memory = 134217728 (131072K bytes) avail memory = 127672320 (124680K bytes) Preloaded elf kernel "kernel" at 0xc0274000. Preloaded elf module "linux.ko" at 0xc027409c. Preloaded elf module "warp_saver.ko" at 0xc027413c. npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 2.0 on pci0 isa0: on isab0 ata-pci0: irq 11 at device 5.0 on pci0 ata-pci0: Busmastering DMA supported ata2 at 0xeff0 irq 11 on ata-pci0 vga-pci0: irq 0 at device 6.0 on pci0 ata-pci1: irq 0 at device 11.0 on pci0 ata-pci1: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci1 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 pcm0: at irq 5 drq 1 flags 0x15 on isa0 vga0: at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0 at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port 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 sio2: at port 0x3e8-0x3ef irq 10 on isa0 sio2: type 16550A ad0: ATA-4 disk at ata2 as master ad0: 8693MB (17803440 sectors), 17662 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 31 depth queue, UDMA33 Creating DISK ad0 Creating DISK wd0 ad1: ATA-? disk at ata2 as slave ad1: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 0 depth queue, DMA Creating DISK ad1 Creating DISK wd1 ata0: Aladdin: two atapi devices on this channel, DMA disabled atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=00 acd0: CDROM drive at ata0 as master acd0: read 2062KB/s (6875KB/s), 128KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked changing root device to wd0s1a WARNING: driver snd should register devices with make_dev() (dev_t = "#snd/4") To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
