RE: more make release
On Wed, 29 Nov 2000, John Baldwin wrote: On 29-Nov-00 Gray, David W. wrote: Hmmm, I'm specifically talking about when you have MAKEOBJDIRPREFIX set to something other than /usr/obj - it *almost* works, but /bin/sh uses files generated on-the-fly that get put in the wrong places (in the chroot'ed hierarchy). (ONLY when building the crunches - makeworld runs fine.) I suppose its beating a dead horse (got around it with a symlink or two) but it niggles - but that whole environment is just too twisted to follow. :( Hmmm. I bet the MAKEOBJDIRPREFIX is getting propagated into the chroot and it is dying in there because of that. crunchgen doesn't understand MAKEOBJDIRPREFIX. It looks for objects in /usr/obj`/bin/pwd` unless `objdir' is specified. The specification for `objdir' is per-program so it would be inconvenient to set it. The crunch configuration files for releases never set it. Support for the src tree not being /usr/src also seems to be broken. There is a global setting `srcdirs' as well as a per-program setting `srcdir'. The crunch configuration files for releases use `srcdirs' with a hard-coded prefix of "/usr/src". Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [jhb@FreeBSD.org: RE: Panic in -current]
Bad callout handler: c_func = 0xc025ad3c, c_arg=0xc0338460, c_flags=7 First I tried a db x/i,10 0xc025ad3c scrn_timer: pushl %ebp [...] nm just confirmed this, so it definitely looks like scrn_timer is to blame here. Any other instructions? ;-) For the time being, vidcontrol -t off (seems to) keep the machine up. Bye, Andrea Weird, I don't see anything offhand that syscons is doing that would cause it to leak Giant. Hmm. Can you add a the same code before the mtx_enter() of Giant? (But after the mtx_exit() of callout_lock to be on the safe side). Also, add in a 'mtx_assert(Giant, MA_NOTOWNED);' in between teh splx() and splhigh() right below the "Give interrupts a chance" comment up about 15 lines or so. I used a slightly different printf and panic text in order to distinguish between the two. It's still panicing at the lower one, still pointing to scrn_timer. Andrea -- Andrea Campi mailto:[EMAIL PROTECTED] I.NET S.p.A. http://www.inet.it Direzione Tecnica - Gruppo Security Phone :+39.02.40906.1 v. Caldera, 21/d - I-20153 Milano, Italy Fax :+39.02.40906.303 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: your mail
On Wed, Nov 29, 2000 at 07:41:14PM -0600, Mike Meyer wrote: Hmm - what's the stupidity? I have a test machine running both -current and -stable Do you have the two FreeBSD installations on the same disk? If so, I'd love to hear how you did it. I spoke with others and they also had problems when trying it sysinstall. I finally did 1 normal install and then booted that and created the 2nd slice, lable, BSD partitions, etc.. by hand and then untared the 2nd installation bits. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: your mail
David O'Brien [EMAIL PROTECTED] types: On Wed, Nov 29, 2000 at 07:41:14PM -0600, Mike Meyer wrote: Hmm - what's the stupidity? I have a test machine running both -current and -stable Do you have the two FreeBSD installations on the same disk? If so, I'd love to hear how you did it. I spoke with others and they also had problems when trying it sysinstall. I finally did 1 normal install and then booted that and created the 2nd slice, lable, BSD partitions, etc.. by hand and then untared the 2nd installation bits. Yup, they're both on the same disk. At this point, I've done that two ways. First was with a system already running -current. I just used a 4.1-RELEASE CD and did a standard install from that - carefully ignoring the slice -current was on, except to mount it's swap instead of allocating one on the -RELEASE slice. Upgrading that to -stable went without a hitch. Later, I had a system running -stable, and wanted to create a -current slice on the same system. Like you, I used the running -stable to create, partition and label a second slice. I then nfs-mounted /usr/src and /usr/obj from a -current system onto the -stable system, and did a "make installworld DESTDIR=/new" from that /usr/src. Then a "make distribution" in /usr/src/etc with the appropriate DESTDIR to get those files installed. Finally tweak the new -current's config files from the running -stable system. I think I had more problems because of differences between the /etc/make.conf files on the -current NFS server and the -stable system than anything else. Again, I set things up with one swap partition shared between the two OSs. I've seen the claim that FreeBSD can swap to a Linux swap partition, but never tested it. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RFC: /dev/console - /var/log/messages idea/patch
On Sat, Nov 25, 2000 at 07:39:33AM -0800, Cy Schubert - ITSD Open Systems Group
scribbled:
| In message 1050.974925641@critter, Poul-Henning Kamp writes:
|
| The attached patch is a "proof-of-concept" on which I would like
| to get some comments:
|
| It bugs me big time that the output from /etc/rc and all other output
| to /dev/console is volatile and lost once it scrolls of your console.
|
| It's a no-brainer. Let's do it.
How about networked ddb/gdb over {ether,ppp,usb,firewire,IrDA}?
Firewire and IrDA are works in progress AFAIK, but certainly
ddb/gdb networked debugging is what all FreeBSD dream of, right? :)
The PPC port would greatly benefit from this, as newer Apple stations
do not even have a serial port.
Darwin seems to have networked debugging.
--
+--+
| [EMAIL PROTECTED] | [EMAIL PROTECTED] |
| http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. |
+--+
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: USB modem?
Mark Huizer [EMAIL PROTECTED] types: Does anyone here have experience on tryuing to add USB devices? I do. I have a USB modem here, (Siemens), that I would like to get to work under FreeBSD, but I can't even find the right tools to get vendor and product ID's to add to usbdevs :-( Try looking in dmesg - USB device that don't have known product and vendor ID's have theirs printed. Failing that, check the usbdevs(8) man page. The serious catch about USB modems is that they have to support the USB CDC spec. Not all of them do. If it does, the serial device will be umodem0 (1, 2, 3, ...), and you use it just like a tty line tied to an external modem. mike -- Mike Meyer http://www.mired.org/home/mwm/ Independent WWW/Unix/FreeBSD consultant,email for rates. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Syscons flag to turn off random_harvest in scmouse?
On Mon, 27 Nov 2000, Mark Murray wrote: I wasn't screaming for a backout, I asked for a way to turn off harvesting from the mouse code. You're the one that started in, I just responded in the same condescending manner you used with me. If I was condescending, then I apologise. I am somewhat frustrated, however, at the apparrent (general) lack of understanding that is going into this discussion. If I was to provide a hackaround for everything that I am working to fix, then that is _all_ I'd do, and undoing them afterwards would be a nightmare. I think this whole topic is another piece of evidence for the, "Not everyone should be running -current" case. All of the development plans for yarrow and its ancillary pieces have been discussed ad nauseum, and yet some people still refuse to even come within pissing distance of a clue. If the harvesting bothers you THAT much, submit patches or install 4.2. While I tend to be rather impatient regarding things like broken builds or prolonged instability on -current; things like this that are A) directly related to ongoing development, B) temporary, and C) improving, are part of the price. If it's too much of a price to pay, help fix it (the right way) or run another branch. Doug -- So what I want to know is, where does the RED brick road go? Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
environment variable for resolv.conf anyone?
Hi, I find myself connected to multiple networks and domains all the time, and was wondering if anyone has solved (without using a chroot environment) using a different resolv.conf for different shells? One solution I thought off was to change the resolver library to look for an environment variable and if that was set, to use the file it pointed to instead of being hardcoded to /etc/resolv.conf as it is today. Anyone have an opinion on the general usefulness of this idea, and whether it poses a security risk? Thanks, Lars To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: environment variable for resolv.conf anyone?
This is my only message in this thread, it's out of topic. On Thu, Nov 30, 2000 at 01:58:59PM -0600, Lars Fredriksen wrote: Hi, I find myself connected to multiple networks and domains all the time, and was wondering if anyone has solved (without using a chroot environment) using a different resolv.conf for different shells? Have you thought about running your own non-authoritative DNS? If you use djbdns, this gives you the added benefit of being able to easily specify which DNS is authoritative for special, local domains. In general, having your local, caching-only (in bind parlance) DNS gives you better security and flexibility, and it's very easy to maintain. All of my machines, clients and servers, run like that, and I never had any problem. Bye, Andrea -- Intel: where Quality is job number 0.9998782345! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: environment variable for resolv.conf anyone?
Hi, Yes I have thought of that. I ran into a few issues that I thought made the solution cumbersome. Perhaps you solved these in a way that makes them dissapear? 1) Need to always use fully qualified names (only a problem when there are duplicates) 2) Need to bounce named a lot to avoid having records for networks that are not currently connected to. (perhaps sufficient to edit search line in resolv.conf each time a network gets added/deleted.) 3) If the remote network consists of lots of subdomains the named config becomes rather large. Lars Andrea Campi wrote: This is my only message in this thread, it's out of topic. On Thu, Nov 30, 2000 at 01:58:59PM -0600, Lars Fredriksen wrote: Hi, I find myself connected to multiple networks and domains all the time, and was wondering if anyone has solved (without using a chroot environment) using a different resolv.conf for different shells? Have you thought about running your own non-authoritative DNS? If you use djbdns, this gives you the added benefit of being able to easily specify which DNS is authoritative for special, local domains. In general, having your local, caching-only (in bind parlance) DNS gives you better security and flexibility, and it's very easy to maintain. All of my machines, clients and servers, run like that, and I never had any problem. Bye, Andrea -- Intel: where Quality is job number 0.9998782345! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Weird ffs panic
I got this weird panic a few days ago on one of my SMP testboxes, but I don't
think it is SMPng related:
Fatal trap 12: page fault while in kernel mode
cpuid = 1; lapic.id = 0100
fault virtual address = 0x7c
fault code = supervisor read, page not present
...
current process = 7421 (make)
kernel: type 12 trap, code=0
Stopped at bread+0x29L testb $0x20,0x7c(%esi)
db trace
bread(c8a63d00,2,1000,0,c8b41bcc) at bread+0x29
ffs_blkatoff()
ufs_lookup()
ufs_vnoperate()
ufs_cache_lookup()
ufs_vnoperate()
lookup()
namei()
vn_open()
open()
syscall2()
Xint0x80_syscall()
Now, 0xc8b41bcc is the bpp argument, and from bread in vfs_bio.c:
int
bread(struct vnode * vp, daddr_t blkno, int size, struct ucred * cred,
struct buf ** bpp)
{
struct buf *bp;
bp = getblk(vp, blkno, size, 0, 0);
*bpp = bp;
/* if not found in cache, do some I/O */
if ((bp-b_flags B_CACHE) == 0) {
I'm fairly sure it is dying trying to do the deref of bp, so I figured bp was
NULL. Checking *bpp confirmed this:
db x/x 0xc8b41bcc
0xc8b41bcc: 0
This means that getblk() returned NULL. I've looked at getblk() and have no
idea why it would return NULL when passed in a timeout of 0. Any ideas? The
panic was during a buildworld -j 128 btw. Current being in the wonderful state
that it is, I don't think I can get a crashdump, so I'm leaving the machine up
at a ddb prompt if more info is needed.
--
John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: -current on ibm tp a20p?
In message [EMAIL PROTECTED] Archie Cobbs writes:
: One thing I noticed is that /etc/defaults/pccard.conf says:
: # Available memory slots
: memory 0xd4000 96k
: while /etc/rc.pccard says:
: case ${pccard_mem} in
: [Dd][Ee][Ff][Aa][Uu][Ll][Tt])
: pccardc pccardmem 0xd
: Seems like there are two settings for the same "default"..
: or am I confusing two different things?
You are confusing two different things. The pccardc pccardmem command
sets the memory that is used to map the CIS, while pccard.conf sets
memory to dole out to the cards inserted. Much like there's a
management IRQ and a card IRQ.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Lucent Orinoco Gold PCCard?
In message [EMAIL PROTECTED] Sascha Luck writes: : has anyone got the Lucent Orinoco Gold (11MBit/s) PC-Card working : with the wi driver in -CURRENT? Yes. I'm running one right now. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Lucent Orinoco Gold PCCard?
In message [EMAIL PROTECTED] John Baldwin writes: : I'm sending this e-mail over a WaveLAN Gold, and from my : understanding the Orinoco card is the same card with a different : name and a different sticker, so it should work fine. I'm doing the same thing. It is the same card with a different label. The newer firmware, however, sets the default channel differently than the older cards. Doesn't matter for infrastructure mode, but does for adhoc. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: your mail
In message [EMAIL PROTECTED] "David O'Brien" writes: : Except for stupidity in libdisk(I believe) and thus sysinstall, there is : no, none, zero reason why one cannot have two installations of FreeBSD in : two different slices on the same disk. I've done make buildworld/installworld of both -current and -stable onto one disk in the 3.x/4.0-current time frame. It took a lot of tweaking, but I was able to boot off either one. I think that booteasy didn't boot the second partition properly and I had to play loader games. Sadly, the disk that had this on it one day started thumping, turning it into a rather large paperweight... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: your mail
Warner Losh [EMAIL PROTECTED] types: In message [EMAIL PROTECTED] "David O'Brien" writes: : Except for stupidity in libdisk(I believe) and thus sysinstall, there is : no, none, zero reason why one cannot have two installations of FreeBSD in : two different slices on the same disk. I've done make buildworld/installworld of both -current and -stable onto one disk in the 3.x/4.0-current time frame. It took a lot of tweaking, but I was able to boot off either one. I think that booteasy didn't boot the second partition properly and I had to play loader games. Sadly, the disk that had this on it one day started thumping, turning it into a rather large paperweight... FWIW, my system running both -current and -stable off of one disk uses grub for booting, not booteasy. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: cvs commit: src/sys/sys mutex.h src/sys/kern kern_mutex.c
On 01-Dec-00 John Baldwin wrote: jhb 2000/11/30 16:11:00 PST Modified files: sys/sys mutex.h sys/kern kern_mutex.c Log: Split the WITNESS and MUTEX_DEBUG options apart so that WITNESS does not depend on MUTEX_DEBUG. The MUTEX_DEBUG option turns on extra assertions and checks to verify that mutexes themselves are implemented properly. The WITNESS option uses extra checks and diagnostics to verify that other code is using mutexes properly. Removing MUTEX_DEBUG and only using WITNESS provided a very noticable performance increase on the quad xeon I have here for testing for I/O bound operations. Before, trying to do a cvs update would end up with cvs having 7s of user time nad 9000s of system time, now it is back down to more sane boundaries. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
