Re: Suspend modeX
On Tue, 29 Jun 1999, Alex Zepeda wrote: > Well, pushing <4s on the power button will turn the computer off (in fact > it's more of a "hard" power off IIRC). Depends on the BIOS. It is often settable. David, who finds most ATX stuff annoying because it hasn't got a 25 pin serial port. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: this of interest to anyone?
On Thu, 1 Jul 1999, Matthew Jacob wrote: > > panic: lockmgr: pid 3344, not exclusive lock holder 3341 unlocking > It might be if you supplied some additional information, like what sources your kernel was built from, as a minimum. UP or SMP? What was the box doing when it paniced? If you have a dump, can you provide a stack trace? Anything else useful. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: loads of SetAttrs in cvsup of cvs repo
On Sun, 4 Jul 1999, Amancio Hasty wrote: > > Curious why are you cvsupping every couple of minutes ? I think you have a language problem here. I think he meant it normally takes a couple of minutes, not that he cvsups every couple of minutes. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: is dumpon/savecore broken?
On Tue, 20 Jul 1999, Matthew Dillon wrote: > > * make sure your swap partition is large enough to hold the crash > dump. If you have 256MB of ram, your swap partition must be > at least 256MB in size. Is there any reason that savecore(8) can't write compressed crashdumps? (Other than no one haveing ever written the the code, of course.) In other words, if I wrote this would it get committed? David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: is dumpon/savecore broken?
On Tue, 20 Jul 1999, Matthew Dillon wrote: > > A crash dump would have to uncopmressed to gdb it. If you have > sufficient space to hold a crash dump, just point /var/crash at that > space. If you compress it right off the bat then someone is going to > have to uncompress it to look at it. savecore saving compressed crash dumps is handy on production machines with lots of memory. I run a bunch of HP/UX boxes that don't have 4 gigs in /var/crash, because they never crash, except of course when they do. It is very useful to be able to save the dump, even if I have to analyze it somewhere else. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: softdep_flushfiles: looping
On Fri, 30 Jul 1999, Daniel C. Sobral wrote: > Peter Holm wrote: > > > > Kirk seems to be out of touch :-), so I created PR kern/12869. > > I seem to recall a message from him last week saying he was going on > a six weeks vacation. Well, he *did* said he was going on vacation, > it's the "last week" and "six weeks" part I'm not 100% sure. Six weeks, and no computer more sophisticated than the SCUBA one, are what I remembered. Someone remind me what a vacation is again? David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sitting inside, looking out...
[moved to -chat] On Tue, 3 Aug 1999, Nik Clayton wrote: > > Hmm. "I submitted a PR to FreeBSD, and all I got was this lousy t-shirt." Wouldn't we rather have "I fixed a PR in FreeBSD..."? David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cd writer recommendation?
On Mon, 16 Aug 1999, Amancio Hasty wrote: > > Sorry about that . The emphasis is more on the hardware and second is the > software -- I usually get around problems with the software. I have a Yamaha 4416 (or something close to that) which has worked attached to every machine I have tried. (FreeBSD, Linux, ScumOS, HP/UX, spit NT) I would buy an external one, as they generate quite a lot of heat. > > Is there any support for IDE CD writers or are they not worth bothering with > on FreeBSD. There is support, but I don't think they are worth bothering with on any OS. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Softupdates reliability?
On Mon, 23 Aug 1999, Stephen McKay wrote: > I was extracting from the Exabyte to the DDRS disk while applying a CTM > update from that disk against one of the DCAS disks when it crashed. The > Exabyte went wonky (took about 6 goes to get the tape ejected) and the > rest of the disk system locked up. The SCSI adapter was so confused I > had to power down. > > When it recovered, there was an "UNEXPECTED SOFT UPDATE INCONSISTENCY" > which turned out to be a referenced but unallocated inode, and two zero size > directories. In all, a couple dozen files ended up in lost+found. I had this happen a couple times in 3.-2 stable. I tried to load a buggy kernel module, and hosed a cylinder group. As near as I could tell, the kernel module was writing to memory at random, and corrupted the buffer chain. I couldn't quite reproduce this enough to get a good handle on exactly what was going on, though. > If many other people have survived sudden power loss or similar no-sync type > crashes, I'll be happy to believe option 1 caused my problem. If not, then > perhaps softupdates still has incomplete handling of dependencies. Of course, > if it is option 1, I'm keen to know what's wrong with the current driver! I have survived a number of power loss crashes, with no problems. I tend to suspect the SCSI driver did something bad. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new man pages
On Tue, 4 Jan 2000, Soren Schmidt wrote: > It seems Marc Schneiders wrote: > > Where do I look for new man pages? I would like to read those for the > > new ata driver and for ntpd. They were not created during a build > > world some 5 days ago. And I cannot find them in > > /usr/src/share/man/man4, where I would expect man ata/ad in any case. > > There are no man pages for the ata driver (yet), for nptd I dunno... The new ntpd doesn't have any man pages. There are some html docs that come with the base distribution. I don't know if they are in the FreeBSD distribution, or where. Try looking in /usr/share. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: options COMPAT_LINUX makes kernel fail to compile
On Wed, 5 Jan 2000, Michael Lucas wrote: > Hello, > > Not that this is an actual fix to the problem, but: > > The COMPAT_LINUX kernel option isn't needed any more, per Marcel. (At > least, when I wrote an article on this, it wasn't.) You can probably > remove COMPAT_LINUX entirely. I use COMPAT_LINUX because I make kernels more frequently then I make world or modules. I get fewer panics that way. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot messages for pci devices...
On Wed, 19 Jan 2000, Andrzej Bialecki wrote: > > I did some hacks a while ago on a tool which could be called "devinfo". It > simply traversed the dev/bus tree and displayed tons of info about each > node. > > Perhaps something like that could be useful instead of full-blown FS? This is something like HP-UX's ioscan(1M)? This would be very handy, even it only gave info on the hardware the kernel knows about, as opposed to actually rescanning the busses. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm - stutters
On Sat, 29 Jan 2000, Nick Hibma wrote: > > > I too notice these problems of mpg123 skipping during disk activity or X > > > graphics ops but I have always had these problems, both with -STABLE and > > > -CURRENT. I notice this with xmms too. So this is nothing new. > > > > Isn't this simply a typical issue of IDE hardware? I too notice xmms > > skipping on heavy disk activity (typically the find command that runs from > > cron at 01:59). This happens even though I have two processors and a disk > > that can do 16 Mb/sec on UDMA66. One would expect such a system to be able > > to do a find and play mp3's simultaneously. > > Pressing Ctrl-Z repeats the same quarter second fragment forever. > And 'fg' doesn't always make it continue properly. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAIN
On Sat, 29 Jan 2000, Warner Losh wrote: > In message <[EMAIL PROTECTED]> Greg Lehey writes: > : I did a make world on my PDP-11 yesterday. It took less than a day. > : But that's 2.11BSD. > > Turns out that 12MB + 30MB of swap isn't enough to build world. I ran > out of swap and the machine rebooted (at least that's what I think > happened, since it silently rebooted). Are you using -pipe? That drastically increases memory requirements. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /usr/ports/ too big?
On Thu, 10 Feb 2000, Donn Miller wrote: > All these makefiles would go inside of audio. To do the building each > port, we can have the "work" be done inside the user's home > directory. This would eliminate the need to log in as root in order > to do the actual building. The benefits of having the port build It is already possible to do this. You simply need to set $WRKDIRPREFIX and $WRKDIR. > inside the user's home directory are: > > * the user could have the option of installing the port in his own > personal directory, in case the sysadmin doesn't see fit to put the > port on the system Already possible. Set $DESTDIR The stuff in /usr/ports/Mk is pretty impressive. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
buildworld failing
I just cvsuped an hour ago, my buildworld fails with this: ===> lib/libc "/usr/src/lib/libc/../libc/sys/Makefile.inc", line 9: Could not find /usr/src/lib/libc/../../sys/sys/syscall.mk make: fatal errors encountered -- cannot continue *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: buildworld failing
On Sun, 29 Aug 1999, David Scheidt wrote: > I just cvsuped an hour ago, my buildworld fails with this: I removed my /usr/src and checkedout of my local repository, and now the build gets past this. I don't do anything on this /usr/src/ except build from it, so I have no idea how it got corrupted. David > > ===> lib/libc > "/usr/src/lib/libc/../libc/sys/Makefile.inc", line 9: Could not find > /usr/src/lib/libc/../../sys/sys/syscall.mk > make: fatal errors encountered -- cannot continue > *** Error code 1 > > Stop in /usr/src/lib. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > > > > > > 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: HEADS UP! ATA driver (atapi DMA)..
On 31 Aug 1999, Kevin Street wrote: > Matthew Dillon <[EMAIL PROTECTED]> writes: > > I should have mentioned that ... it's a 32x cdrom. dmesg says it > claims to be able to do 5515 KB/sec. > > I've played around with using dd ... skip=n to reposition which part > of the cd I'm reading and I've seen some much better speeds on the > outer tracks (I think I now recall that cd's start numbering from the > inside tracks, don't they?). So you're probably right that it's just Almost all fast (>12X or so) CD-ROM drives are variable speed. You will see much greater performance from the outer edge as from the inside edge. You are correct that the begining of the CD is in the center. dd the whole disk and use iostat to see what your transfer rates are. They will go up as the disk reaches the end. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
another newpcm casualty
Yesterday's -current fails to find my soundcard. It's an Opti chipset thing that worked fine (for a $12 soundcard...) with the old driver. What is decent soundcard that works with the new driver?pnpinfo and dmesg snippet for the thing: Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID OPT0931 (0x3109143e), Serial Number 0x PnP Version 1.0, Vendor Version 0 Device Description: OPTi Audio 16 Logical Device ID: OPT 0x143e #0 Vendor register funcs 00 Device Description: AUX0 Logical Device ID: OPT9310 0x1093143e #1 Vendor register funcs 00 Device Description: OPTi Audio 16 TAG Start DF I/O Range 0x534 .. 0x608, alignment 0x4, len 0x4 [16-bit addr] I/O Range 0x380 .. 0x3f0, alignment 0x10, len 0xc [16-bit addr] I/O Range 0x220 .. 0x240, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0xe0c .. 0xffc, alignment 0x4, len 0x4 [16-bit addr] IRQ: 5 7 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Type F DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Type F TAG Start DF I/O Range 0x534 .. 0xff0, alignment 0x4, len 0x4 [16-bit addr] I/O Range 0x380 .. 0x3f0, alignment 0x10, len 0xc [16-bit addr] I/O Range 0x220 .. 0x240, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0xe0c .. 0xffc, alignment 0x4, len 0x4 [16-bit addr] IRQ: 5 7 9 10 11 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Type F DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Type F TAG Start DF I/O Range 0x534 .. 0xff0, alignment 0x4, len 0x4 [16-bit addr] I/O Range 0x380 .. 0x3f0, alignment 0x10, len 0xc [16-bit addr] I/O Range 0x220 .. 0x240, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0xe0c .. 0xffc, alignment 0x4, len 0x4 [16-bit addr] IRQ: 5 7 9 10 11 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Type F TAG End DF Logical Device ID: OPT0001 0x0100143e #2 Vendor register funcs 00 Device Description: Game Port I/O Range 0x200 .. 0x20f, alignment 0x1, len 0x1 [16-bit addr] Logical Device ID: OPT0002 0x0200143e #3 Vendor register funcs 00 Device Description: MPU401 I/O Range 0x300 .. 0x360, alignment 0x10, len 0x2 [16-bit addr] IRQ: 5 7 9 10 11 - only one type (true/edge) End Tag Successfully got 37 resources, 4 logical fdevs -- card select # 0x0001 CSN OPT0931 (0x3109143e), Serial Number 0x Logical device #0 IO: 0x 0x 0x 0x 0x 0x 0x 0x IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x01 Logical device #1 IO: 0x0380 0x0380 0x0380 0x0380 0x0380 0x0380 0x0380 0x0380 IRQ 5 0 DMA 0 1 IO range check 0x00 activate 0x01 Logical device #2 IO: 0x 0x 0x 0x 0x 0x 0x 0x IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x01 Logical device #3 IO: 0x 0x 0x 0x 0x 0x 0x 0x IRQ 10 0 DMA 4 4 IO range check 0x00 activate 0x01 dmesg of the probe: unknown0: on isa0 unknown1: on isa0 unknown2: on isa0 pcm0: at port 0x534-0x537,0x380-0x38b,0x220-0x22f,0xe0c-0xe0f irq 5 drq 0,1 on isa0 AD_WAIT_INIT FAILED 1002 0xff AD_WAIT_INIT FAILED 1002 0xff AD_WAIT_INIT FAILED 1002 0xff AD_WAIT_INIT FAILED 201 0xff AD_WAIT_INIT FAILED 1002 0xff AD_WAIT_INIT FAILED 201 0xff AD_WAIT_INIT FAILED 1002 0xff AD_WAIT_INIT FAILED 1002 0xff AD_WAIT_INIT FAILED 1002 0xff AD_WAIT_INIT FAILED 201 0xff AD_WAIT_INIT FAILED 1002 0xff AD_WAIT_INIT FAILED 201 0xff AD_WAIT_INIT FAILED 1002 0xff AD_WAIT_INIT FAILED 201 0xff AD_WAIT_INIT FAILED 1002 0xff AD_WAIT_INIT FAILED 201 0xff AD_WAIT_INIT FAILED 1002 0xff AD_WAIT_INIT FAILED 201 0xff AD_WAIT_INIT FAILED 1002 0xff AD_WAIT_INIT FAILED 201 0xff AD_WAIT_INIT FAILED 1002 0xff AD_WAIT_INIT FAILED 201 0xff AD_WAIT_INIT FAILED 1002 0xff AD_WAIT_INIT FAILED 201 0xff AD_WAIT_INIT FAILED 1002 0xff AD_WAIT_INIT FAILED 201 0xff AD_WAIT_INIT FAILED 1002 0xff AD_WAIT_INIT FAILED 201 0xff AD_WAIT_INIT FAILED 1002 0xff AD_WAIT_INIT FAILED 201 0xff AD_WAIT_INIT FAILED 1002 0xff AD_WAIT_INIT FAILED 201 0xff AD_WAIT_INIT FAILED 1002 0xff AD_WAIT_INIT FAILED 201 0xff AD_WAIT_INIT FAILED 1002 0xff AD_WAIT_INIT FAILED 201 0xff AD_WAIT_INIT FAILED 1002 0xff AD_WAIT_INIT FAILED 201 0xff AD_WAIT_INIT FAILED 1002 0xff AD_WAIT_INIT FAILED 201 0xff AD_WAIT_INIT FAILED 1002 0xff AD_WAIT_INIT FAILED 201 0xff AD_WAIT_INIT FAILED 1002 0xff AD_WAIT_INIT FAILED 201 0xff AD_WAIT_INIT FAILED 1002 0xff To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: another newpcm casualty
On Sun, 5 Sep 1999, Doug Rabson wrote: > On Sun, 5 Sep 1999, David Scheidt wrote: > > > Yesterday's -current fails to find my soundcard. It's an Opti chipset thing > > that worked fine (for a $12 soundcard...) with the old driver. What is > > decent soundcard that works with the new driver?pnpinfo and dmesg snippet > > for the thing: > > Try this patch: The card is now found, but when I try to use it, I get hundreds and hundreds of messages like Sep 5 19:09:33 tumbolia /kernel: AD_WAIT_INIT FAILED 201 0xff in /var/log/messages followed by Sep 5 19:09:33 tumbolia /kernel: mss: Auto calibration timed out(1). David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PNP problems
On Tue, 7 Sep 1999, Randy Bush wrote: > % xmix > Error opening mixer device /dev/mixer: Device not configured > > and similar whinging. xmix worked before the change. Did you remake your snd0 devices? David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: optional 'make release' speed-up patch
On Wed, 8 Sep 1999, Jordan K. Hubbard wrote: > > No offense, but this is really pretty ugly for something that I'd > anticipate to be a *major* edge case. I've been building releases for > years, for example, and I've yet to build one on a filesystem all by > itself. I usually just cast around for some space on an existing > (shared) fs and go to it, and I suspect that many others are the same > way. :-) Every make release I have done has been on its own filesystem. I do have two entire disks that don't do anything useful, so I might be a weirdo. The way disk prices are going though, I don't know that this will stay that way. [I haven't looked at the patches, and don't really feel qualified to pass judgement on them.] David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newpcm and Vibra16X
On Tue, 14 Sep 1999, Jordan K. Hubbard wrote: > > If this is a card you own, please just wrap it up and put it in the post > > to Cameron so that he has a chance to see what is going on. > > If only it were - it's the on-board sound on my Tyan Thunder 100 Mobo. > If you or anyone else knows of a particular card which uses this chip, > however, then I'd be happy to pick one up. I have a friend with one of these. I will find out what it is, and let you know. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Testers please!
On Sun, 19 Sep 1999, Poul-Henning Kamp wrote: > > If you have a PIIX4 based SMP system and run current, could you > please try out this patch: > > http://phk.freebsd.dk/piix/ > > I'm very interested in hearing if there are any measurable difference > apart from clock granularity being 3 times better. What sort of tests would you like done before and after? David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Linux X Server
On Tue, 12 Oct 1999, Bill A. K. wrote: > Hi, > Has anyone ever run a Linux X Server under FreeBSD/Linux Emulation? I'm > trying to run the Voodoo Banshee server from Creative Labs. The reason I'm Yup. I run a Voodoo Banshee, with the Creative Labs Linux X server. This is on -CURRENT just before newpcm and newpnp, and XFree 3.3.3. I don't remember having to do anything too wild to get it working. The one problem I do remember is that it doesn't play nicely with /dev/sysmouse. I have to use the real mouse device, and can't run moused. I don't have access to the machine at the moment, so I cannot tell you much more than that. I will take a look at the machine when I get home, and see what else I might have done. I don't run xdm, which might be an issue. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The eventual fate of BLOCK devices.
On Tue, 12 Oct 1999, Kirk McKusick wrote: > I would like to take a step back from the debate for a moment and > ask the bigger question: How many real-world applications actually > use the block device interface? I know of none whatsoever. All the > filesystem utilities go out of their way to avoid the block device > and use the raw interface. Does anyone on this list know of any > programs that need/want the block interface? If there are none, or It doesn't run on FreeBSD, but Sybase uses block devices for its dedicated disk devices. There may be other RDBMSes that do this. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can't make crashdump after panic
On Thu, 14 Oct 1999, Alex Le Heux wrote: > After configuring the system for making a crashdump, I get "panic: Timeout > table full" halfway through the dump. I had a panic tuesday, due to trying to load a broken module. I got the same panic: Timeout table full message. Interestingly, savecore seems to have recovered the full dump, at least by filesize. I didn't look at it since I knew what had caused the crash. My old kernel, from late august or early september (just pre NewPNP.) was unable to get savecore to save the core, though. > > This is on a stock PII system (weirdest hardware is a ZIP drive :), which > I'm trying to upgrade from a -current from Sep 17. (install new kernel > first, make world after, etc) > Sounds like your modules are out of date? That bit me. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: linux emulation broken..
On Thu, 14 Oct 1999, Marc van Woerkom wrote: > > (im)perfect. I was using the linux version of netscape, until > > recently when it began hanging for long periods of time during > > network or disk activity. > > Calling up linux-netscape-4.61 causes my system to freeze for a > couple of seconds, then it reboots. Is your linux emulation module out of date? I got bit by this the other day. It will causee quite a nice panic. Fixed that (options COMPAT_LINUX). David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: People getting automatically unsub'ed from -arch
On Thu, 14 Oct 1999, Ollivier Robert wrote: > According to Jonathan M. Bresler: > > thanks for the note on bouncefilter. > > i'll take a look at it. > > Someday, when you have 5 minutes free (aha!) have a look at Listar. It is a > small, fast and feature-full list manager written in C with automatic bounce > handling (among other things). It also builds almost out of the box on FreeBSD. You have to define BSDMOD, build it, install it, and add a listar user. I have a port that is nearly finished, pending acquistion of a round tuit. > > www.listar.org David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can't make crashdump after panic
On Fri, 15 Oct 1999, Khetan Gajjar wrote: > I've been getting these really odd panics as well (which I reported > but no-one seemed interested), with that error. I had only the panics caused by loading an out of date KLD. > I'm using the "experimental" ATA code though; are you using IDE > disks with the ATA or old WD driver, or are you using SCSI disks ? I have both IDE and SCSI disks, I am dumping to an ide disk controlled by the ATA driver. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can't make crashdump after panic
On Fri, 15 Oct 1999, Alfred Perlstein wrote: > > What is your memory size? what is your swap device size? 256MB. 512MB. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Can't make crashdump after panic
On Fri, 15 Oct 1999, Khetan Gajjar wrote: > > Looks like we have our problem; it's the ATA driver. I don't recall > seeing this error when using the wd driver. Yup. When I force a panic from DDB, I get panic: timeout table full and a message about "Dump already in progress, bailing". I haven't yet looked at them dump, to see whats in it. This doesn't happen with wd driver. Relevent bits of my dmesg: SMP: AP CPU #1 Launched! ad0: ATA-4 disk at ata0 as master ad0: 9787MB (20044080 sectors), 19885 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue, UDMA33 Creating DISK ad0 Creating DISK wd0 DANGER wait_intr active=ATA_IGNORE_INTR ad1: ATA-? disk at ata0 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 atapi: MODE_SENSE_BIG - UNIT ATTENTION skey=6 asc=29 ascq=00 error=04 acd0: CDROM drive at ata1 as master acd0: read 1033KB/s (1033KB/s), 256KB buffer, PIO acd0: supported read types: CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM unknown medium, unlocked Waiting 15 seconds for SCSI devices to settle To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /usr/share/calendar/calendar.freebsd ?
On Mon, 1 Nov 1999, Greg Lehey wrote: > I've never let my horses commit anything. Well, I won't admit it, > anyway. > > But I still think their birthdays belong in the list :-) > Can't remember 1 January? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cpu name
On Sat, 20 Nov 1999, Byung Yang wrote: > I lowered the optimization level from -O6 to -O and now it shows the cpu > name properly. I was using "-O6 -march=pentium" for the optimization flag > before, but would it affect the performance of the kernela lot if I lower > the optimization flag to -O? It makes it work properly, so yes it would. None of the kernel code is tested beyond -O. Much of it works, but if it doesn't you aren't going to get any support from anyone, except to tell you to turn the optimization down. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: Netscape and -current
On Mon, 22 Nov 1999, Brian Fundakowski Feldman wrote: > On Mon, 22 Nov 1999, Alexander N. Kabaev wrote: > > > The same here. CURRENT updated and built on Sunday causes native > > FreeBSD Netscape to lock up. Linux Netscape still works fine. > > > > Happens here, too. Can someone with a machine to spare try the following: > Working on this now. I presume I can just build a kernel, since the machine I am trying to upgrade form -STABLE to CURRENT does this. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Netscape and -current
On Tue, 23 Nov 1999, Peter Wemm wrote: > I'm pretty sure it's this commit to i386/machdep.c: Good call! A tree checked out with -D 1999-11-21 14:47 won't run netscape. A kernel built with the same sources, except for 1.376 of i386/machdep.c will. David Scheidt > === > revision 1.377 > date: 1999/11/21 14:46:43; author: pho; state: Exp; lines: +5 -5 > Moved useracc() to top of sigreturn as to avoid panic > caused by invalid arguments to rutine. > > Reviewed by:marcel, phk > === > > .. it's right in the area that's breaking netscape: > 484 communicator-4.7 PSIG SIGALRM caught handler=0x8fea40 mask=0x0 code=0x0 > 484 communicator-4.7 CALL sigreturn(0x50011ed4) > 484 communicator-4.7 RET sigreturn -1 errno 14 Bad address > > Cheers, > -Peter > -- > Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [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: buildworld across signal changes not quite right
On Tue, 23 Nov 1999, David O'Brien wrote: > > Thanks to Marcel's latest Makefile.inc1 changes (1.92), a -current > > buildworld running on an older -current system now progresses much > > further - in fact it now completes :-). > > Actually, I've been seeing just the opposite. > Before you could build a -CURRENT kernel and then the world. Now those > with worlds from this past summer can't build today's world regardless > of which of userland or kernel is built first. The upgrade from -STABLE is also broken because of this. The %expect stuff is blowing up. I haven't yet tried to see if building yacc and bison manually fixes things or not. I will tomorrow, when I have access to the box, assuming my workload doesn't try to kill me first. (I hadn't reported it, because I haven't had time to investigate properly. ) David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
World breakage in libpam?
Seeing this trying to build world, cvsup'd earlier today. cc -O -pipe -static -DSETPROCTITLE -DSKEY -DLOGIN_CAP -DVIRTUAL_HOSTING -Wall -I/usr/src/libexec/ftpd/../../contrib-crypto/telnet -DINTERNAL_LS -Dmain=ls_main -I/usr/src/libexec/ftpd/../../bin/ls -I/usr/obj/usr/src/tmp/usr/include -o ftpd ftpd.o ftpcmd.o logwtmp.o popen.o skey-stuff.o ls.o cmp.o print.o stat_flags.o util.o -lskey -lmd -lcrypt -lutil -lpam /usr/obj/usr/src/tmp/usr/lib/libpam.a(pam_static_modules.o): In function `_pam_get_static_sym': pam_static_modules.o(.text+0x299): undefined reference to `rad_create_request' pam_static_modules.o(.text+0x2af): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x2cc): undefined reference to `rad_put_string' pam_static_modules.o(.text+0x2e9): undefined reference to `rad_put_string' pam_static_modules.o(.text+0x319): undefined reference to `rad_put_string' pam_static_modules.o(.text+0x32d): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x34d): undefined reference to `rad_put_attr' pam_static_modules.o(.text+0x363): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x379): undefined reference to `rad_put_int' pam_static_modules.o(.text+0x394): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x3db): undefined reference to `rad_cvt_string' pam_static_modules.o(.text+0x40d): undefined reference to `rad_get_attr' pam_static_modules.o(.text+0x438): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x4b7): undefined reference to `rad_cvt_string' pam_static_modules.o(.text+0x4f2): undefined reference to `rad_get_attr' pam_static_modules.o(.text+0x50a): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x760): undefined reference to `rad_open' pam_static_modules.o(.text+0x789): undefined reference to `rad_config' pam_static_modules.o(.text+0x79d): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x7dd): undefined reference to `rad_send_request' pam_static_modules.o(.text+0x821): undefined reference to `rad_close' pam_static_modules.o(.text+0x881): undefined reference to `rad_close' pam_static_modules.o(.text+0x8ab): undefined reference to `rad_close' pam_static_modules.o(.text+0x8bc): undefined reference to `rad_strerror' pam_static_modules.o(.text+0x8d5): undefined reference to `rad_close' pam_static_modules.o(.text+0x8f4): undefined reference to `rad_close' pam_static_modules.o(.text+0xb07): undefined reference to `tac_strerror' pam_static_modules.o(.text+0xb23): undefined reference to `tac_close' pam_static_modules.o(.text+0xb4b): undefined reference to `tac_get_msg' pam_static_modules.o(.text+0xb5e): undefined reference to `tac_strerror' pam_static_modules.o(.text+0xb77): undefined reference to `tac_close' pam_static_modules.o(.text+0xb96): undefined reference to `tac_set_msg' pam_static_modules.o(.text+0xbb0): undefined reference to `tac_strerror' pam_static_modules.o(.text+0xbc9): undefined reference to `tac_close' pam_static_modules.o(.text+0xc60): undefined reference to `tac_open' pam_static_modules.o(.text+0xc90): undefined reference to `tac_config' pam_static_modules.o(.text+0xca7): undefined reference to `tac_strerror' pam_static_modules.o(.text+0xcc3): undefined reference to `tac_create_authen' pam_static_modules.o(.text+0xcda): undefined reference to `tac_strerror' pam_static_modules.o(.text+0xcf6): undefined reference to `tac_close' pam_static_modules.o(.text+0xd09): undefined reference to `tac_set_user' pam_static_modules.o(.text+0xd32): undefined reference to `tac_set_port' pam_static_modules.o(.text+0xd5b): undefined reference to `tac_set_rem_addr' pam_static_modules.o(.text+0xd84): undefined reference to `tac_send_authen' pam_static_modules.o(.text+0xd9b): undefined reference to `tac_strerror' pam_static_modules.o(.text+0xde8): undefined reference to `tac_close' pam_static_modules.o(.text+0xe48): undefined reference to `tac_close' pam_static_modules.o(.text+0xf52): undefined reference to `tac_close' pam_static_modules.o(.text+0xfbc): undefined reference to `tac_get_data' pam_static_modules.o(.text+0x101c): undefined reference to `tac_close' *** Error code 1 Stop in /usr/src/libexec/ftpd. *** Error code 1 Stop in /usr/src/libexec. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: semi-HEADS-UP (dumpon now wants raw disk device)
On Tue, 30 Nov 1999, Thomas Stromberg wrote: > " > > I see no needs of this change. I have -current dumpon/savecore work with > > old entrly like /dev/wd0... > > savecore understand both character and old block devices now. > > > > While I see your commit in cvsweb to savecore, I still run into this > (just cvsupp'd off of cvsup6.freebsd.org and rebuilt it): > > [root@karma] dumpon> grep \$FreeBSD dumpon.c > "$FreeBSD: src/sbin/dumpon/dumpon.c,v 1.8 1999/11/28 16:24:46 phk Exp > $"; > [root@karma] dumpon> dumpon /dev/wd0s1b > dumpon: /dev/wd0s1b: must specify a block device > [root@karma] dumpon> dumpon /dev/rwd0s1b > [root@karma] dumpon> > Do you have the correct devices in /dev? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
panic: vm_page_free: freeing wired page
I am having the following panic, with a -CURRENT system as fo CTM
cvs-cur.5868. I *think* the panic was induced by running mpg123 with a not
an mp3 file. I've had two (maybe three, something happened to the box over
night.) of these panics, but hte first was with no dump device configured.
I suspect I can reproduce it, since this one I did.
su-2.03# gdb -k
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd".
(kgdb) symbol-file kernel.debug
Reading symbols from kernel.debug...done.
(kgdb) exec-file /u/crash/kernel.0
(kgdb) core-file /u/crash/vmcore.0
IdlePTD 3047424
initial pcb at 2749e0
panicstr: vm_page_free: freeing wired page
panic messages:
---
panic: vm_page_free: freeing wired page
syncing disks... 6
done
dumping to dev #wd/0x20001, offset 262144
dump ata0: resetting devices .. done
128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110
109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88
87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63
62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38
37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13
12 11 10 9 8 7 6 5 4 3 2 1
---
#0 boot (howto=256) at ../../kern/kern_shutdown.c:273
273 dumppcb.pcb_cr3 = rcr3();
(kgdb) trace
trace command requires an argument
(kgdb) bt
#0 boot (howto=256) at ../../kern/kern_shutdown.c:273
#1 0xc0137115 in panic (fmt=0xc02405c0 "vm_page_free: freeing wired
page\n")
at ../../kern/kern_shutdown.c:523
#2 0xc01e1bf6 in vm_page_free_toq (m=0xc04e5a50) at ../../vm/vm_page.c:1102
#3 0xc01d9f59 in vm_fault (map=0xd8a18980, vaddr=672231424,
fault_type=1 '\001', fault_flags=0) at ../../vm/vm_page.h:504
#4 0xc021a46a in trap_pfault (frame=0xd9451fa8, usermode=1, eva=672231424)
at ../../i386/i386/trap.c:781
#5 0xc0219f7f in trap (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
tf_edi = 134661840, tf_esi = -1077946152, tf_ebp = 0,
tf_isp = -649781292, tf_ebx = -1077946153, tf_edx = -1077946796,
tf_ecx = -1077946796, tf_eax = 672231424, tf_trapno = 12, tf_err = 4,
tf_eip = 134592249, tf_cs = 31, tf_eflags = 66070, tf_esp =
-1077946820,
tf_ss = 47}) at ../../i386/i386/trap.c:348
(kgdb)
dmesg:
opyright (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 #6: Thu Dec 2 15:55:20 GMT 1999
[EMAIL PROTECTED]:/usr/src/sys/compile/RALLY3
Timecounter "i8254" frequency 1193182 Hz
CPU: Pentium II/Xeon/Celeron (348.49-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x651 Stepping = 1
Features=0x183f9ff
real memory = 134217728 (131072K bytes)
avail memory = 127102976 (124124K bytes)
Preloaded elf kernel "kernel" at 0xc02d6000.
Preloaded userconfig_script "/boot/kernel.conf" at 0xc02d609c.
Pentium Pro MTRR support enabled
npx0: on motherboard
npx0: INT 16 interface
pcib0: on motherboard
pci0: on pcib0
pcib1: at device 1.0 on pci0
pci1: on pcib1
vga-pci0: irq 11 at device 0.0 on pci1
fxp0: irq 10 at device 18.0 on
pci0
fxp0: Ethernet address 00:08:c7:89:57:ed
isab0: at device 20.0 on pci0
isa0: on isab0
ata-pci0: at device 20.1 on pci0
ata-pci0: Busmastering DMA supported
ata0 at 0x01f0 irq 14 on ata-pci0
ata1 at 0x0170 irq 15 on ata-pci0
pci0: UHCI USB controller (vendor=0x8086, dev=0x7112) at 20.2
chip1: at device 20.3 on pci0
isa0: unexpected tag 14
isa0: unexpected tag 14
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
psm0: irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
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 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
sio2: not probed (disabled)
sio3: not probed (disabled)
ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/8 bytes threshold
plip0: on ppbus 0
lpt0: on ppbus 0
lpt0: Interrupt-driven port
ppi0: on ppbus 0
unknown: can't assign resources
unknown: can't assign resources
unknown: can't assign resources
unknown: can't assign resources
unknown0: at port 0x268-0x26f on isa0
pcm0: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on
isa
0
unknown1: at iomem
0-0x9,0xe-0xf,0x10-0x7ff,0xfffc
-0x,0xc9000-0xcbfff on
Re: 3.3-stable -> 4.0-current problem...
On Tue, 7 Dec 1999, Darryl Okahata wrote: > Michael Chin-Yuan Wu <[EMAIL PROTECTED]> wrote: > > > Please try this tutorial when you move from -stable to -current > > > > www.external.org/freebsd/current.html > > I think you're missing the recent block device obsolescence > change. I had to build and install a -CURRENT yacc when I upgraded right before thanks giving. I haven't looked to see if this has been changed. (I think it was a Makefile.inc? problem.) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot stops after "Mounting root from ufs:/dev/ad0s2a"
On Wed, 8 Dec 1999, Greg Lehey wrote: > On Monday, 6 December 1999 at 15:07:21 -0500, Kelvin Farmer wrote: > > > > Problem: Computer _sometimes_ stops after the "Mounting root from > > ufs:/dev/ad0s2a" line. > > Running Current, built world yesterday. (Problem appeared fairly > > recently (as in ~2 weeks?, but didn't have ddb in previous kernel) > > > > dmesg: > > [...] > > ad0: ATA-3 disk at ata0 as master > > ad0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S > > ad0: 16 secs/int, 1 depth queue, DMA > > acd0: CDROM drive at ata1 as master > > acd0: read 1378KB/s (1378KB/s), 128KB buffer, PIO > > acd0: supported read types: CD-R, CD-DA > > acd0: Audio: play, 256 volume levels > > acd0: Mechanism: ejectable tray > > acd0: Medium: no/blank disc inside, unlocked > > Mounting root from ufs:/dev/ad0s2a > > It's difficult to mount your root if there's no disk in the drive. ad0 != acd0 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall: is it really at the end of its lifecycle?
On Wed, 15 Dec 1999, Brad Knowles wrote: > At 12:04 PM -0800 1999/12/15, Jordan K. Hubbard wrote: > > > OK, I hereby vote for "orca" as the code name. It's shorter than > > "leopard seal" :) > > Except that there is already a well-known tool by that name. See > <http://www.gps.caltech.edu/~blair/orca/>. > > -- Stoat then? http://home.capu.net/~kwelch/pp/predators/mammals.html David scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Init Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) )
On Wed, 15 Dec 1999, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Warner Losh writes: > > I would really like to see the devd functionality to live in init > and at the same time I wouldn't mind if init were taught to keep > important programs running, things like sshd, inetd, syslogd and > similar should be restarted if they die. > > No, I don't want sysV runlevels or the weird shit AIX has. I'm sure > a clean and sensible way can be found, if some mental energies are > poured into the problem. What's wrong with run with system V runlevels? Other than it's system V and everything AT^HUSL did is evil, of course. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Init Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) )
On Wed, 15 Dec 1999, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, Dav > id Scheidt writes: > >What's wrong with run with system V runlevels? Other than it's system V and > >everything AT^HUSL did is evil, of course. > > runlevels are a very oldfashioned way to think about things, I don't > want to have one big button which is called "NETWORKING ON/OFF". runlevels let you do more than just run gettys, control networking, and run /sbin/rc?.d scripts. We do. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with MAKEDEV.
On Sat, 15 Apr 2000, Peter Jeremy wrote: > On 2000-Apr-14 22:49:40 +1000, Steve Ames <[EMAIL PROTECTED]> wrote: > >That's always struck me a bit odd... I thought 'MAKEDEV std' made > >the generic set of devices and that 'MAKEDEV all' should make... well.. > >_ALL_. *shrug* > > What do you define as `all'? Say I have a big FTP server with 8 wide > SCSI controllers, each with 15 disks - that's da0..da119. I might > have a big shell (or similar) server that needs a few thousand PTYs. > I could have all sorts of other wierd hardware. "MAKEDEV all" has to > draw the line somewhere. Sure. What's the point of having both std and all, though? How much does it hurt to have a few extra device files kicking around? David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Archive pruning
On Tue, 25 Apr 2000, Matthew Hunt wrote: > Maintaining a CVS repository is necessary only if you are working > on the code, so your proposal would only affect devlopers, not Joe > User. Normal users do not maintain copies of the repository and do > not have a frequent need to examine history. There's always cvsweb > for occasional browsing. This isn't quite true. A repository is very handy if you have a number of different enviornments, two or three STABLEs with different date stamps, say. That's not ideal, but it can be much easier than regression testing a bunch of applications. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cc1 sig 11'ing recently?
On Wed, 26 Apr 2000, Matthew Jacob wrote: > > Umm- doubt it, but I'll check. This system has been fine for the last 18 > months and runs everything else just peachy. > Sudden SIGSEGVs are almost always the result of failed memory. The fact that the machine worked fine for 18 months doesn't mean anything. Replace the memory and your problems will likely go away. If they don't, it's likely that the problem is cooling, processor cache, or a bad motherboard memory bus. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Archive pruning
On Fri, 28 Apr 2000, David O'Brien wrote: > On Fri, Apr 28, 2000 at 01:17:56PM -0400, Brian Dean wrote: > > > I've often traced files back to the begining of FreeBSD time (and then > > > continued in the CSRG SCCS tree). > > > > I've wanted to do this on occasion. Where are these pre-FreeBSD > > history records available? > > Glad you asked. http://www.mckusick.com/csrg/index.html Not incidently, SCO have waived the $100 license application fee, which means that you can get your own official Ancient UNIX(TM) Source Code License for free. This roughly cuts in half the cost of the disks for someone not covered under a orginizaitonal souce code license. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Archive pruning
On Fri, 28 Apr 2000, Bush Doctor wrote: > Out of da blue David Scheidt aka ([EMAIL PROTECTED]) said: > > > > Not incidently, SCO have waived the $100 license application fee, which > > means that you can get your own official Ancient UNIX(TM) Source Code > > License for free. This roughly cuts in half the cost of the disks for > > someone not covered under a orginizaitonal souce code license. > Is there a new license form to sign or do we just fill out the current > form without sending the applicateion fee? > I don't know. SCO just made the announcement a week or two ago -- the same time they BSD licensed cscope -- and don't appear to have made changes to their web site yet. The press release is at http://www.sco.com/press/releases/2000/6927.html It might be worthwhile to attempt to contact the contact name on the release. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: db 1.85 --> 2.x or 3.x?
On Tue, 2 May 2000, Brad Knowles wrote: > At 1:16 PM +0200 2000/5/2, Poul-Henning Kamp wrote: > > > Sleepycats license is not FreeBSD compatible :-/ > > I don't understand. Reading > <http://www.sleepycat.com/license.net>, it seems to me that FreeBSD > meets all the necessary requirements. Can someone who understands > the details of the licensing issues either explain the situation to > me, or provide pointers to references that do? FreeBSD meets the license requirements. A non-FreeBSD developed application that used the DB interfaces might not. I don't think it would be a good idea for FreeBSD to do things that make it harder to produce commerical software. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Archive pruning
On Fri, 28 Apr 2000, David Scheidt wrote: > On Fri, 28 Apr 2000, Bush Doctor wrote: > > > Out of da blue David Scheidt aka ([EMAIL PROTECTED]) said: > > > > > > Not incidently, SCO have waived the $100 license application fee, which > > > means that you can get your own official Ancient UNIX(TM) Source Code > > > License for free. This roughly cuts in half the cost of the disks for > > > someone not covered under a orginizaitonal souce code license. > > Is there a new license form to sign or do we just fill out the current > > form without sending the applicateion fee? > > > > I don't know. SCO just made the announcement a week or two ago -- the same > time they BSD licensed cscope -- and don't appear to have made changes to > their web site yet. > > The press release is at http://www.sco.com/press/releases/2000/6927.html > It might be worthwhile to attempt to contact the contact name on the > release. SCO have updated their webpages, to show that they are now giving these licenses away. See http://www.sco.com/offers/ancient.html. They also have have the 5th, 6th and 7th edition UNIXs available, as well as system III and 32V available. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Anyone else seeing jumpy mice?
On Mon, 22 May 2000, Jordan K. Hubbard wrote: > Well, in my case it happens without any such things going on. More to > the point, it *never* works entirely right, from the moment I boot the > machine to the moment I turn it off. The mouse is always jumpy now, > and it's the same mouse I've been using for years so it's not a > physical mouse problem of any kind. > Unless your mouse died of old age. The PS/2 mouse I had been using for quite some time started to behave exactly like yours at some point last year. I avoided replacing it for a long time, since I couldn't find another mouse with a long enough cord. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: mktemp() patch
On Wed, 7 Jun 2000, Kris Kennaway wrote: :This patch was developed by Peter Jeremy and myself and increases the :number of possible temporary filenames which can be generated by the :mktemp() family, by more densely encoding the PID and using a larger set :of characters to randomly pad with. : :Instead of using only alphabetic characters, the patch uses the following :character set: : :0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz@#%^-_=+:,.~ ":" is path seperator in Apple's HFS filesystem. "@" is used as the line erase character in some shells. "#" is rubout in some shells. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Worst case swapping.
On Sun, 11 Jun 2000, Brian Hechinger wrote: :Kent Stewart drunkenly mumbled... :> :> Netscape reallys goes to pot in a hurry if you allow it to use more :> than 1-2MB of memory cache. A friend was seeing a terrible response :> and tracked it back to Netscape's memory cache. He had a lot of memory :> and started out with something on the order of 16MB. By the time he :> was satisfied he was allowing less than ~2MB of memory cache, which is :> all I had ever allowed it to use. : :i never screwed with the memory cache, but i've seen some pretty heavy memory :leakage with navigator. how long have you had netscape running? an hour, a Netscape has lots of memory leaks. the worst seem to be in Javascript, with java being a close second. I find I get the best performance and stability out of it if I leave those off, except when you need them. I also keep the memory cache size small, 2 or 3 megs; I leave the disk cache at a large size, since I am behind a slow link. The FreeBSD buffer caching does a good job of not throwing stuff away that I am actually using, so that works out quite well. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ACPI project progress report
On Mon, 19 Jun 2000, Brooks Davis wrote: :On Tue, Jun 20, 2000 at 10:49:24AM +1000, Andrew Reilly wrote: : :> Processes do still wind up in "sleep" state, completely paged :> out, don't they? : :Observationaly, no. Unless I actually manage to run my system low on :RAM, none of my swap is used even with ~5MB Eterm processes sitting :unused for days. I suppose if I let memory get tight, they might get :ditched in favor of disk cache, but I haven't seen that happen. Someone :with a better grasp of the VM could give a more preciese answer. I find lots my xterms getting swapped out on my office desktop. It's only (!) got 128MB of RAM, and I routinely have two or three dozen xterms running locally, plus a like number from remote machines, plus an instance of the X server and Netscape. It only takes a couple seconds to swap in one of the xterms when I start to use it again, and I often don't notice, because I have to move my hand from the mouse back to hte keyboard. I'm probably not a typical user, of course. David scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: /etc/rc.shutdown calls local scripts now
On Thu, 6 Jul 2000, Linh Pham wrote: :> :> Can we have little green "[ OK ]"s as well? :) :> :> j/k : :I hope you are joking... LOL... We don't want Linux emulation to go in :that direction. HP/UX does something like this. I find it rather useful, but that may be because I have boxes that take almost an hour to boot David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: etc/rc.d & things...
On Mon, 10 Jul 2000, Mike Meyer wrote: :Daniel C. Sobral writes: :> Mike Meyer wrote: :> The multiple levels are there to deal with changes in state. In BSD, for :> instance, we have single user/multi-user. A number of other variations :> can exist, both in heavy duty servers where you might want to bring :> certain services down for upgrade and then back up, and "desktop" :> machines, such as notebooks where you can be stand-alone, docked into :> different networks (eg. home/work). : :I'm familiar with why mutliple levels exist. I've never run into a :system that had a real use for more than three run levels - powered :off, maintenance, and up - though I've not dealt with Some of the machines I work on have three useful multi-user states. Runlevel 2 is plain-old multi-user mode, where filesystems are mounted, and the normal collection of services (mail, telnetd, ftpd, etc) are running. Run level 3 adds the DBMS, run level 4 adds the database dependent application. :P.S. - anyone else remember rc.single? Anyone care? Haven't seen one since Ultirx. shudder. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: **HEADS UP** if you used to cvsup the crypto repo from internat !
On Fri, 14 Jul 2000, Sheldon Hearn wrote: : : :On Thu, 13 Jul 2000 19:19:48 +0200, Mark Murray wrote: : :> > 2711: :> >If you used to get your crypto files from internat, AND you :> >used cvsup to get cvs' ,v files, then the latest changes :> >to the source collections will impact you. You will need to :> >remove all the crypto files and start over. : :Warner, Mark says that this applies if you used CTM to get cvs's ,v :files, not CTM. Also, he clarified the last sentence for me, by saying Should this read "used CTM ... not CVS" or "used CVS ... not CTM"? DAvid To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: randomdev entropy gathering is really weak
On Fri, 21 Jul 2000, Mark Murray wrote: : :Sure; we neet to be appropriately paranoid about that, but let's not :get ridiculous. The seed file could certainly use some decent protection, :but unfortunately, PC architectures don't come with SIMcards or the like. : Is it possible to combine the state of the disk based seed with some other source of real entropy? That would redudce the risk of having someone read your disks while the system is shutdown. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mouse frozen in X when returning from text console
On Wed, 26 Jul 2000, Jos Backus wrote: :[This is with yesterdays' -current and today's kernel, and Xfree86 4.0.1 using :the ati driver module.] : :Something I noticed today: switch to text console from X using C-A-F1; upon :return, the mouse cursor is frozen. moused appears to still work because I :can cut/paste text in the text console. Restarting moused doesn't help. : I don't have this problem, using XFree86 4.0.1, the ati module, /dev/psm0, and a current from early june. I do have a problem that some Solaris applications die horrible deaths trying to display on the FreeBSD box. That's probably neither FreeBSD nor XFree's fault though. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: When Good DIMMS go Bad (or how I fixed my sig11)
On Fri, 4 Aug 2000, Mike Muir wrote: :Stephen Hocking wrote: :> :> About a week ago, I complained of mysterious Sig 11s during a make world. :> After some experimentation, a PC100 DIMM was found to be better suited for a :> 66MHz memory bus in another machine, who obligingly donated a DIMM in return :> that actually works with a 100MHz bus. I think the trip from Australia and :> this Texas heat finally pushed the dodgy one over the edge. : :Have you tried any memory testing routines such as memtest86 ? Its the :only you write to a floppy and it runs before any bootstrap kicks in -- :independant of the OS -- and takes around 18 hours for a single pass. It :appears to be quite a comprehensive torture test. If so, how did that Software memory testers don't work. They may sometimes find problems, true, but if they don't, it doesn't mean the memory is good. Lots of failures are only triggered by certain access paterns, which is why it's so hard to convince people that their memory is bad. The only reliable way to test memory is with a hardware testor, or swapping known good memory in. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: When Good DIMMS go Bad (or how I fixed my sig11)
On Mon, 7 Aug 2000, Warner Losh wrote: :In message <[EMAIL PROTECTED]> David :Scheidt writes: :: convince people that their memory is bad. The only reliable way to test :: memory is with a hardware testor, or swapping known good memory in. : :Yes. while (1) do ; make world; done is a close second to a hardware :tester. Ah, that tells you have a problem. It unfortunatly, doesn't distinguish a bad memory module from a bad memory bus. One of my abits blew up a bit ago with SIGSEGVs, I swapped memory in and around till I got to the point that I realized that as long as I didn't populate the last DIMM slot, it worked fine. It's not long for this earth, that machine. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ftp and /etc/services...
On Wed, 16 Aug 2000, Donn Miller wrote: :This is on a recently-built -current box. When I try to move ftp from :port 21 to port 2121 in /etc/services, I get a "Connection :refused" message when I try to login to anonymous ftp sites. Should ftp :be this dependent on /etc/services? What if you _have_ no services :running, e.g. inetd & portmap? Returning ftp to port 21 in services fixes :this problem. I posted earlier about my problems with ftp recently. Yes. One would expect this. ftp(1) uses getservbyname(3), which looks at /etc/services to figure out what port to use. Since you've changed what getservbyname(3) returns to 2121, ftp(1) is trying to connect to the remote machine on port 2121. It's really quite unlikely they are running an ftp daemon there, so your connection is refused. This has absolutely nothing to do with what services your box runs, if inetd or portmap is running, or the phase of the moon. David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Boot hang with pcm
Current as of yesterday afternoon hangs trying to boot on my box with an OPTi931 soundcard installed. It prints the probe, and then hangs. With boot -v, the messages are pcm0: at port 0x5 34-0x537,0x380-0x38b,0x220-0x22f,0xe0c-0xe0f irq 5 drq 0,1 on isa0 mss_init: opti_offset=2 Yanking the card, or removing the driver from the kernel config allows the machine to boot fine. Unfortunatly, I just upgraded from a September 2000 vintage -current, so I don't know when this broke. David -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: background fsck
On Thu, 17 May 2001, David Wolfskill wrote: :>From: John Baldwin <[EMAIL PROTECTED]> : :>Hmm, that's odd, I did have soft updates on on /usr and /var before the crash. :>It seems to be off now. :( : :That also happened to me. I thought it odd at the time, but forgot to :mention it At least I have some reason to believe I was unlikely to :have been hallucinating about that Does tunefs update the alternate superblocks when it enables soft updates? It doesn't look it does, but I might be missing something. -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: background fsck
On Thu, 17 May 2001, David Wolfskill wrote: :(I see it does want the file system clean when soft updates is enabled, :but doesn't check for that for a disable request.) : Right. fsck(8) can make assumptions about the state of the filesystem if it knows that softupdates were in use. (There's a smaller set of possible inconsistancies, but I don't remember what they are.) It's safe for fsck to assume that the filesystem could be in worse shape than it actually is, but not safe to assume it's cleaner. David -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Unrecognised CBCP packet [strange problems with ppp(8)]
On Mon, 28 May 2001, Maxim Sobolev wrote: :Hi, : :I'm having strange problems with one of local dial-up providers: without :any visible reasons from time to time I can't establish PPP connection :during 20-30 minutes. Shortly after going into `Network' mode ppp(8) :complains about `Unrecognised CBCP packet' and drops down line. :Restarting ppp/machine/modem etc. doesn't help and provider's technical :people have no idea what could be wrong. Attached please find piece of :log, please let me know if any additional information would be necessary. : I've seen this too. Not very often, not repeatably. I don't think I ever had a problem reconnecting, though. I'm pretty sure I saw this as long ago as 1999, as well. I no longer have a dialup, so I'm kind of fuzzy on details. -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: su broken?
On Sun, 24 Jun 2001, Bob Bishop wrote: :Hi, : :su appears to be asking for a password when invoked by root, eg: : :# su bin -c "pwd" :Password: : :Broken, surely? What /etc/pam.conf do you have? I had this problem after my last world update until I mergemastered. -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: softupdates on /
On Thu, 5 Jul 2001, Dan Nelson wrote: :In the last episode (Jul 05), Benjamin P. Grubin said: :> As of a month ago or so, there was some discussion that concluded it :> was unsafe to enable softupdates on a root partition. Is it safe to :> go back in the water there, now? : :The 2 drawbacks with SU are : :1 - You can't immediately reuse the space occupied by a file you just :deleted; this may bite you if you do an installworld and don't have :20MB free on /. when it comes to installing /sbin, you need 18MB :for the new binaries, but you can't reuse the 18MB for the :just-deleted binaries. I've dodged that problem by SIGSTOPing installworld a couple times during the /sbin install, waiting for softupdates to catchup, and then SIGCONTing it. That's a pain; it's ugly, but it does work. Easier than a reboot, sometimes. -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
SMP panic at boot
My SMP box, running current from about 24 hours ago, panics on a cold boot,
but only if I don't touch a key. If I use the keyboard to do anything,
whether to skip the loader twiddler, or to skip the BIOS disk probing, or
just to bang my head against it, it boots fine. It will reboot fine once
it's booted.
What I get on the screen: (transcribed by hand, typos mine)
SMP: AP CPU #1 launched!
kernel trap 12 with interrupts disabled
panic: mutex sched lock recursed at /usr/src/sys/kern/kern/sync.c:807
cpuid =1; lapic.id =0100
Debugger("panic")
And then it hangs, failing to go into ddb.
Everytime, as long as I don't touch the keyboard.
--
[EMAIL PROTECTED]
Bipedalism is only a fad.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: -current lockups
On Wed, 1 Aug 2001, Sheldon Hearn wrote: : : :On Tue, 31 Jul 2001 12:06:49 -1000, Vincent Poy wrote: : :> Yeah, that's the weird part... I thought adding a DDB_UNATTENDED :> as a option would atleast make it reboot or something... : :For the record, DDB_UNATTENDED is mostly pointless. It just sets the :default value of debug.debugger_on_panic, which you can just as well set :in /etc/sysctl.conf. Unless, of course, you're seeing a panic in the :startup process. But then do you really want an indefinite panic cycle? ::-) Well, my current startup panic only happens at cold boot. After it panics the first time, it boots fine. If DDB_UNATTENED isn't set, it hangs trying to enter DDB. -- [EMAIL PROTECTED] Bipedalism is only a fad. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: disk quota overriding
On Wed, 17 Mar 1999, Jon Hamilton wrote: :Under HP-UX 9.x, the behavior you describe was the default, and it :was changable by altering a kernel config parameter and relinking the :kernel. The same tunable is available under 10.x, but I'm less certain :what the default behavior is there. Whether quotas are enabled or not :does not affect the behavior, only the kernel tunable parameter. This is still the default in 10.20. At least, all of the machines around here are that way. It has some uses on test and lab type machines, as it makes some tasks not have to involve root. As default behavior for a production machine, it is damn silly. David Scheidt : To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
moused broken?
My -CURRENT box is having problems with the mouse pointer freezing. Killing moused and restarting it seems to solve the problem, until it happens again, of course. It seems to happen after about 8 or nine hours of use. This hadn't been a problem with the previous -CURRENT, which was a month or so old. I am now running -CURRENT as of cvs-cur-5352, which is from sunday 23 May. I haven't seen anything in the commit logs that would indicate anything has changed that would break this. If it happens again, I shall see if I can get a better look at what happens. David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: moused broken?
On Thu, 27 May 1999, Kazutaka YOKOTA wrote: > It is a PS/2 mouse or a serial mouse? What model is it? > Sorry. It is a three button PS/2 mouse, an AT&T 320. I think it is really a Logitech mouse in Deathstar clothing. From dmesg: May 24 13:59:31 rally3 /kernel: psm0: irq 12 on atkbdc0 May 24 13:59:31 rally3 /kernel: psm0: model Generic PS/2 mouse, device ID 0 I never had a problem with the mouse under 2.2.8, 3.x, or NT. (I really like these mice: 3m cords). I also found the following lines in syslog: May 25 15:33:34 rally3 /kernel: psmintr: out of sync (0080 != ). David To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: Announcing a new cvsup server - cvsup6.freebsd.org
On Sun, 30 May 1999, John Polstra wrote: > There were other objections which were serious to make me (hang on > a second -- where is that CVSupMeister cap ... ah, there we go, > it's in place now) decide not to do it. One objection was that a > mirror might have been network-isolated from the master server for an > extended period of time. In that case, you'd randomly get a _big_ > step backwards in time. > > John Can't the supfile be made to ignore updates into the past? David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: bsd.lib.mk "@"'s
On Mon, 7 Jun 1999, Chuck Robey wrote: > Why are many of the build lines in bsd.lib.mk hidden with leading @'s, > so that they don't display in the build? This is useless, it hides > things that go wrong, and hardly belongs here, it seems to me. > How often do your calls to ld, mv and rm fail? David To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: ENABLE_SERIAL_BREAK_KEY...or something?
On Thu, 10 Jun 1999, Don Read wrote: > > Are you guys serious about dropping the box by powering off the console ? > > Suns do this. They sense the terminal power off as a break. One previous ork place had a bunch of rack mounted suns, sharing a serial console via a switch box. There was a problem that sometimes switching from one machine to another would cause a break. Someone wired it slightly different, and included a push button on the switch box to send a break. David Scheidt To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
