Re: Repeatable kernel panic for 3.2-RELEASE NFS server
On Fri, 21 May 1999, Matthew Dillon wrote: : entirely contained within the current stack trace. :All my kernels are now DDB kernels :) But since I do almost all of :my work remotely they are DDB_UNATTENDED, and the machine I am panic-ing :is not on the serial console server (sorry). I do have another question :about DDB, I unstalled -STABLE as of today (from releng3.fre...) and I :compiled the kernel with DDB, and DDB_UNATTENDED per usual. Now when I :C-A-E to get into the debugger and type 'panic' it drops me at another :debugging prompt. If I type panic from that I get the real thing, any ideas? : :My next email will hopefully have the stack trace for this panic. :-- :David Cross | email: cro...@cs.rpi.edu Panic has a counter. The first time it is called it tries to drop into the debugger. The second time it is called it reboots the machine for real. When you control-alt-escape, you have not yet called panic for the first time, so when you panic manually from the DDB prompt it drops you into the debugger again. Second time's the charm! Since the debugger repeats the previous command if you just hit return, I've gotten used to simply typing 'panic returnreturnreturnreturn...' I use that too :-). For the alpha, I put in a 'halt' command (also linked to remote-gdb's kill operation) which drops the machine back to the firmware which is handy if you don't care about buffers not being synced. -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
[ALERT] a.out support is broken in 3.2-STABLE and 4.0-CURRENT
Environment --- - 3.2-STABLE (CD-ROM version or built without -DWANT_AOUT) - 4.0-CURRENT (built without -DWANT_AOUT) Problem --- Fact: ld.so (rtld-aout) is built as part of ``legacy-build'' and then installed as part of ``legacy-install''. In order to build it, one needs to pass -DWANT_AOUT to the ``make world'' process. This will build a.out libraries and legacy boot as well. Fact: compatXX distributions depend on ld.so. Problem: Releases are built (see src/release/Makefile) by calling the ``make world'' without -DWANT_AOUT, thus making compatXX distributions useless. Possible Solutions -- 1. Add -DWANT_AOUT to src/release/Makefile. But in this case release will also contain (besides ld.so) a lot of unnecessary items: legacy boot files and a.out versions of current libraries. 2. Make -DWANT_AOUT build only the basic a.out support (ld.so) for binary compatibility with earlier releases and pass -DWANT_AOUT in src/release/Makefile when calling ``make world''. The necessary libraries could then be built and installed by passing corresponding -DCOMPATxx options to ``make world'' process, or by selecting desired compatXX distributions, if installing from the release media (FTP, CDROM). 3. Totally remove a.out support and push ld.so into all compatXX distributions. By the way, this is promised in src/Makefile: # If -DWANT_AOUT is specified, a `make world' with OBJFORMAT=elf will # update the legacy support for aout. This includes all libraries, ld.so # and boot objects. This part of build should be regarded as # deprecated and you should _not_ expect to be able to do this past the ^^ # release of 3.1. You have exactly one major release to move entirely ^^ # to elf. References -- http://www.freebsd.org/cgi/query-pr.cgi?pr=11828 Cheers, -- Ruslan Ermilov Sysadmin and DBA of the r...@ucb.crimea.ua United Commercial Bank +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: [ALERT] a.out support is broken in 3.2-STABLE and 4.0-CURRENT
On Sat, May 22, 1999 at 03:57:01PM +0300, I wrote: Environment --- - 3.2-STABLE (CD-ROM version or built without -DWANT_AOUT) - 4.0-CURRENT (built without -DWANT_AOUT) [...] 3. Totally remove a.out support and push ld.so into all compatXX distributions. By the way, this is promised in src/Makefile: [...] Just noticed David's commits into HEAD... ;-) David, you have forgotten to put ld.so into compat22 And would it be possible to MFC this stuff and add an 3.2-ERRATA entry... Thanks, -- Ruslan Ermilov Sysadmin and DBA of the r...@ucb.crimea.ua United Commercial Bank +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Suggestion...
One other suggestion, while I'm at it. The dgb driver has been marked alpha quality for a LONG time. I've had a fax server running on a PC/Xe 8 port card (64k shared RAM) for well over a year on one of these cards - and have NEVER had a single problem with it. That server gets a LOT of extremely heavy use, and if there were driver problems I would have found them by now. I'd suggest that someone drop the alpha byline on that one - its definitely stable :-) I plan on doing some work on it and the dgm driver. They're almost the same and should be merged. They both violate style(9) in almost every way too :-[ I know of only one person with an Xem card (dgm driver), but he's promised to send me the specs by snail mail. Once I get them, I'll start the work. Let's leave the `alpha' there for a little longer :-) -- -- Karl Denninger (k...@denninger.net) Web: fathers.denninger.net I ain't even *authorized* to speak for anyone other than myself, so give up now on trying to associate my words with any particular organization. -- Brian br...@awfulhak.orgbr...@freebsd.org http://www.Awfulhak.org br...@openbsd.org Don't _EVER_ lose your sense of humour ! br...@uk.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Logging promiscuous mode disabled
Hi folks, Are there issues that make the following apparently innocuous change to the handling of turning off promiscuous mode a bad idea? It doesn't seem to me like it'd break anything, and I'd like to know for sure when it's turned off -- it'd mean I don't have to count up the number of promiscous mode enabled messages and make sure that that number matches the number of applications I've run and subsequently terminated. Thanks, Sheldon. Index: if.c === RCS file: /home/ncvs/src/sys/net/if.c,v retrieving revision 1.70 diff -u -d -r1.70 if.c --- if.c1999/04/28 11:37:32 1.70 +++ if.c1999/05/22 14:18:45 @@ -828,6 +828,8 @@ if (--ifp-if_pcount 0) return (0); ifp-if_flags = ~IFF_PROMISC; + log(LOG_INFO, %s%d: promiscuous mode disabled\n, + ifp-if_name, ifp-if_unit); } ifr.ifr_flags = ifp-if_flags; error = (*ifp-if_ioctl)(ifp, SIOCSIFFLAGS, (caddr_t)ifr); To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Suggestion...
On Sat, May 22, 1999 at 02:33:51PM +0100, Brian Somers wrote: One other suggestion, while I'm at it. The dgb driver has been marked alpha quality for a LONG time. I've had a fax server running on a PC/Xe 8 port card (64k shared RAM) for well over a year on one of these cards - and have NEVER had a single problem with it. That server gets a LOT of extremely heavy use, and if there were driver problems I would have found them by now. I'd suggest that someone drop the alpha byline on that one - its definitely stable :-) I plan on doing some work on it and the dgm driver. They're almost the same and should be merged. They both violate style(9) in almost every way too :-[ I know of only one person with an Xem card (dgm driver), but he's promised to send me the specs by snail mail. Once I get them, I'll start the work. Let's leave the `alpha' there for a little longer :-) What are you planning on doing with it? Other than DDB support I can't imagine what could be *added* to the driver; it is one of those just works things right now. -- -- Karl Denninger (k...@denninger.net) Web: fathers.denninger.net I ain't even *authorized* to speak for anyone other than myself, so give up now on trying to associate my words with any particular organization. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Suggestion...
On 22-May-99 Karl Denninger wrote: On Sat, May 22, 1999 at 02:33:51PM +0100, Brian Somers wrote: One other suggestion, while I'm at it. The dgb driver has been marked alpha quality for a LONG time. I've had a fax server running on a PC/Xe 8 port card (64k shared RAM) for well over a year on one of these cards - and have NEVER had a single problem with it. That server gets a LOT of extremely heavy use, and if there were driver problems I would have found them by now. I'd suggest that someone drop the alpha byline on that one - its definitely stable :-) I plan on doing some work on it and the dgm driver. They're almost the same and should be merged. They both violate style(9) in almost every way too :-[ I know of only one person with an Xem card (dgm driver), but he's promised to send me the specs by snail mail. Once I get them, I'll start the work. Let's leave the `alpha' there for a little longer :-) What are you planning on doing with it? Other than DDB support I can't imagine what could be *added* to the driver; it is one of those just works things right now. Why not merge the two into a *new* driver? Once it's running at an acceptable level, drop support for the two old drivers. That way if something breaks, the current users still have the one that works. Vince. -- == Vince Vielhaber -- KA8CSH email: v...@michvhf.com flame-mail: /dev/null # include std/disclaimers.h TEAM-OS2 Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com == To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
RE: Logging promiscuous mode disabled
On 22-May-99 Sheldon Hearn wrote: It doesn't seem to me like it'd break anything, and I'd like to know for sure when it's turned off -- it'd mean I don't have to count up the number of promiscous mode enabled messages and make sure that that number matches the number of applications I've run and subsequently terminated. Sounds like a good idea to me Sheldon... Would make intrusion detection easier, etc etc =) --- Jeroen Ruigrok van der Wervenasmodai(at)wxs.nl The FreeBSD Programmer's Documentation Project Network/Security Specialist http://home.wxs.nl/~asmodai *BSD: Accept no limitations... To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: [ALERT] a.out support is broken in 3.2-STABLE and 4.0-CURRENT
Just noticed David's commits into HEAD... ;-) David, you have forgotten to put ld.so into compat22 No I didn't (and I wish people would stop accusing me of forgetting stuff!). For some reason, I am now having problems with remove CVS commits. :-( -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: [ALERT] a.out support is broken in 3.2-STABLE and 4.0-CURRENT
Problem --- Fact: ld.so (rtld-aout) is built as part of ``legacy-build'' and then installed as part of ``legacy-install''. In order to build it, one needs to pass -DWANT_AOUT to the ``make world'' process. This will build a.out libraries and legacy boot as well. Ok, I'm going to blow up here... People PLEASE drop this topic. It is being addressed -- maybe not as fast as people like, but it is being addressed. I really, REALLY don't understand why all of a sudden this problem is comming up when the compat22 distribution was made a while ago. Also, I install the compat* distributions and forget about them. I've never had ld.so problems. I really don't understand why so many people want to reinstall the compatXX files with every ``make world''. But I guess we do support such functionality, so someone should use it. So are people deleting ld.so before evey ``make world''. I also never make the a.out libs. Remember any a.out libs made with WANT_AOUT will be 3.2 libs with the same functional contents as the ELF ones. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: [ALERT] a.out support is broken in 3.2-STABLE and 4.0-CURRENT
And would it be possible to MFC this stuff After it is tested in -CURRENT first. and add an 3.2-ERRATA entry... Why? The compat22 distribution on the FTP site has ld.so in it, as wil the CDROM. Did you install 3.2 on the very first day? -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Source code of SGI XFS
As Mike Smith wrote ... Pavel Narozhniy wrote: Does anybody heard about SGI releasing XFS source code? Yup, they're doing it. I would guess that FreeBSD would need a fairly thorough revamp of its handling of kernel memory allocation before XFS would be fully usable, though: XFS buffer management is pretty full-on. Read Irix has shitty block I/O support so XFS has to do it all itself. The filesystem maintains its own pool of kernel buffers separate from the VM page cache which it uses for aggregating I/O transfers (so that if, say, you make 5 separate out-of-order I/Os which just happen to blanket a contiguous region of a disk object, XFS will collapse them into a single I/O; We do this too; it's called I/O clustering, but it's done below the filesystem so that anyone and everyone can benefit from it. The most interesting thing of XFS is it's GRIO I'd say. | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: ifconfig: changing mac address
As sth...@nethelp.no wrote ... Things like DECnet set the MAC address. Don't ask me why though. Because there is a one to one correspondence between the DECnet (Phase IV) address and the MAC address. Ie. if you specify the DECnet address, you have also implicitly specified the MAC address. Ah, that rings a (faint) bell. I only remember because it bit a colleague of mine once. They had a machine sitting behind a bridge and assumed that would keep their traffic local. Did not work too well because the bridge had been programmed to block the default MAC address, and not the one that DECnet made out of it. | / o / / _ Arnhem, The Netherlands- Powered by FreeBSD - |/|/ / / /( (_) BulteWWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: RE: GPS receivers for xntpd (off-topic)
: [ gps talk ] :... I've been very impressed with the newer ( last 5 months ) Garmin handhelds. The older ones only had 8 channel receivers. The newer ones have 12 channel receivers sensitive enough that the units often work indoors. FWIW, the Garmin 12XL is a *very* nice unit. I've used it for almost 2 years now (work related), and have nothing but high-praise to speak about it. The Garmin 12 is also nice, but does not allow for an external antenna. (We use them for clock synchronization at a macro-level of +-1sec, which is adequate for our applications.) Nate To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: [ALERT] a.out support is broken in 3.2-STABLE and 4.0-CURRENT
On Sat, May 22, 1999 at 09:09:46AM -0700, David O'Brien wrote: Just noticed David's commits into HEAD... ;-) David, you have forgotten to put ld.so into compat22 No I didn't (and I wish people would stop accusing me of forgetting stuff!). For some reason, I am now having problems with remove CVS commits. :-( Sorry, I didn't know that. I just saw the following: obrien 1999/05/21 11:36:00 PDT Modified files: lib/compat/compat22 Makefile Log: Add usr/libexec/ld.so Revision ChangesPath 1.2 +4 -2 src/lib/compat/compat22/Makefile -- Ruslan Ermilov Sysadmin and DBA of the r...@ucb.crimea.ua United Commercial Bank +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: [ALERT] a.out support is broken in 3.2-STABLE and 4.0-CURRENT
On Sat, May 22, 1999 at 09:20:26AM -0700, David O'Brien wrote: And would it be possible to MFC this stuff After it is tested in -CURRENT first. and add an 3.2-ERRATA entry... Why? The compat22 distribution on the FTP site has ld.so in it, as wil the CDROM. Did you install 3.2 on the very first day? Sorry again. I built the release myself, and in my environment (3.2-STABLE, make release) compat22 distribution doesn't contain ld.so. -- Ruslan Ermilov Sysadmin and DBA of the r...@ucb.crimea.ua United Commercial Bank +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: GPS receivers for xntpd (off-topic)
Nate Williams wrote: : [ gps talk ] :... I've been very impressed with the newer ( last 5 months ) Garmin handhelds. The older ones only had 8 channel receivers. The newer ones have 12 channel receivers sensitive enough that the units often work indoors. FWIW, the Garmin 12XL is a *very* nice unit. I've used it for almost 2 years now (work related), and have nothing but high-praise to speak about it. The Garmin 12 is also nice, but does not allow for an external antenna. (We use them for clock synchronization at a macro-level of +-1sec, which is adequate for our applications.) My GPS-II is the Garmin 12 in a cooler package, with an external antenna. It's a great little unit, and acquires position quite quickly. The II Plus is still available in the same package for about $250, and is feature idential to the 12XL. Garmin can't be beat in GPS. -- Where am I, and what am I doing in this handbasket? Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr w...@softweyr.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
ISA LM78 driver help
Hello there... I have an application where I require access to an LM78 health monitor chip on a certain type of industrial PC motherboard we use. Unfortunately, the LM78 is tied to ISA and not I2C/SMBus. Can anyone recommend a good framework to start writing a driver for this beastie? I've never actually written a driver before (*gulp*), so please treat me gently ;-) In essense, the chip sits at 0x290 with an address line at 0x290+5 and a data line at 0x290+6. I'd be happy writing a program that merely peeks and pokes in that address area, rather than a fully-fledged driver... TIA. -marc Marc Nicholas netSTOR Technologies, Inc. http://www.netstor.com 1.877.464.4776 416.979.9000 fax: 416.979.8223 cell: 416.346.9255 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: ISA LM78 driver help
In message pine.bsf.4.05.9905221943010.13140-100...@medulla.hippocampus.net, Marc Nicholas wrote: Hello there... I have an application where I require access to an LM78 health monitor chip on a certain type of industrial PC motherboard we use. Unfortunately, the LM78 is tied to ISA and not I2C/SMBus. Can anyone recommend a good framework to start writing a driver for this beastie? I've never actually written a driver before (*gulp*), so please treat me gently ;-) In essense, the chip sits at 0x290 with an address line at 0x290+5 and a data line at 0x290+6. I'd be happy writing a program that merely peeks and pokes in that address area, rather than a fully-fledged driver... TIA. I have two imprementation about it. One is userland imprementation based on code by Shimizu-san. It is available at http://www.planet.sci.kobe-u.ac.jp/~takawata/smbus/examples/xmbmon104.new.tar.gz And I wrote experimental kernel driver for LM78. http://www.planet.sci.kobe-u.ac.jp/~takawata/smbus/sys/lm-dist.tar.gz Regards, Takanori Watanabe a href=http://www.planet.kobe-u.ac.jp/~takawata/key.html; Public Key/a Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: dlopen failure
In article 37458ff0.fc9b2...@cablenet.net,
Damian Hamill dam...@cablenet.net wrote:
I have found the problem and it is a problem with make. By chance I did
an ls -l of the directory and noticed the shared object was only 371
bytes and thought no that can't be right.
Thanks for letting us know. I'm glad it's solved now.
My makefile sez.
mysqlacc.so : mysqlacc.o
ld -Bshareable -o $@ $ -u _floor ../../lib/libV.a ... {other libs}
By the way, don't use ld -Bshareable to build shared libraries.
Use cc -shared. There are some special .o files from /usr/lib
that need to be linked in, and cc -shared will do that for you
automatically.
John
--
John Polstra j...@polstra.com
John D. Polstra Co., Inc.Seattle, Washington USA
Self-interest is the aphrodisiac of belief. -- James V. DeLong
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
IPv6 and -current?
Out of a perhaps morbid curiosity, I'm somewhat interested in setting up an IPv6 stack on my computer. From what I can tell there are two well supported stacks. Kame and Inria, and both support 2.2.8, Kame also supports 3.x. Has anyone tried to port either to -current? I tried playing around with the Kame release for 3.0, and it generated quite a few rejects... - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: ISA LM78 driver help
I have done simple drivers before. I would be interested in working with you on this (it would benefit me as well). If you couild provide a web site with more information that would help too. -- David Cross | email: cro...@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science| Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Need help recovering from major mistake
Hi, I just made a major mistake with my FreeBSD drive that I hope I can recover from. Not thinking too far ahead, I tried to install OS-BS on a dangerously dedicated FreeBSD drive. This had the unfortunate side effect of wiping out both the boot code and disklabel from the drive. I'd like to restore them, but I don't have a printout of what the disklabel used to be. Therein lies the challenge. Using my FreeBSD CD-ROMs, I've been able to go into fixit mode and mount the root filesystem of the drive, but I'm not sure where to go from there. How can I figure out what my old disklabel was? Is there some way I can search the raw disk for the locations of the file systems? Any help will be GREATLY appreciated. Please email me directly with your responses as I'm not subscribed to the FreeBSD mailing lists. See ya later, Craig -- Craig Struble (cstru...@vt.edu) Ph.D. Candidate, Virginia Tech http://www.acm.vt.edu/~cstruble/ cstru...@vt.edu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
