Re: m3socks and cvsup

[Warner Losh]

In message <19990608084217.a5...@alaska.cert.siemens.de> Udo Schweigert writes:
: I'm using it (runsocks cvsup -P m) for a year now and it works without 
: any problems. (Since cvsup 16 the "-P m" is not needed, so "runsocks cvsup"
: should so it).

Oddd.  I can't get mine to work.  I always get a destination
unreachable.

Warner


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: The choice of MAXPHYS

[Jos Backus]

On Tue, Jun 08, 1999 at 12:53:54AM -0600, Warner Losh wrote:
> Isn't that 24 bits for addresses?  You can dma from an ISA card to
> anywhere in the first 16M...

Arrgh, yes, I'm terribly confused. Sorry 'bout that.

-- 
Jos Backus  _/ _/_/_/  "Reliability means never
   _/ _/   _/   having to say you're sorry."
  _/ _/_/_/ -- D. J. Bernstein
 _/  _/ _/_/
jos.bac...@nl.origin-it.com  _/_/  _/_/_/  use Std::Disclaimer;


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Killing NIC's

[Leif Neland]

I seem to have killed my 2.NIC. Both probe and init as usual, and can read
from the net (trafshow) but can't transmit.
I removed both from the pc, without removing the netcable. (Trying to
resolve an IRQ-conflict)
Is this a bad-thing (tm) ?
If something went broke from this, I would expect it to be something other
than the transmitter.

Leif




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: m3socks and cvsup

[Udo Schweigert]

On Tue, Jun 08, 1999 at 01:36:21AM -0600, Warner Losh wrote:
> In message <19990608084217.a5...@alaska.cert.siemens.de> Udo Schweigert 
> writes:
> : I'm using it (runsocks cvsup -P m) for a year now and it works without 
> : any problems. (Since cvsup 16 the "-P m" is not needed, so "runsocks cvsup"
> : should so it).
> 
> Oddd.  I can't get mine to work.  I always get a destination
> unreachable.
> 
> Warner

Is your cvsup linked dynamic? If not, runsocks wont work.

Udo

---
Udo Schweigert  || Voice  : +49 89 636 42170
Siemens AG, Siemens CERT|| Fax: +49 89 636 48000
ZT IK 3 || email  : udo.schweig...@mchp.siemens.de
D-81730 Muenchen / Germany  ||: u...@cert.siemens.de
PGP fingerprint || 2A 53 F6 A6 30 59 64 02  6B C4 E0 73 B2 C9 6C E7
---


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: The choice of MAXPHYS

[Chuck Youse]

I believe the DMA chip itself provides 20 bits, and external circuitry
extends the remaining 4 bits.

Chuck Youse
Director of Systems
cyo...@cybersites.com

-Original Message-
From: Warner Losh 
To: Jos Backus 
Cc: Wilko Bulte ; zzh...@cs.binghamton.edu
; freebsd-hackers@FreeBSD.ORG

Date: Tuesday, June 08, 1999 1:54 AM
Subject: Re: The choice of MAXPHYS


>In message <19990603231216.a36...@hal.mpn.cp.philips.com> Jos Backus
writes:
>: On Thu, Jun 03, 1999 at 07:30:20PM +0200, Wilko Bulte wrote:
>: > 20 bits. But older cards can do no more than 64 kB.
>:
>: Indeed, 20 bits (=1 Mbyte) for the address, 16 bits for the transfer
counter
>: (offset).
>
>Isn't that 24 bits for addresses?  You can dma from an ISA card to
>anywhere in the first 16M...
>
>Warner
>
>
>To Unsubscribe: send mail to majord...@freebsd.org
>with "unsubscribe freebsd-hackers" in the body of the message
>



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Wierd behavour from G++28!

[Josef Karthauser]

Strange.

I'm having a wierd time trying to get a package called Swish++ working.
It's a C++/STL based program, which the author recommends compiling up
with Gcc2.8 or higher.

So... I've installed gcc-2.8.1 && glibstdc++-2.8.1.1, and compiled it
up.  Strangely however, the 'search' part of it core dumps in an
unexpected way.

gandalf% ./search
Segmentation fault (core dumped)
gandalf% gdb search search.core 
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"...
Core was generated by `search'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib/libm.so.2...done.
Reading symbols from /usr/lib/libc.so.3...done.
Reading symbols from /usr/libexec/ld-elf.so.1...done.
#0  0x8052c0f in ostream::flush () at /usr/include/ctype.h:149
149 }
(gdb) bt
#0  0x8052c0f in ostream::flush () at /usr/include/ctype.h:149
#1  0x8052912 in ostream::operator<< () at /usr/include/ctype.h:149
#2  0x804995f in main (argc=1, argv=0xbfbfdb54) at search.c:219
(gdb) l


What gives?  It looks like a library thing.

Can anyone put me on the right track please?

Joe
-- 
Josef KarthauserFreeBSD: How many times have you booted today?
Technical Manager   Viagra for your server (http://www.uk.freebsd.org)
Pavilion Internet plc.  [...@pavilion.net, j...@uk.freebsd.org, j...@tao.org.uk]


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: FS tuning (Was: File system gets too fragmented ???)

[Daniel C. Sobral]

Dag-Erling Smorgrav wrote:
> 
> No, I don't think there's much point in doing that before Kirk
> McKusick removes the restrictions on the soft updates code. When that
> happens, we can make soft updates non-optional and turn on soft
> updates on all file systems by default.

I hope *that* doesn't happen, unless the free space problem is
corrected first.

--
Daniel C. Sobral(8-DCS)
d...@newsguy.com
d...@freebsd.org

"definition of an expert: X means experimental and a spurt is a
drip under pressure."




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Wierd behavour from G++28!

[Thomas David Rivers]

> 
> Strange.
> 
> I'm having a wierd time trying to get a package called Swish++ working.
> It's a C++/STL based program, which the author recommends compiling up
> with Gcc2.8 or higher.
> 
> So... I've installed gcc-2.8.1 && glibstdc++-2.8.1.1, and compiled it
> up.  Strangely however, the 'search' part of it core dumps in an
> unexpected way.
> 
> gandalf% ./search
> Segmentation fault (core dumped)
> gandalf% gdb search search.core 
> 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"...
> Core was generated by `search'.
> Program terminated with signal 11, Segmentation fault.
> Reading symbols from /usr/lib/libm.so.2...done.
> Reading symbols from /usr/lib/libc.so.3...done.
> Reading symbols from /usr/libexec/ld-elf.so.1...done.
> #0  0x8052c0f in ostream::flush () at /usr/include/ctype.h:149
> 149 }
> (gdb) bt
> #0  0x8052c0f in ostream::flush () at /usr/include/ctype.h:149
> #1  0x8052912 in ostream::operator<< () at /usr/include/ctype.h:149
> #2  0x804995f in main (argc=1, argv=0xbfbfdb54) at search.c:219
> (gdb) l
> 
> 
> What gives?  It looks like a library thing.
> 
> Can anyone put me on the right track please?
> 
> Joe

 Or - it could be that the stream wasn't properly opened and no-one
checked for it...

 Look at line 219 in search.c, it should be a <<-operator operating
on a stream of some kind.  Then, find where that stream is 
declared/constructed and ensure everything is all right...


- Dave Rivers -


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Wierd behavour from G++28!

[Josef Karthauser]

On Tue, Jun 08, 1999 at 10:45:39AM -0400, Thomas David Rivers wrote:
> > (gdb) bt
> > #0  0x8052c0f in ostream::flush () at /usr/include/ctype.h:149
> > #1  0x8052912 in ostream::operator<< () at /usr/include/ctype.h:149
> > #2  0x804995f in main (argc=1, argv=0xbfbfdb54) at search.c:219
> > (gdb) l
> > 
 
>  Or - it could be that the stream wasn't properly opened and no-one
> checked for it...
> 
>  Look at line 219 in search.c, it should be a <<-operator operating
> on a stream of some kind.  Then, find where that stream is 
> declared/constructed and ensure everything is all right...

216file_vector the_index( index_file_name );
217if ( !the_index ) {
218cerr<< me << ": could not read index from "
219<< index_file_name << endl;
220::exit( 2 );
221}


(gdb) break 218
Breakpoint 1 at 0x8049941: file search.c, line 218.
(gdb) run
Starting program: /data/home/joe/src/swish/swish++-2.0/search 

Breakpoint 1, main (argc=1, argv=0xbfbfdb14) at search.c:219
219 << index_file_name << endl;
(gdb) print index_file_name
$1 = 0x806bfe2 "the.index"
(gdb) print me
$2 = 0xbfbfdc35 "search"
(gdb) print cerr
$3 = 134671820
(gdb) print endl
$4 = {} 0x8052d20 
(gdb) s
0x80528ed in ostream::operator<< () at /usr/include/ctype.h:149
149 }
(gdb) s

Program received signal SIGSEGV, Segmentation fault.
0x8052c0f in ostream::flush () at /usr/include/ctype.h:149
149 }

Is it because the program's compiled using the wrong includes?
(/usr/include/ctype.h && /usr/local/bin/g++28)


Joe
-- 
Josef KarthauserFreeBSD: How many times have you booted today?
Technical Manager   Viagra for your server (http://www.uk.freebsd.org)
Pavilion Internet plc.  [...@pavilion.net, j...@uk.freebsd.org, j...@tao.org.uk]


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Wierd behavour from G++28!

[Thomas David Rivers]

> On Tue, Jun 08, 1999 at 10:45:39AM -0400, Thomas David Rivers wrote:
> > > (gdb) bt
> > > #0  0x8052c0f in ostream::flush () at /usr/include/ctype.h:149
> > > #1  0x8052912 in ostream::operator<< () at /usr/include/ctype.h:149
> > > #2  0x804995f in main (argc=1, argv=0xbfbfdb54) at search.c:219
> > > (gdb) l
> > > 
>  
> >  Or - it could be that the stream wasn't properly opened and no-one
> > checked for it...
> > 
> >  Look at line 219 in search.c, it should be a <<-operator operating
> > on a stream of some kind.  Then, find where that stream is 
> > declared/constructed and ensure everything is all right...
> 
> 216file_vector the_index( index_file_name );
> 217if ( !the_index ) {
> 218cerr<< me << ": could not read index from "
> 219<< index_file_name << endl;
> 220::exit( 2 );
> 221}
> 
> 
>   (gdb) break 218
>   Breakpoint 1 at 0x8049941: file search.c, line 218.
>   (gdb) run
>   Starting program: /data/home/joe/src/swish/swish++-2.0/search 
> 
>   Breakpoint 1, main (argc=1, argv=0xbfbfdb14) at search.c:219
>   219 << index_file_name << endl;
>   (gdb) print index_file_name
>   $1 = 0x806bfe2 "the.index"
>   (gdb) print me
>   $2 = 0xbfbfdc35 "search"
>   (gdb) print cerr
>   $3 = 134671820
>   (gdb) print endl
>   $4 = {} 0x8052d20 
>   (gdb) s
>   0x80528ed in ostream::operator<< () at /usr/include/ctype.h:149
>   149 }
>   (gdb) s
> 
>   Program received signal SIGSEGV, Segmentation fault.
>   0x8052c0f in ostream::flush () at /usr/include/ctype.h:149
>   149 }
> 
> Is it because the program's compiled using the wrong includes?
> (/usr/include/ctype.h && /usr/local/bin/g++28)

 I was guessing that the stream may be wrong - but cerr is likely
correctly constructed...

 You may have mixed up the libraries somehow when you linked... but
I'll have to defer that to someone who's used gcc2.8...

- Dave Rivers -



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Wierd behavour from G++28!

[Josef Karthauser]

On Tue, Jun 08, 1999 at 12:03:03PM -0400, Thomas David Rivers wrote:
> > 
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x8052c0f in ostream::flush () at /usr/include/ctype.h:149
> > 149 }
> > 
> > Is it because the program's compiled using the wrong includes?
> > (/usr/include/ctype.h && /usr/local/bin/g++28)
> 
>  I was guessing that the stream may be wrong - but cerr is likely
> correctly constructed...
> 
>  You may have mixed up the libraries somehow when you linked... but
> I'll have to defer that to someone who's used gcc2.8...

Can someone comment please?  Is this a bug in the way the gcc2.8 is
installed, or is it a bug in my understanding?  (probably the latter).

Tnx,
Joe
-- 
Josef KarthauserFreeBSD: How many times have you booted today?
Technical Manager   Viagra for your server (http://www.uk.freebsd.org)
Pavilion Internet plc.  [...@pavilion.net, j...@uk.freebsd.org, j...@tao.org.uk]


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: The choice of MAXPHYS

[Wilko Bulte]

As Jos Backus wrote ...
> On Tue, Jun 08, 1999 at 12:53:54AM -0600, Warner Losh wrote:
> > Isn't that 24 bits for addresses?  You can dma from an ISA card to
> > anywhere in the first 16M...
> 
> Arrgh, yes, I'm terribly confused. Sorry 'bout that.

Be happy, you're not alone ;-)

|   / o / /  _   Arnhem, The Netherlands- Powered by FreeBSD -
|/|/ / / /( (_) BulteWWW  : http://www.tcja.nl  http://www.freebsd.org


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: m3socks and cvsup

[Warner Losh]

In message <19990608120755.a92...@alaska.cert.siemens.de> Udo Schweigert writes:
: Is your cvsup linked dynamic? If not, runsocks wont work.

No.  That's the problem...

Warner


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

edited xcircuit to current version, now what?

[Richard E. Hawkins]

I've edited the makefile in the portes, and the source, to install 
xcircuit 2.0a10 rather than 1.7 (1.7 can't open its own files, it 
seems).

the old patch-aa was 

*** Imakefile.orig  Thu Mar 12 12:22:41 1998
--- Imakefile   Sun May 17 15:52:05 1998
***
*** 31,37 
  # Change the following as desired to suit your environment:
  #
  #
! PREFIX = /usr/local
  XCIRCUIT_LIB_DIR = $(PREFIX)/lib/xcircuit
  XCIRCUIT_BIN_DIR = $(PREFIX)/bin
  XCIRCUIT_MAN_DIR = $(PREFIX)/man/man1
--- 31,37 
  # Change the following as desired to suit your environment:
  #
  #
! PREFIX ?= /usr/local
  XCIRCUIT_LIB_DIR = $(PREFIX)/lib/xcircuit
  XCIRCUIT_BIN_DIR = $(PREFIX)/bin
  XCIRCUIT_MAN_DIR = $(PREFIX)/man/man1


so I put the ? into that line in Imakefile.

Of the second patchfile,  the first patch was already in main, and the 
second added 

   fpsetmask(0) conditionally for freebsd at the beginning of main, so 
I inserted this.  

It compiles & installs, then executes, quite nicely.

I found instructions on what to do with them once I made them, but I'm 
not clear on how to make them.  I need to make a patch against 
/usr/ports/cad/xcircuit/work/xcircuit-2.0a10/xcircuit.c, 
/usr/ports/cad/xcircuit/work/xcircuit-2.0a10/Imakefile,
and  the Makefile.

I presume there's some difference between how I do the first two and 
the third.  And then I expect that there's some kind of CVS meta-patch 
that gets created, cos that a cvsup will update folks port collection?

rick



-- 




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Segfault in longjmp() ?

[Dan Moschuk]

The machine is a SMP 3.0-RELEASE box.

A heavily threaded program is segfaulting in the longjmp() function.
Any ideas what would cause this?

Regards,

Dan



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Segfault in longjmp() ?

[Thomas David Rivers]

> 
> The machine is a SMP 3.0-RELEASE box.
> 
> A heavily threaded program is segfaulting in the longjmp() function.
> Any ideas what would cause this?
> 
> Regards,
> 
> Dan
> 
> 

 You could have trashed your jmp_buf...  (i.e. you're passing bad data
to longjmp().)

 Just a thought...

- Dave Rivers -



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Segfault in longjmp() ?

[John Birrell]

Dan Moschuk wrote:
> 
> The machine is a SMP 3.0-RELEASE box.
> 
> A heavily threaded program is segfaulting in the longjmp() function.
> Any ideas what would cause this?

A bug in the thread exit code. This was fixed at the "13th hour" during
the release of 3.2.

-- 
John Birrell - j...@cimlogic.com.au; j...@freebsd.org 
http://www.cimlogic.com.au/
CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Segfault in longjmp() ?

[Daniel Eischen]

Dan Moschuk wrote:
> The machine is a SMP 3.0-RELEASE box.
>
> A heavily threaded program is segfaulting in the longjmp() function.
> Any ideas what would cause this?

Libc_r or Linuxthreads?

There are some known problems WRT signal handling in libc_r.  I
think they've been mostly fixed (with possible exception of
signals interrupting signal handlers) with the changes at:

  ftp://ftp.pcnet.com/users/eischen/FreeBSD/uthread.tgz

If you're having problems with libc_r and these changes don't
solve your problem, let me know.  Make sure you do a 'make clean'
in src/lib/libc_r before building.

Dan Eischen
eisc...@vigrid.com


To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: edited xcircuit to current version, now what?

[Kris Kennaway]

On Tue, 8 Jun 1999, Richard E. Hawkins wrote:

> I've edited the makefile in the portes, and the source, to install 
> xcircuit 2.0a10 rather than 1.7 (1.7 can't open its own files, it 
> seems).

See the section in the handbook on porting. These kinds of questions are
better sent to freebsd-ports where all the porters hang out.

Good luck!

Kris


"Never criticize anybody until you have walked a mile in their shoes,
because by that time you will be a mile away and have their shoes."
-- Unknown




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

Re: Wierd behavour from G++28!

[Brian Somers]

> On Tue, Jun 08, 1999 at 12:03:03PM -0400, Thomas David Rivers wrote:
> > > 
> > >   Program received signal SIGSEGV, Segmentation fault.
> > >   0x8052c0f in ostream::flush () at /usr/include/ctype.h:149
> > >   149 }
> > > 
> > > Is it because the program's compiled using the wrong includes?
> > > (/usr/include/ctype.h && /usr/local/bin/g++28)
> > 
> >  I was guessing that the stream may be wrong - but cerr is likely
> > correctly constructed...
> > 
> >  You may have mixed up the libraries somehow when you linked... but
> > I'll have to defer that to someone who's used gcc2.8...
> 
> Can someone comment please?  Is this a bug in the way the gcc2.8 is
> installed, or is it a bug in my understanding?  (probably the latter).

Perhaps you need a gcc-compiled version of libstdc++.  It's just a 
guess, but when we shifted to egcs, there were all sorts of problems 
linking against the gcc-compiled version.

> Tnx,
> Joe
> -- 
> Josef Karthauser  FreeBSD: How many times have you booted today?
> Technical Manager Viagra for your server (http://www.uk.freebsd.org)
> Pavilion Internet plc.  [...@pavilion.net, j...@uk.freebsd.org, 
> j...@tao.org.uk]

-- 
Brian 
     
Don't _EVER_ lose your sense of humour !  




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

SDL port done yet?

[Stephen Hocking-Senior Programmer PGS Tensor Perth]

A while ago, someone mentioned that they were partway through a port of the 
Simple DirectMedia Layer. Has this been completed?


Stephen
-- 
  The views expressed above are not those of PGS Tensor.

"We've heard that a million monkeys at a million keyboards could produce
 the Complete Works of Shakespeare; now, thanks to the Internet, we know
 this is not true."Robert Wilensky, University of California




To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message

CCD and strange hang

[Antti Kaipila]

I have two 10G hard drives and I have been trying to get them mirrored
with ccd. I have got /var (100MB) mirrored fine. But I'm experiencing
total hangup of the machine when trying to configure one disk ccd with the
slice ment as the second part of the /usr (9380MB) ccd.

Here's my slice layout from disk no. 1:

wd0s1a 40MB *
wd0s1b  swap261MB SWAP
wd0s1e100MB *
wd0s1f   9380MB *

I don't see anything in the logs. The machine just hangs totaly when I
issue the ccdconfig command (ccdconfig ccd2 32 none /dev/wd1s1h)

I have 4 ccd drivers in kernel.
OS version is FreeBSD 3.2-RELEASE

Any ideas? I'm at a loss here. Please CC me, I'm not on the list.

Thanks.

--
  Antti Kaipila 



To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message