Re: natd core dumping with bus error

2002-07-09 Thread Richard Seaman, Jr.
On Thu, Jul 04, 2002 at 09:20:38AM -0500, Richard Seaman, Jr. wrote: On Tue, Jul 02, 2002 at 06:04:36PM -0700, Joel M. Baldwin wrote: Something has messed up natd. If I don't have the punch_fw option in the /etc/natd.conf file it eventuially core dumps with a bus error. I think

Re: natd core dumping with bus error

2002-07-08 Thread Richard Seaman, Jr.
created a debug version of natd (but not libalias) and saw that the bus error was in PunchFWHole. Since I didn't have a debug version of libalias, I can't tell you what line. Perhaps PunchFWHole is being called when its not supposed to be, with bad values? -- Richard Seaman, Jr.email

Re: natd core dumping with bus error

2002-07-08 Thread Richard Seaman, Jr.
net.inet.ip.forwarding: 1 net.inet.ip.fastforwarding: 0 net.inet6.ip6.forwarding: 0 Everything works fine with pre new-ipfw, and has for years. Same rules, same configuration, and with new ipfw, core dump. -- Richard Seaman, Jr.email:[EMAIL PROTECTED] 5182 N. Maple Lane phone

Re: natd core dumping with bus error

2002-07-08 Thread Richard Seaman, Jr.
. The problem still exits. It isn't an instant dump, it runs for a while. Right. Typically 30secs - 5 mins before it dumped. And when I ran natd in verbose mode, it showed quite a few packets in and out before it dumped. -- Richard Seaman, Jr.email:[EMAIL PROTECTED] 5182 N. Maple Lane

Re: problems with natd, ipfw

2002-07-07 Thread Richard Seaman, Jr.
from any to any Yes, I saw this. However, 'ipfw l' doesn't include a 0 rule, and the rule list appears correct. -- Richard Seaman, Jr.email:[EMAIL PROTECTED] 5182 N. Maple Lane phone:262-367-5450 Nashotah WI 53058fax:262-367-5852 To Unsubscribe: send

Re: problems with natd, ipfw

2002-07-07 Thread Richard Seaman, Jr.
On Sun, Jul 07, 2002 at 04:45:52PM -0500, Richard Seaman, Jr. wrote: On Sun, Jul 07, 2002 at 11:35:46PM +0200, Szilveszter Adam wrote: Hello everybody, I upgraded to yesterday's -CURRENT and have made a few observations: 2) and much more alarmingly: Although the new ipfw really seems

Re: natd core dumping with bus error

2002-07-04 Thread Richard Seaman, Jr.
ip_dummynet.c ip_fw.h sys/conf files lib/libalias alias_db.c Added files: sbin/ipfwipfw2.c sys/netinet ip_fw2.c Log: The new ipfw code. -- Richard Seaman, Jr.email:[EMAIL PROTECTED] 5182 N. Maple Lane phone:262-367

Re: xmms broken by either libc_r or sound

2000-06-14 Thread Richard Seaman, Jr.
to chn_wrintr in channel.c. Lots of the reportable problems with the pcm driver can be reproduced here when the driver does not get dma interrupts. However, it may be unique to my setup. -- Richard Seaman, Jr.email:[EMAIL PROTECTED] 5182 N. Maple Lane phone:262-367-5450 Nashotah

PCM problems (was Re: cvs commit: src/sys/dev/sound/pcm channel.c)

2000-06-11 Thread Richard Seaman, Jr.
- Jordan On Fri, Jun 09, 2000 at 02:11:29PM -0500, Richard Seaman, Jr. wrote: If I just cat a .au file into /dev/audio, I get about 1/4 of a second of plan and then silence, with without the patch. Your symptoms are different then. Don't know if the cause is the same. Thin

Re: IPv6: can a link-site (or global) address be configured in rc.conf?

2000-03-10 Thread Richard Seaman, Jr.
please try this patches and try to ping6 to my host's 6to4 address? The procedure is, For the benefit of the lists, and confirming private mail I sent, ping6 works using the second of the patches sent (I didn't try the first). -- Richard Seaman, Jr. email: [EMAIL PROTECTED] 5182 N

Re: IPv6: can a link-site (or global) address be configured in rc.conf?

2000-03-10 Thread Richard Seaman, Jr.
On Fri, Mar 10, 2000 at 07:35:08AM -0600, Richard Seaman, Jr. wrote: On Fri, Mar 10, 2000 at 08:09:04PM +0900, Yoshinobu Inoue wrote: 6to4 support seems to be very important for initial IPv6 deployment on FreeBSD4.0, so I tried small additinal patches to make it available. And It seems

Re: IPv6: can a link-site (or global) address be configured in rc.conf?

2000-03-10 Thread Richard Seaman, Jr.
the non 6to4 address as the source? I can ping6 your non 6to4 address from my 6to4 address, see attached. -- Richard Seaman, Jr. email: [EMAIL PROTECTED] 5182 N. Maple Lanephone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 PING6(56=40+8+8 bytes) 2002:cc5f:bb02

Re: IPv6: can a link-site (or global) address be configured in rc.conf?

2000-03-10 Thread Richard Seaman, Jr.
:5aff:fe86:b65a ping6 statistics --- 7 packets transmitted, 5 packets received, 28% packet loss round-trip min/avg/max = 341.997/432.005/582.145 ms -- Richard Seaman, Jr. email: [EMAIL PROTECTED] 5182 N. Maple Lanephone: 262-367-5450 Chenequa WI 53058 fax: 262-367

Re: IPv6: can a link-site (or global) address be configured in rc.conf?

2000-03-10 Thread Richard Seaman, Jr.
that freenet6 was OK. Just to clarify, I had to configure a hole in ipfw for freenet6.net too. I had just forgotten about it. :) -- Richard Seaman, Jr. email: [EMAIL PROTECTED] 5182 N. Maple Lanephone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852

Re: IPv6: can a link-site (or global) address be configured in rc.conf?

2000-03-06 Thread Richard Seaman, Jr.
n't really need 6to4 "relay" routers? This is only for reaching native IPv6 sites without 6to4 addresses? Thanks. -- Richard Seaman, Jr. email: [EMAIL PROTECTED] 5182 N. Maple Lanephone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe:

Re: xntpd - VERY old folks, how about updating? :-)

2000-01-29 Thread Richard Seaman, Jr.
with bde about them. This was about 1-2 months ago. -- Richard Seaman, Jr. email: [EMAIL PROTECTED] 5182 N. Maple Lanephone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-cu

Re: ATA driver problem?? (lost disk contact)

1999-12-18 Thread Richard Seaman, Jr.
gs. As I said, this is purely a wild guess from someone who understands all this poorly. -- Richard Seaman, Jr. email: [EMAIL PROTECTED] 5182 N. Maple Lanephone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to [EMAIL PROTEC

Re: ATA driver problem?? (lost disk contact)

1999-12-17 Thread Richard Seaman, Jr.
secs max for this drive. I'm assuming that what we're seeing is that the ata driver "lost contact" because the timeout is less that the time it takes to spinup from standby to idle (or to spinup from an interrupted switch from idle to standby)? -- Richard Seaman, Jr. ema

Re: ATA driver problem?? (lost disk contact)

1999-12-17 Thread Richard Seaman, Jr.
pinning up. If so, for just this case, perhaps you can adjust the timeout to a greater value before retrying the command? Also, perhaps you want to skip printing the diagnostic if the timeout was due to standby/spinup, unless it also fails on retry? -- Richard Seaman, Jr. ema

Re: ATA driver problem?? (lost disk contact)

1999-12-16 Thread Richard Seaman, Jr.
ecs/int, 1 depth queue, DMA Dec 11 11:31:02 test /kernel: ad2: Maxtor 91152D8/WAS82739 ATA-4 disk at ata1 as master Dec 11 11:31:02 test /kernel: ad2: 10991MB (22510656 sectors), 22332 cyls, 16 heads, 63 S/T, 512 B/S Dec 11 11:31:02 test /kernel: ad2: 16 secs/int, 1 depth queue, UDMA33 -- Richard

Re: ATA driver problem?? (lost disk contact)

1999-12-16 Thread Richard Seaman, Jr.
sturbed by a command, it is retried 12 hours later. For timeout concern, refer to 13.0, "Timeout Values" on page 185. -- Richard Seaman, Jr. email: [EMAIL PROTECTED] 5182 N. Maple Lanephone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe:

Re: SiS ata Driver (was Re: HEADSUP: wd driver will be retired!)

1999-12-11 Thread Richard Seaman Jr.
On Thu, Dec 09, 1999 at 11:28:20AM +0100, Soren Schmidt wrote: It seems Soren Schmidt wrote: It seems Richard Seaman, Jr. wrote: On Wed, Dec 08, 1999 at 03:02:37PM +0100, Soren Schmidt wrote: OK, you asked for it, following is a patch to support the sis 5591 chipset. Remember

Re: Reasonable decision-making [Re: HEADSUP: wd driver will be retired!]

1999-12-11 Thread Richard Seaman, Jr.
gone, I would still vote to retain it for some intermediate period. You can put my vote in the appropriate column of your tally. -- Richard Seaman, Jr. email: [EMAIL PROTECTED] 5182 N. Maple Lanephone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852

Re: Breaking DMA support for multiple chipsets? (was: HEADSUP: wd driver will be retired!)

1999-12-09 Thread Richard Seaman Jr.
was changed from the original submission, when it was committed. See the attached message: From [EMAIL PROTECTED] Thu May 6 15:14:56 1999 Date: Thu, 6 May 1999 15:14:56 -0500 From: "Richard Seaman, Jr." [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Buglet in SiS support in ide_pci.c

Re: HEADSUP: wd driver will be retired!

1999-12-08 Thread Richard Seaman, Jr.
in the tree for a while, even if its not the default. Possibly there are others in the same boat? -- Richard Seaman, Jr. email: [EMAIL PROTECTED] 5182 N. Maple Lanephone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to [EMAIL

SiS ata Driver (was Re: HEADSUP: wd driver will be retired!)

1999-12-08 Thread Richard Seaman, Jr.
heads, 63 S/T, 512 B/S Dec 8 17:25:02 test /kernel: ad2: 16 secs/int, 1 depth queue, UDMA33 Dec 8 17:25:02 test /kernel: Mounting root from ufs:/dev/ad0s1a -- Richard Seaman, Jr. email: [EMAIL PROTECTED] 5182 N. Maple Lanephone: 262-367-5450 Chenequa WI 53058

Re: ATA driver as the default

1999-12-06 Thread Richard Seaman, Jr.
. With wd I get UDMA. This was about 2-3 weeks ago. -- Richard Seaman, Jr. email: [EMAIL PROTECTED] 5182 N. Maple Lanephone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-cu

Re: new sigset_t and upgrading: a proposal

1999-10-02 Thread Richard Seaman, Jr.
in the patchkit days, or very early FreeBSD 1.x. Unless I'm mistaken, the FreeBSD Tutorial "Upgrading FreeBSD from source" tells you to "make world" before you make and install the kernel. I take it the tutorial is wrong? :) -- Richard Seaman, Jr. email: [EMAIL PROTECTED

Re: calcru and upages

1999-05-24 Thread Richard Seaman, Jr.
) thoughts on what FreeBSD thread related syscalls might be helpful. -- Richard Seaman, Jr. email: d...@tar.com 5182 N. Maple Lanephone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd

Re: compiler specs for -pthread/-kthread

1999-04-13 Thread Richard Seaman, Jr.
to their compile options. (This works now too). -- Richard Seaman, Jr. email: d...@tar.com 5182 N. Maple Lanephone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body

Re: rfork()

1999-03-22 Thread Richard Seaman, Jr.
worth doing, but not a top priority. The main issue is to decide what interface would be most convenient. Its not a top priority since the code already exists for those (rare) cases where someone really needs it. And, lets not call it clone. -- Richard Seaman, Jr. email: d...@tar.com

Re: rfork()

1999-03-21 Thread Richard Seaman, Jr.
, which includes an example using thr_fork. No reason I can see that thr_fork and/or clone couldn't be added to libc. -- Richard Seaman, Jr. email: d...@tar.com 5182 N. Maple Lanephone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 .file rf.S #include

Re: rfork()

1999-03-21 Thread Richard Seaman, Jr.
, thread_self can examine its stack, and derive the address of the TLS efficiently. Now, it would be very nice to find a better way to do the thread_self stuff. -- Richard Seaman, Jr. email: d...@tar.com 5182 N. Maple Lanephone: 414-367-5450 Chenequa WI 53058 fax: 414

SMP Threads (was: Re: SMP and SO5.0)

1999-03-04 Thread Richard Seaman, Jr.
problem is, whether it is a bad signal handler, or more likely, the real problem is whatever generated the signal within malloc/free, and the bad signal handler is a misdirect. -- Richard Seaman, Jr. email: d...@tar.com 5182 N. Maple Lanephone: 414-367-5450 Chenequa WI 53058

Heads up: Linux Thread port changes.

1999-03-02 Thread Richard Seaman, Jr.
in emulation mode you don't have to worry about this. -- Richard Seaman, Jr. email: d...@tar.com 5182 N. Maple Lanephone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body

Re: lockmgr panic with mmap()

1999-02-28 Thread Richard Seaman, Jr.
as the old code, but via a different path. Case d) will now continue executing in a manner equivalent to the new case c). The question is whether there is a way to do the autogrow function if the map lock is already held. -- Richard Seaman, Jr. email: d...@tar.com 5182 N. Maple Lane

Re: /etc/defaults/rc.conf

1999-02-16 Thread Richard Seaman, Jr.
in /etc/rc.conf ? It appears to here. -- Richard Seaman, Jr. email: d...@tar.com 5182 N. Maple Lanephone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body

Re: more about yield() versus sched_yield()

1999-01-31 Thread Richard Seaman, Jr.
. its a kernel thread of the same process) and if so, raise the priority of pid to that of the calling process for one time slice so pid has a chance to execute and free the lock. -- Richard Seaman, Jr. email: d...@tar.com 5182 N. Maple Lanephone: 414-367-5450 Chenequa WI

Re: LINUX clone? sched_yield?

1999-01-30 Thread Richard Seaman, Jr.
-DCOMPAT_LINUX_THREADS to CFLAGS and COPTFLAGS in /etc/make.conf and make world and remake and install your kernel. Also, you need to add the posix priority extensions to your kernel (see LINT). Or, there is also more information at http://lt.tar.com -- Richard Seaman, Jr. email: d

Re: Locked at 100% User CPU

1999-01-29 Thread Richard Seaman, Jr.
implementation. It wouldn't be all that much more work than getting the user thread code in first rate shape. But, either way I think its a fairly big project. -- Richard Seaman, Jr. email: d...@tar.com 5182 N. Maple Lanephone: 414-367-5450 Chenequa WI 53058 fax

Re: 4.0-Current, netscape halts system

1999-01-27 Thread Richard Seaman, Jr.
On Wed, Jan 27, 1999 at 10:20:14AM -0500, Brian Feldman wrote: On Wed, 27 Jan 1999, Sheldon Hearn wrote: I still don't think we're getting any closer to the question Why is Netscape unstable on CURRENT when it worked fine for me on STABLE? The problem seems to be that those who know

Re: 4.0-Current, netscape halts system

1999-01-27 Thread Richard Seaman, Jr.
On Wed, Jan 27, 1999 at 10:02:31AM -0600, Richard Seaman, Jr. wrote: If you have Netscape problems, it would be worthwhile to try removing -DVM_STACK from src/sys/compile/BLAH/Makefile and doing a make clean all install. I am pretty certain this is the cause of Netscape crashing, at least

Re: 4.0-Current, netscape halts system

1999-01-27 Thread Richard Seaman, Jr.
On Wed, Jan 27, 1999 at 11:04:22AM -0800, Parag Patel wrote: Just another data point. I just updated my 2xPII/300 system to 4.0-CURRENT last night (Tues Jan 26), and I'm running Netscape 4.5 just fine - no crashes od any odd behavior at all. VM_STACK is defined, I have 256Mb RAM, and

Re: Netscape | Mozilla

1999-01-27 Thread Richard Seaman, Jr.
On Wed, Jan 27, 1999 at 02:20:32PM -0500, Luke wrote: I tried that one but it wants linux_lib installed on /compat and theres no room. Do you know if its ok to make /compat a link to somewhere else for the linux_lib port. [why does it install into / anyways] I have /compat

Whats VM_STACK (was Re: Netscape | Mozilla)

1999-01-27 Thread Richard Seaman, Jr.
On Wed, Jan 27, 1999 at 12:35:09PM -0500, Luke wrote: what is this VM_STACK option? Its some new code to manage autogrow stacks. The existing (old) code made a process stack autogrow. But, its useful to be able to create additional autogrow memory regions to use as thread stacks in

Re: HEADS UP! (kernel thread support)

1999-01-26 Thread Richard Seaman, Jr.
On Mon, Jan 25, 1999 at 07:09:37PM -0800, Manfred Antar wrote: At 06:41 PM 1/25/99 -0800, Julian Elischer wrote: The Linuxthreads changes in the system that have been optioned out for a while have been enabled after testing by many people. this will require a recompile of at least PS and

Re: linux kld

1999-01-26 Thread Richard Seaman, Jr.
On Tue, Jan 26, 1999 at 02:38:12PM -0500, Kenneth Wayne Culver wrote: when my computer starts up (just finished make world 5 minutes ago) I get the following error: link_elf: symbol grow undefined. does this mean that the linux emu is broken right now? I think it means there is a goof in

Re: IDE DMA works, I'll be a...

1999-01-25 Thread Richard Seaman, Jr.
On Mon, Jan 25, 1999 at 05:08:19PM +1100, Bruce Evans wrote: Can you find out what chipset is in this guy? There's support for anything Intel or VIA, Promise UDMA cards, Cyrix MediaGX, and Acer Aladdin IV/V right now. See kern/9550. The driver *used* to support my SiS chipset, but it

Re: Using LinuxThreads

1999-01-22 Thread Richard Seaman, Jr.
On Thu, Jan 21, 1999 at 07:39:28PM -0700, Russell L. Carter wrote: d...@tar.com said: %libc_r could be modified so that is doesn't replace libc, but rather %is an addon, comparable to the kernel threaded libc case. But, it %would involve a bit of work. I thought so at first, but then I

Re: Using LinuxThreads

1999-01-22 Thread Richard Seaman, Jr.
On Thu, Jan 21, 1999 at 12:38:14PM -0600, Richard Seaman, Jr. wrote: On Thu, Jan 21, 1999 at 06:12:29PM +0200, Jeremy Lea wrote: On Tue, Jan 19, 1999 at 09:11:51AM -0600, Richard Seaman, Jr. wrote: Actually, the new version, in FreeBSD ports form, doesn't require -DLINUXTHREADS anymore

Re: -D_REENTRANT (Was: Using LinuxThreads)

1999-01-22 Thread Richard Seaman, Jr.
On Thu, Jan 21, 1999 at 02:00:53PM -0800, Kurt D. Zeilenga wrote: For kernel threading you just use libc. Whether or not libc generates thread safe (re-entrant) calls depends on whether its also linked with a library that 1) sets __isthreaded to a non-zero value, 2) has a _spinlock()

Re: -D_REENTRANT (Was: Using LinuxThreads)

1999-01-22 Thread Richard Seaman, Jr.
On Fri, Jan 22, 1999 at 09:49:23AM -0800, Kurt D. Zeilenga wrote: Richard Seaman, Jr. wrote: _THREAD_SAFE is only used in stdio.h. Looking at what's there, it could be rewritten to eliminate _THREAD_SAFE entirely, at a (very slight) performance penalty. You'd have to check __isthreaded

Re: Using LinuxThreads

1999-01-22 Thread Richard Seaman, Jr.
On Fri, Jan 22, 1999 at 02:47:53PM -0500, Alfred Perlstein wrote: *confused look* somehow even though i've been trying to follow this thread i got lost. questions: 1) are 'linuxthreads' enabled by defualt now? The terminology is a little confusing. There's linuxthreads for those running

Re: Using LinuxThreads

1999-01-21 Thread Richard Seaman, Jr.
On Thu, Jan 21, 1999 at 06:12:29PM +0200, Jeremy Lea wrote: On Tue, Jan 19, 1999 at 09:11:51AM -0600, Richard Seaman, Jr. wrote: Actually, the new version, in FreeBSD ports form, doesn't require -DLINUXTHREADS anymore, but it does require -I/usr/local/include to pick up the right header

Re: Using LinuxThreads

1999-01-21 Thread Richard Seaman, Jr.
On Thu, Jan 21, 1999 at 11:04:38AM -0800, Julian Elischer wrote: On Thu, 21 Jan 1999, Richard Seaman, Jr. wrote: And when are COMPAT_LINUX_THREADS and VM_STACK going away? I have no idea. I was hoping that at least COMPAT_LINUX_THREADS would go away before the branch. I don't

Re: Using LinuxThreads

1999-01-21 Thread Richard Seaman, Jr.
On Thu, Jan 21, 1999 at 11:42:14AM -0800, Kurt D. Zeilenga wrote: This is nagging at me. Having two headers of the same name, but importantly different content is asking for touble. There needs to be a way to ensure that only one or the other is picked up. The best way I can think of is to

Re: linuxthreads, gimp 1.1+, dies

1999-01-19 Thread Richard Seaman, Jr.
On Mon, Jan 18, 1999 at 06:27:18PM -0800, br...@worldcontrol.com wrote: I running gimp -unstable (CVS 1/17/1998) and FreeBSD -current (1/17/1998) with CFLAGS= -O2 -m486 -pipe -DCOMPAT_LINUX_THREADS -DVM_STACK COPTFLAGS= -O -pipe -DCOMPAT_LINUX_THREADS -DVM_STACK and linuxthreads port

Re: linuxthreads, gimp 1.1+, dies

1999-01-19 Thread Richard Seaman, Jr.
On Tue, Jan 19, 1999 at 02:06:13PM +0200, Jeremy Lea wrote: On Tue, Jan 19, 1999 at 02:45:39AM -0800, br...@worldcontrol.com wrote: Gimp (CVS) compiled with CFLAGS=-g -D_THREAD_SAFE -I/usr/local/include -L/usr/local/lib -O2 -m486 -pipe -lpthread Hmm, if you're using the libpthread from