Re: Build of RELENG_5 fails in libmagic

2004-11-14 Thread Mark Dixon
On Saturday 13 Nov 2004 21:01, Ruslan Ermilov wrote:
 On Sat, Nov 13, 2004 at 08:17:31PM +, Mark Dixon wrote:
  Hi,
 
  I'm trying to build 5-STABLE, I have cvsuped the latest source, cleared
  out /usr/obj and I still get this problem. Any idea what could be causing
  it?

 Check that your system's date/time is set correctly, I bet
 it's not.

Right, that was it. I noticed sending that email, but thought nothing of it. 
Is this something we could easily sanity check for at the start of the build?

Thanks for the help,


-- 
Mark

'If it compiles, ship it'


pgpcNomy0mwDF.pgp
Description: PGP signature


subscription to 5.3 stable mailing list, thanks

2004-11-14 Thread marco foglia
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: IPv6 bridge + gif tunnel

2004-11-14 Thread Hideki Yamamoto

Hi, 

About the combination between bridge function and gif tunnel function,
I have tested it on FreeBSD 4.10, but not succeeded.  FreeBSD 4.10 box
shows the message when we typed 'sysctl net.link.ether.bridge_cfg=rl0,gif0',

  gif0 is not an ethernet, continue
  interface gif0 Not found in bridge.

I changed operating system from FreeBSD to OpneBSD 3.5, and succeeded.
Multicast and unicast UDP packets, ICMP packets are bridged without
losing packets.  It seems that the bridge function on OpenBSD is
better than FreeBSD.  Though I will use OpenBSD for a while as a test
tool, I hope OpenBSD bridge function will be ported into FreeBSD in
the future.  Does anyone have a plan to port it?

Regards,

Hideki Yamamoto.

From: Hideki Yamamoto [EMAIL PROTECTED]
Subject: Re: IPv6 bridge + gif tunnel
Date: Sun, 07 Nov 2004 06:15:47 +0900 (JST)
Message-ID: [EMAIL PROTECTED]

 
 Hi,
 
 I would like to make my problems clear.
 I have two questions about bridge function in the following figure.
 
 (1) Can we use bridge function over psuedo devices such as
 gif and tun?
 
  box3# ifconfig bge0 inet 133.149.0.2 netmask 255.255.255.0
  box2# ifconfig create gif0
  box2# gifconfig gif0 inet 133.149.0.2 133.149.1.2
  box2# sysctl net.link.ether.bridge: 1
  box2# sysctl net.link.ether.bridge_cfg: fxp0,gif0
 
  box3# ifconfig bge1 inet 133.149.1.2 netmask 255.255.255.0
  box3# ifconfig create gif1
  box3# gifconfig gif1 inet 133.149.1.2 133.149.0.2
  box3# sysctl net.link.ether.bridge: 1
  box3# sysctl net.link.ether.bridge_cfg: gif1,fxp0
 
 (2) Can any protocols go through between IPv6 MC router and
 IPv6 terminal in this step2 figure?  Are there any limitations?
 Is IPv6 packet available?
 
  STEP2 IPv6 bridge cascaded by gif tunnel
  
+--box#2--+
[IPv6 MC router ]-+-+-(fxp0) IPv6 bridge  |
| |
| |
   (IPv4)133.149.0.2 +--+-(bge0) IPv6 bridge and IPv4 |
 |  | (gif0) IPv6 over IPv4   |
 |  +-+
 |
   IPv4 router   
 |
 |  +---box#3-+
   (IPv4)133.149.1.2 +--+-(bge1) IPv6 bridge and IPv4 |
| (gif1) IPv6 over IPv4   |
| |
| |
| |
 +--+-(fxp0) IPv6 bridge  |
 |  +-+
 |
 |term#2
 +-[IPv6 terminal(NDP client)]
  
 
 Thanks in advance
 
 Hidei Yamamoto
 
-
Hideki YAMAMOTO  |
Broadband Media Solutions Department | E-mail: [EMAIL PROTECTED]
Broadband Media Company  | Tel: +81-48-420-7012
Oki Electric Industry Co., Ltd.  | FAX: +81-48-420-7016
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Build of RELENG_5 fails in libmagic

2004-11-14 Thread Massimiliano Stucchi
On 130104, 19:37, Mark Dixon wrote:
 
 I'm trying to build 5-STABLE, I have cvsuped the latest source, cleared 
 out /usr/obj and I still get this problem. Any idea what could be causing it?
 
 /usr/obj/usr/src/i386/usr/bin/ld: cannot find -lc
 *** Error code 1

I had the same exact problem while tryint to buildworld on an amd64 box
I have, but this disappeared when I issued a make clean in /usr/src.
Maybe it could help.

Ciao !
-- 

Massimiliano Stucchi
WillyStudios.com
[EMAIL PROTECTED]
Http://www.willystudios.com/max/


pgpK2p073mmZ5.pgp
Description: PGP signature


Can't compile 5.3-STABLE from 5.3-RC2

2004-11-14 Thread Ralf Folkerts
Hi,

I wanted to Update my System that runs FreeBSD 5.3-RC2 to the final
5.3-Level.

However, compile reproducible stops in libstdc++, claiming a missing
unwind.h.

I already removed /usr/src and re-cvsupped it and also searched
the /usr/src/UPDATING and the CURRENT- and STABLE-Lists for such
Problems.

The Update from 5.2.1 to 5.3-RC2 ran just fine on that machine (after
removing the CXXFLAGS from /etc/make.conf).

uname -a:
FreeBSD beaster.home.folkerts-net.de 5.3-RC2 FreeBSD 5.3-RC2 #1: Mon Nov
1 15:42:06 CET 2004
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/BEASTERKERNEL
i386

I'll paste the libstdc++-Output and my /etc/make.conf below.

What did I do wrong? As it worked fine from 5.2.1 to 5.3 I hope it's
just a small Problem ;-)

Would be great if I could get a hint!
MTIA,
cheers,
_ralf_

--- /etc/make.conf ---
PUTYPE=athlon-xp
CFLAGS= -O -pipe
NO_LPR=yes
CUPS_OVERWRITE_BASE=yes
NOINET6=true
NOPROFILE=true
COMPAT4X=yes
# -- use.perl generated deltas -- #
# Created: Sat Jan 17 12:55:06 2004
# Setting to use base perl from ports:
PERL_VER=5.6.1
PERL_VERSION=5.6.1
PERL_ARCH=mach
NOPERL=yo
NO_PERL=yo
NO_PERL_WRAPPER=yo
X_WINDOW_SYSTEM=xfree86-4
--- end of /etc/make.conf ---

=== gnu/lib/libreadline/readline/doc
=== gnu/lib/libstdc++
ln -sf /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc
++/config/cpu/i486/atomicity.h atomicity.cc
rm -f .depend
mkdep -f .depend -a-DIN_GLIBCPP_V3 -DHAVE_CONFIG_H
-I/usr/src/gnu/lib/libstdc++ -I/usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc++/libsupc++ -I/usr/src/gnu/lib/libstdc
++/../../../contrib/gcc -I/usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc++/include /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc
++/libmath/signbitf.c /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc
++/libmath/signbitl.c /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc++/libmath/stubs.c/usr/src/gnu/lib/libstdc
++/../../../contrib/gcc/cp-demangle.c
mkdep -f .depend -a  /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc++/src/allocator.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc++/src/codecvt.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc++/src/complex_io.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc++/src/ctype.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc++/src/debug.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc
++/src/functexcept.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc
++/src/globals_locale.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc++/src/globals_io.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc++/src/ios.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc
++/src/ios_failure.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc++/src/ios_init.cc/usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc++/src/ios_locale.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc++/src/limits.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc++/src/list.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc++/src/locale.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc
++/src/locale_init.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc
++/src/locale_facets.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc++/src/localename.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc++/src/stdexcept.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc++/src/strstream.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc++/src/tree.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc
++/src/allocator-inst.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc
++/src/concept-inst.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc
++/src/fstream-inst.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc++/src/ext-inst.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc++/src/io-inst.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc
++/src/istream-inst.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc
++/src/locale-inst.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc
++/src/locale-misc-inst.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc++/src/misc-inst.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc
++/src/ostream-inst.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc
++/src/sstream-inst.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc
++/src/streambuf-inst.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc
++/src/string-inst.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc
++/src/valarray-inst.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc
++/src/wlocale-inst.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc++/src/wstring-inst.cc
atomicity.cc /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc
++/config/locale/generic/codecvt_members.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc
++/config/locale/generic/collate_members.cc /usr/src/gnu/lib/libstdc
++/../../../contrib/libstdc
++/config/locale/generic/ctype_members.cc /usr/src/gnu/lib/libstdc

new threads problem? pthread_cond_timedwait ?

2004-11-14 Thread David Gilbert
My hard drive failed right around FreeBSD-5.3, so I got to do a fresh
install of 5.3-RC1 followed by a cvsup to -STABLE (yesterday).

Due to my nvidia video driver, I still have libmap.conf forcing
libpthread to use libc_r.

When compiling audio/xmms-imms, I get the following error, and I don't
know how to deal with it:

c++  -L/usr/X11R6/lib `xmms-config --libs` -lc -lm -lpcre -lsqlite3 -lz -ltag 
analyzer.o spectrum.o `pkg-config fftw3f --libs` libimmscore.a -o  analyzer
/usr/local/lib/libgthread12.so.3: undefined reference to 
`pthread_cond_timedwait'

Dave.

-- 

|David Gilbert, Independent Contractor.   | Two things can only be |
|Mail:   [EMAIL PROTECTED]|  equal if and only if they |
|http://daveg.ca  |   are precisely opposite.  |
=GLO
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Either I do something wrong or there is a regexp bug in sed !!

2004-11-14 Thread Zoltan Frombach
I'm trying to use sed under FreeBSD 5.3-RELEASE in a new 'netqmail' port I 
am currently working on. I want to replace a bunch of digits (in plain 
English: a decimal number) in a text file at the beginning of a line. Here 
is how the original file looks before I do anything (this file is part of 
the netqmail-1.05 package, but it is unimportant):

--- file conf-split begins
23
This is the queue subdirectory split.
--- file conf-split ends
Okay, so I try to replace 23 (or whatever number is there!) at the beginning 
of the first line to let's say 199 in this file using sed. I would expect 
this to work:

sed -e s/^[0-9]+/199/ conf-split  conf-split.new
But it doesn't change anything in conf-spilt.new!! My regexp ^[0-9]+ doesn't 
match anything! After spending like an hour investigating this, I realized 
that the + after my bracket expression ( I'm talking about this part here: 
[0-9]+ ) does not match! If I omit the use of + and use * instead, I can 
make my regexp to match. So this works - but IMHO it's ugly:

sed -e s/^[0-9][0-9]*/199/ conf-split  conf-split.new
It gives this output, which is what I always wanted:
--- file conf-split.new begins
199
This is the queue subdirectory split.
--- file conf-split.new ends
According to the sed man page, the regexp syntax that is used by sed is 
documented in the re_format man page. And according to the re_format man 
page: A piece is an atom possibly followed by a single= `*', `+', `?', or 
bound.  An atom followed by `*' matches a sequence of 0 or more matches of 
the atom.  An atom followed by `+' matches a sequence of 1 or more matches 
of the atom. ...
And the definition of an atom is (quoted from the same man page): An atom 
is a regular expression enclosed in `()' (matching a match for the regular 
expression), an empty set of `()' (matching the null string)=, a bracket 
expression (see below) ...

So either my bracket expression ( [0-9] ) in my first sed command was not 
recognized as an atom, or if it was recognized as an atom then the + that 
followed it was not interpreted properly... Can anyone please tell me why?

I believe this is a bug in sed or in the regexp library which sed uses. If 
it is a regexp library issue, then there is a chance that it affects other 
programs that use it, as well! At least it can break all programs that use 
sed regexps, especially ports...

My uname -a is:
FreeBSD www..com 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov 12 
01:07:41 PST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ 
i386

Zoltan 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Either I do something wrong or there is a regexp bug in sed !!

2004-11-14 Thread Brandon S. Allbery KF8NH
On Sun, 2004-11-14 at 18:39, Zoltan Frombach wrote:
 match anything! After spending like an hour investigating this, I realized 
 that the + after my bracket expression ( I'm talking about this part here: 

Normal.

 According to the sed man page, the regexp syntax that is used by sed is 
 documented in the re_format man page. And according to the re_format man 
 page: A piece is an atom possibly followed by a single= `*', `+', `?', or 

You need to read it more carefully.  There are two kinds of regular
expressions, basic and extended.  sed, ed, and grep speak BRE
syntax, whereas awk and egrep speak ERE syntax.  + is special only in
ERE syntax.

(And then there's GNU, where the difference between BRE and ERE is that
some things use a preceding backslash in BRE and don't in ERE, and vice
versa, so GNU sed does what you want if you use \+ instead of +.)

-- 
brandon s. allbery[linux,solaris,freebsd,perl] [EMAIL PROTECTED]
system administrator  [WAY too many hats][EMAIL PROTECTED]
electrical and computer engineering, carnegie mellon univ. KF8NH

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Can't compile 5.3-STABLE from 5.3-RC2

2004-11-14 Thread Alex de Kruijff
On Sun, Nov 14, 2004 at 08:31:36PM +0100, Ralf Folkerts wrote:
 Hi,
 
 I wanted to Update my System that runs FreeBSD 5.3-RC2 to the final
 5.3-Level.
 
 However, compile reproducible stops in libstdc++, claiming a missing
 unwind.h.
 
 I already removed /usr/src and re-cvsupped it and also searched
 the /usr/src/UPDATING and the CURRENT- and STABLE-Lists for such
 Problems.
 
 The Update from 5.2.1 to 5.3-RC2 ran just fine on that machine (after
 removing the CXXFLAGS from /etc/make.conf).
 
 uname -a:
 FreeBSD beaster.home.folkerts-net.de 5.3-RC2 FreeBSD 5.3-RC2 #1: Mon Nov
 1 15:42:06 CET 2004
 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BEASTERKERNEL
 i386
 
 I'll paste the libstdc++-Output and my /etc/make.conf below.
 
 What did I do wrong? As it worked fine from 5.2.1 to 5.3 I hope it's
 just a small Problem ;-)

Did you follow the handbook to the letter? I was succesful at compileing
from RC2 to STABLE. You could try my script. I've put it in
www.kruijff.org/files/FreeBSD/update.sh

Options are:
update.sh cvs
update.sh build (fails to build my special kernels)
update.sh install GENERIC

Log files goto /var/world/

-- 
Alex

Please copy the original recipients, otherwise I may not read your reply.
WWW: http://www.kruijff.org/alex/FreeBSD/
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Either I do something wrong or there is a regexp bug in sed !!

2004-11-14 Thread Zoltan Frombach
You are right. My mistake. This indeed works:
sed -E -e s/^[0-9]+/199/ conf-split  conf-split.new
Thanks for clearing this up.
Zoltan
On Sun, 2004-11-14 at 18:39, Zoltan Frombach wrote:
match anything! After spending like an hour investigating this, I 
realized
that the + after my bracket expression ( I'm talking about this part 
here:
Normal.
According to the sed man page, the regexp syntax that is used by sed is
documented in the re_format man page. And according to the re_format man
page: A piece is an atom possibly followed by a single= `*', `+', `?', 
or
You need to read it more carefully.  There are two kinds of regular
expressions, basic and extended.  sed, ed, and grep speak BRE
syntax, whereas awk and egrep speak ERE syntax.  + is special only in
ERE syntax.
(And then there's GNU, where the difference between BRE and ERE is that
some things use a preceding backslash in BRE and don't in ERE, and vice
versa, so GNU sed does what you want if you use \+ instead of +.)
--
brandon s. allbery[linux,solaris,freebsd,perl] [EMAIL PROTECTED]
system administrator  [WAY too many hats][EMAIL PROTECTED]
electrical and computer engineering, carnegie mellon univ. KF8NH 
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Either I do something wrong or there is a regexp bug in sed !!

2004-11-14 Thread Bjrn Knig
use -E

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


New 5.x packages uploaded

2004-11-14 Thread Kris Kennaway
I've uploaded new packages for 5.3-stable; they'll make their way onto
the ftp mirrors over the next day or so.  Included are the new
versions of GNOME and KDE, among others.

Kris



pgpwhOvbU0XR1.pgp
Description: PGP signature


Re: Either I do something wrong or there is a regexp bug in sed !!

2004-11-14 Thread Maxime Henrion
Zoltan Frombach wrote:
 You are right. My mistake. This indeed works:
 
 sed -E -e s/^[0-9]+/199/ conf-split  conf-split.new
 
 Thanks for clearing this up.

For what it's worth, there is another way to write this regexp without
using the -E flag.  Since x+ == xx*, you can write it:
s/^[0-9][0-9]*/199/.  The reason for not using -E is that it's not
portable, since it's not specified by the standard.  GNU sed uses -r for
extended REs.

Cheers,
Maxime
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Either I do something wrong or there is a regexp bug in sed !!

2004-11-14 Thread Zoltan Frombach
Thanks. I will not use the -E flag then.
Zoltan
Zoltan Frombach wrote:
You are right. My mistake. This indeed works:
sed -E -e s/^[0-9]+/199/ conf-split  conf-split.new
Thanks for clearing this up.
For what it's worth, there is another way to write this regexp without
using the -E flag.  Since x+ == xx*, you can write it:
s/^[0-9][0-9]*/199/.  The reason for not using -E is that it's not
portable, since it's not specified by the standard.  GNU sed uses -r for
extended REs.
Cheers,
Maxime
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: New 5.x packages uploaded

2004-11-14 Thread Matthias Andree
Kris Kennaway [EMAIL PROTECTED] writes:

 I've uploaded new packages for 5.3-stable; they'll make their way onto
 the ftp mirrors over the next day or so.  Included are the new
 versions of GNOME and KDE, among others.

BTW, are we getting long-standing security issues in ports fixed, for
instance cups-base, open-motif, others? Yeah I know send patches, but my
ressources are limited and committers are also overworked already...

The general question I'd like to raise is how long will we allow ports
with known security flaws linger around before they are marked BROKEN?

-- 
Matthias Andree
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: New 5.x packages uploaded

2004-11-14 Thread Kris Kennaway
On Mon, Nov 15, 2004 at 04:06:07AM +0100, Matthias Andree wrote:
 Kris Kennaway [EMAIL PROTECTED] writes:
 
  I've uploaded new packages for 5.3-stable; they'll make their way onto
  the ftp mirrors over the next day or so.  Included are the new
  versions of GNOME and KDE, among others.
 
 BTW, are we getting long-standing security issues in ports fixed, for
 instance cups-base, open-motif, others? Yeah I know send patches, but my
 ressources are limited and committers are also overworked already...
 
 The general question I'd like to raise is how long will we allow ports
 with known security flaws linger around before they are marked BROKEN?

In general serious security flaws should be marked FORBIDDEN
immediately, and they generally are.  Fixing the security issues is up
to the community.

Kris


pgpXpiCG8HFqu.pgp
Description: PGP signature


gvinum setstate missing?

2004-11-14 Thread Zaphod Beeblebrox
I'm in the uncomfortable position of needing to setstate down a gvinum
drive.  I can't seem to effect this as the gvinum command doesn't
understand setstate (even though it proclaims that it does in gvinum
help).

Is there a way of making this so?
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


SIIG cards and puc

2004-11-14 Thread Paul Sandys

I've tried to get one of the 20x family 16C650 64-byte buffer SIIG cards to
work. It does not work out of the box.

I had to add 0x4001 into the flags in pucdata.c for my card and options
COM_MULTIPORT into the kernel config. It's still limited to 115200 baud, but
all I was interested is 9600 anyway.

Can this be implemented into the source tree ?

P.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
 [EMAIL PROTECTED]   Paul Sandys   |   New York Connect   http://www.nyct.net 
 network operations manager   |   Total Solution provider
-
  The Internet Solutions Provider You Can Count On !   
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


panic: APIC: Previous IPI is stuck

2004-11-14 Thread Adrian Wontroba
At work, I've just taken an old cast off NT server and used it as
a replacement for an equally elderly low end PC which performs an
important monitoring task.

I took the opportunity to upgrade to 5.3 (5.3-RC2 now, yesterday's
5.3-STABLE when I get to work again) rather than stay on 4.10-RELEASE.

The rationale was this would be a nice resilient machine, demonstrating
how FreeBSD can extend the useful working life of aging hardware.

The practice is that it it has now crashed three times in a couple of
days with panic: APIC: Previous IPI is stuck, the most recent one
dragging me out from home early in a Monday morning.

Over in current there are a couple of threads starting in late September
where a few people are suffering this problem.  Like them, I'm using an
old (1997) Pentium Pro multiprocessor, in my case a 4 way Fujitsu M700.

The machine is running with the SMP kernel (ie GENERIC + SMP), 4BSD
scheduler, without preemption.

I've set kern.sched.ipiwakeup.enabled=0 and crossed my fingers.

I'm a SMP novice.  Would the machine become stable if I switched to a
non-SMP kernel?  Reliability is more important than speed in this case,
and the opportunity for experimentation close to zero.  Creditability
has already been damaged by the gvinum RAID5 experience (8-(

I'm not knocking 5.3 - in all other respects it seems wonderful.

me too diagnostics:

kern.sched.name: 4BSD
kern.sched.quantum: 10
kern.sched.ipiwakeup.enabled: 1
kern.sched.ipiwakeup.requested: 858129
kern.sched.ipiwakeup.delivered: 858129
kern.sched.ipiwakeup.usemask: 1
kern.sched.ipiwakeup.useloop: 0
kern.sched.ipiwakeup.onecpu: 0
kern.sched.ipiwakeup.htt2: 0
kern.sched.followon: 0
kern.sched.pfollowons: 0
kern.sched.kgfollowons: 0
kern.sched.runq_fuzz: 1



MPTable, version 2.0.15

 looking for EBDA pointer @ 0x040e, found, searching EBDA @ 0x0008f000
 searching CMOS 'top of mem' @ 0x0008ec00 (571K)
 searching default 'top of mem' @ 0x0009fc00 (639K)
 searching BIOS @ 0x000f

 MP FPS found in BIOS @ physical addr: 0x000fdc30



MP Floating Pointer Structure:

  location: BIOS
  physical address: 0x000fdc30
  signature:'_MP_'
  length:   16 bytes
  version:  1.4
  checksum: 0x56
  mode: Virtual Wire



MP Config Table Header:

  physical address: 0x0008f151
  signature:'PCMP'
  base table length:332
  version:  1.4
  checksum: 0x05
  OEM ID:   'Fujitsu '
  Product ID:   'Pro Server  '
  OEM table pointer:0x
  OEM table size:   0
  entry count:  30
  local APIC address:   0xfee0
  extended table length:0
  extended table checksum:  0



MP Config Base Table Entries:

--
Processors: APIC ID Version State   Family  Model   Step
Flags
 3   0x11BSP, usable 6   1   9
0xfbff
 0   0x11AP, usable  6   1   9
0xfbff
 1   0x11AP, usable  6   1   9
0xfbff
 2   0x11AP, usable  6   1   9
0xfbff
--
Bus:Bus ID  Type
 0   PCI   
 1   PCI   
 2   EISA  
--
I/O APICs:  APIC ID Version State   Address
 8   0x11usable  0xfec0
 9   0x11usable  0xfec0c000
--
I/O Ints:   TypePolarityTrigger Bus ID   IRQAPIC ID PIN#
ExtINT  active-hiedge2 0  80
INT  conformsconforms2 1  81
INT  conformsconforms2 2  82
INT  conformsconforms2 3  83
INT  conformsconforms2 4  84
INT  conformsconforms2 5  85
INT  conformsconforms2 6  86
INT  conformsconforms2 7  87
INT  conformsconforms2 8  88
INT  conformsconforms2 9  89
INT  conformsconforms210  8   10
INT  conformsconforms211  8   11
INT  conformsconforms212  8   12
INT  

gvinum again?

2004-11-14 Thread Zaphod Beeblebrox
I'm looking at gstat while fsck'ing a gvinum partition.  The trouble
I'm seeing is that I don't see activity on the second disk.  Now...
I'm using fsck -n ... just checking things ... so there's no writes,
but does gvinum not (yet) load balance on reads?
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: msdosfs - support for large disks?

2004-11-14 Thread Torfinn Ingolfsen
On Sun, 31 Oct 2004 18:27:08 +0200
Saulius Menkevicius [EMAIL PROTECTED] wrote:

 It support those, you just have to include
 options MSDOSFS_LARGE
 in you kernel config file.

OK, I found that (shouldn't this be documented in the NOTES file,
even if it is an experimental patch?), and made a new kernel with it.

 At least it works for me on 184GB fat32 partition.

Well, it works here too, on a 234GB partition. Sort of, at least.
I can mount the partition, and copy files to (and from) it, make
directories and so on. But, I get lots of invalid file handle messages
when I try to copy files to it. That makes it unusable for me.

I guess I'll have to use something else.
-- 
Regards,
Torfinn Ingolfsen,
Norway


___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: gvinum again?

2004-11-14 Thread Paul Mather
On Mon, 2004-11-15 at 00:36 -0500, Zaphod Beeblebrox wrote:
 I'm looking at gstat while fsck'ing a gvinum partition.  The trouble
 I'm seeing is that I don't see activity on the second disk.  Now...
 I'm using fsck -n ... just checking things ... so there's no writes,
 but does gvinum not (yet) load balance on reads?

Your observation is correct: it doesn't (yet) load balance across plexes
of mirrored volumes; geom_mirror (gmirror) does, though (and offers
various load-balancing options).

Cheers,

Paul.
-- 
e-mail: [EMAIL PROTECTED]

Without music to decorate it, time is just a bunch of boring production
 deadlines or dates by which bills must be paid.
--- Frank Vincent Zappa
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: gvinum again?

2004-11-14 Thread Zaphod Beeblebrox
On Mon, 15 Nov 2004 01:26:54 -0500, Paul Mather [EMAIL PROTECTED] wrote:

 Your observation is correct: it doesn't (yet) load balance across plexes
 of mirrored volumes; geom_mirror (gmirror) does, though (and offers
 various load-balancing options).

Is this something planned for the near future?  I'm migrating legacy
units here, so I don't really have a choice.

... also ... I suspect, whatever form it eventually takes, that volume
management and geom and/or vinum is essential.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]