doscmd broken on current?

1999-01-04 Thread John Hay
Is doscmd working for anyone on current? Here I just get: - angel:~ > doscmd -bx Illegal instruction (core dumped) angel:~ > gdb /usr/obj/usr/src/usr.bin/doscmd/doscmd doscmd.core GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General P

Re: show stopper for Gcc 2.95.2 conversion

1999-01-04 Thread Gary Jennejohn
Bruce Evans writes: >On Fri, 5 Nov 1999, David O'Brien wrote: > >> The current show stopper for switching over to GCC 2.95.2 is a problem >> compiling the `ahc' driver: >> >> cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs >> -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -

Re: ESS 1868 driver, again

1999-01-04 Thread Peter Wemm
"D. Rock" wrote: > I read the last mails regarding problems with their ESS 1868 boards. > Well, at least it is partially working for them. I didn't have any > luck with the driver for some time now. I couldn't get a single tone. > > With the old voxware driver, sound worked at least partially > (

Re: stuck with ~year old current

1999-01-04 Thread Lauri Laupmaa
On Fri, 5 Nov 1999, Michael Reifenberger wrote: > The flag is probably -fformat-extensions so eliminate it from > /usr/share/mk/bsd.kern.mk. > Then build linker/kernel/world. Thank you all who replied! The trick was to take new loader from running system, because it was impossible to build one

Re: Serious locking problem in CURRENT

1999-01-04 Thread David Malone
On Sat, Nov 06, 1999 at 12:50:16AM +0100, Ollivier Robert wrote: A child process seems to be able to let go of a parent's lock on 4.0 by closing a file discriptor, the same doesn't seem to be true on 3.3. For example, if you try to run two copies of the included program as on 3.3, you get a res

Java segfaulting

1999-01-04 Thread Patrick Hartling
I'm running -current as of 9:00 CDT October 30, and ever since I rebuilt, I have not been able to run any Java applications. All of them exit with the following error output: SIGSEGV 11* segmentation violation Full thread dump: Monitor Cache Dump: Registered Monitor Dump: Monitor IO lock

Re: Java segfaulting

1999-01-04 Thread Nate Williams
> I'm running -current as of 9:00 CDT October 30, and ever since I rebuilt, I > have not been able to run any Java applications. All of them exit with > the following error output: Running Java on -current is at best a hit-miss operation, simply because we were forced to hard-code in some linker

Re: -current panic on AHA

1999-01-04 Thread Warner Losh
In message <[EMAIL PROTECTED]> "Andrey A. Chernov" writes: : Very fresh -current always paniced after detecting SCSI devices on : aha0: AHA-1542CF FW Rev. B.0 (ID=45) SCSI Host Adapter, SCSI ID 7, 16 CCBs : page fault: supervisor, read page not present : Old kernel from Oct 8 works nicely : Sorry

gzip(1) hanging

1999-01-04 Thread Steve Price
Hi all, I've got a -current box freshly CVSup'd and built from last night that is exhibiting some rather bizarre behavior. I actually noticed the problem on my Alpha package building machine, but the same behavior exists on my i386 box. To see what I'm seeing (or maybe not :) all you have to do

Re: Wondering about cardbus support.

1999-01-04 Thread Warner Losh
In message <[EMAIL PROTECTED]> Frank Mayhar writes: : I have the misfortune to have a cardbus Ethernet card that came with my : Dell laptop. I was wondering how cardbus support was going, and if I could : help in any way. Here's the status of what's going on... I have started to port the newcon

Re: boot problems with todays kernel

1999-01-04 Thread Warner Losh
In message <[EMAIL PROTECTED]> Will Andrews writes: : Hmm.. ep0 on IRQ 3? It should be on IRQ 10. At least, that's what has : always worked : for me on previous -CURRENT code. Otherwise I get the same last 2 messages. I've always used 11. : Yep - this happens to me when i do a `ifconfig ep0`. Ka

Re: sio working

1999-01-04 Thread Warner Losh
In message <[EMAIL PROTECTED]> Greg Lehey writes: : Nov 5 17:15:19 mojave /kernel: sio1: configured irq 3 not in bitmap of probed irqs 0 Unless you are running pccardd, you won't see the pccard devices show up. The probe messages that I'm interested in would be the ones that say something about

Re: sio working

1999-01-04 Thread Warner Losh
In message <[EMAIL PROTECTED]> "D. Rock" writes: : I tried many different combinations. I disabled the onboard serial devices : in the BIOS and kernel, so config index 0xf could grap io port 0x3f8 with : irq 4 but the only thing I get is : sio2: configured irq -1071415680 not in bitmap of probed i

Re: doscmd broken on current?

1999-01-04 Thread Warner Losh
In message <[EMAIL PROTECTED]> John Hay writes: : angel:~ > doscmd -bx I've never been able to boot dos with doscmd. I've only ever run programs like sourcer with it. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: gzip(1) hanging

1999-01-04 Thread Nate Williams
> I've got a -current box freshly CVSup'd and built from last > night that is exhibiting some rather bizarre behavior. I > actually noticed the problem on my Alpha package building > machine, but the same behavior exists on my i386 box. > > To see what I'm seeing (or maybe not :) all you have to

Re: gzip(1) hanging

1999-01-04 Thread Steve Price
On Sat, 6 Nov 1999, Nate Williams wrote: # > I've got a -current box freshly CVSup'd and built from last # > night that is exhibiting some rather bizarre behavior. I # > actually noticed the problem on my Alpha package building # > machine, but the same behavior exists on my i386 box. # > # > T

Re: doscmd broken on current?

1999-01-04 Thread Jonathan Lemon
In article [EMAIL PROTECTED]> you write: >Is doscmd working for anyone on current? Here I just get: > >- > >I have tried it on a single processor and SMP -current and both do the same >thing. I had it working a while back, so I think my configuration is ok. > >Ideas on how to look into th

Re: Serious locking problem in CURRENT

1999-01-04 Thread Dmitrij Tejblum
David Malone wrote: > A child process seems to be able to let go of a parent's lock on > 4.0 by closing a file discriptor, the same doesn't seem to be true > on 3.3. So, apparently, it was broken in rev. 1.68 of kern_descript.c. (Another example that comments (in closef() in this case) serve no

Re: Serious locking problem in CURRENT

1999-01-04 Thread Jonathan Lemon
In article [EMAIL PROTECTED]> you write: > >On Sat, Nov 06, 1999 at 12:50:16AM +0100, Ollivier Robert wrote: > >A child process seems to be able to let go of a parent's lock on >4.0 by closing a file discriptor, the same doesn't seem to be true >on 3.3. >From the manual page for flock: NOTES