TB --- 2003-09-10 08:11:32 - starting CURRENT tinderbox run for i386/pc98
TB --- 2003-09-10 08:11:32 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/i386/pc98
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-09-10 08:16:01 - building world
TB --- cd
Hi
I was experimenting with growfs yesterday and I noticed this wierd
thing crop up in my label. Notice the 'a' partition which I can
no longer get rid of and appears automatically. using bsdlabel -e
I have to delete this partition if I want to change any of the other
partitions (it complains
TB --- 2003-09-10 09:33:53 - starting CURRENT tinderbox run for ia64/ia64
TB --- 2003-09-10 09:33:53 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-09-10 09:37:18 - building world
TB --- cd
TB --- 2003-09-10 10:46:59 - starting CURRENT tinderbox run for sparc64/sparc64
TB --- 2003-09-10 10:46:59 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-09-10 10:48:53 - building world
TB
Sorry if this sounds a bit flame-ish, but the way I see it we now have a
system compiler in -CURRENT that doesn't even compile a hello world if
-pedantic is specified and breaks with lots of existing software out there
that tries to use a threads library because -pthread errors out (why could
I was trying to boot my net4501 board with PXE.
This worked like a charm with pxeboot compiled on -STABLE, but
using -CURRENT to build it my net4501 continuously reboot just after
the DHCP/TFTP phase (it appears something like POST12345 and
then reboots). Any hint?
--
Alex Dupre
Is devfs.conf still valid? I didn't find a man page. Also man devfs
doesn't list any FILES section.
I want to have
own da0 root:stick
perm da0 0660
and when I put this in /etc/devfs.conf it doesn't seem to have any effect.
--
Chris Christoph P. U. Kukulies kukulies (at) rwth-aachen.de
The following thing became clear as a result of investigating many things.
Network collision increased strangely, after it turned into the following revision.
/src/sys/pci/if_dc.c
Revision 1.115 Sun Jul 6 21:45:31 2003 UTC
Why does collision increase by this change?
On Wed, 10 Sep 2003 15:30:28 +0200
Michael Nottebrock [EMAIL PROTECTED] wrote:
Sorry if this sounds a bit flame-ish, but the way I see it we now have
a system compiler in -CURRENT that doesn't even compile a hello world
if-pedantic is specified and breaks with lots of existing software out
Hi,
I'm trying to enable DRM on an ATI Radeon AIW 8500DV (Which gets detected
as a Radeon R200 BB-class board). I've added both device radeondrm and
device agp to my kernel config file and made sure that XFree86 has both
a load dri and a load glx directive.
I'm seeing the following in my
This is the exact output:
CLIENT MAC ADDR: 00 00 24 C1 2D F0
CLIENT IP: 10.0.0.36 MASK: 255.255.255.0 DHCP IP: 10.0.0.1
GATEWAY IP: 10.0.0.4
PXE Loader 1.00
Building the boot loader arguments
Relocating the loader and the BTX
Starting the BTX loader
POST: 012345...
rebooting...the pxeboot
Steve Kargl wrote:
I have no problems in building the traditional C hello world
program with cc -pedantic.
You're right about that, you'll need a C++ hello world (iostream, cout).
This is in the archives anyway and (should be) well known.
(why could
this change not have been made _after_ 4.9
Am Mi, 2003-09-10 um 15.30 schrieb Michael Nottebrock:
Sorry if this sounds a bit flame-ish, but the way I see it we now have a
system compiler in -CURRENT that doesn't even compile a hello world if
-pedantic is specified and breaks with lots of existing software out there
Yes. I agree on
* Alexander Leidinger [EMAIL PROTECTED] [030910 10:53]:
In 5-current we have 3 threads libraries and want to be able to install
and use them in parallel. So there has to be a way to specify which one.
This is why we need the ports collection to respect the PTHREAD*
variables. A lot of ports
On Wed, Sep 10, 2003 at 05:23:55PM +0200, Michael Nottebrock wrote:
Steve Kargl wrote:
I have no problems in building the traditional C hello world
program with cc -pedantic.
You're right about that, you'll need a C++ hello world (iostream, cout).
This is in the archives anyway and
TB --- 2003-09-10 16:00:01 - starting CURRENT tinderbox run for alpha/alpha
TB --- 2003-09-10 16:00:01 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-09-10 16:03:28 - building world
TB --- cd
On Wed, 10 Sep 2003, Andre Guibert de Bruet wrote:
I'm trying to enable DRM on an ATI Radeon AIW 8500DV (Which gets detected
as a Radeon R200 BB-class board). I've added both device radeondrm and
device agp to my kernel config file and made sure that XFree86 has both
a load dri and a load
There's been few reports of deadlocks in md on the lists recently,
and I walked into it trying to generate flash images for my shiny
new Soekris box. In particular, A previous mail mentioned something
getting stuck in wdrain: (Message-ID [EMAIL PROTECTED]
from [EMAIL PROTECTED])
For the
On Tue, 9 Sep 2003, Tomi Vainio - Sun Finland wrote:
Tomi Vainio - Sun Finland writes:
Our system died when using iozone -a to ~300G vinum partition made
from four disks. Sources were cvsupped 7.9.2003.
Second panic an hour later. Any good ideas how to fix this?
Tomppa
panic:
On Wed, Sep 10, 2003 at 12:41:41PM -0400, Michael Edenfield wrote:
gnome2 depends on gnomemedia2.
gnomemedia2 depends on gstreamer-plugins.
gstreamer-plugins fails because ARTSD_FLAGS in several dozen Makefiles
includes -pthread.
This is being worked on from the compiler stand point.
On Wed, Sep 10, 2003 at 09:56:45AM -0700, Steve Kargl wrote:
4.9 and 5.0-R are independent branch. By your logic we should wait to
4.10 or 4.11 or 4.12 or ... before any substantial change can be made
to -CURRENT.
The point is that is isn't wise to commit a change like the -pthread
Doug White writes:
On Tue, 9 Sep 2003, Tomi Vainio - Sun Finland wrote:
Tomi Vainio - Sun Finland writes:
Our system died when using iozone -a to ~300G vinum partition made
from four disks. Sources were cvsupped 7.9.2003.
Second panic an hour later. Any good ideas how
On Wed, 10 Sep 2003, Michael Nottebrock wrote:
Sorry if this sounds a bit flame-ish, but the way I see it we now have a
system compiler in -CURRENT that doesn't even compile a hello world if
-pedantic is specified and breaks with lots of existing software out there
that tries to use a threads
* David O'Brien [EMAIL PROTECTED] [030910 15:33]:
On Wed, Sep 10, 2003 at 12:41:41PM -0400, Michael Edenfield wrote:
gnome2 depends on gnomemedia2.
gnomemedia2 depends on gstreamer-plugins.
gstreamer-plugins fails because ARTSD_FLAGS in several dozen Makefiles
includes -pthread.
This
Tomi Vainio - Sun Finland [EMAIL PROTECTED] writes:
First maxusers was 0 then when changed it to 8.
That's a regression. Keep it at 0.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
Dag-Erling Smørgrav writes:
Tomi Vainio - Sun Finland [EMAIL PROTECTED] writes:
First maxusers was 0 then when changed it to 8.
That's a regression. Keep it at 0.
I understood that there is a bug on new kmem allocator and this was an
attempt to reduce kmem allocations but it didn't
On Wed, 10 Sep 2003, Michael Edenfield wrote:
* David O'Brien [EMAIL PROTECTED] [030910 15:33]:
On Wed, Sep 10, 2003 at 12:41:41PM -0400, Michael Edenfield wrote:
gnome2 depends on gnomemedia2.
gnomemedia2 depends on gstreamer-plugins.
gstreamer-plugins fails because ARTSD_FLAGS in
Tomi Vainio - Sun Finland [EMAIL PROTECTED] writes:
Dag-Erling Smørgrav writes:
Tomi Vainio - Sun Finland [EMAIL PROTECTED] writes:
First maxusers was 0 then when changed it to 8.
That's a regression. Keep it at 0.
I understood that there is a bug on new kmem allocator and this was an
Dag-Erling Smørgrav writes:
The backtrace you showed seems to indicate that the panic happened
somewhere in the softupdates code, but IIRC that code has a fairly
conservative built-in limit on memory consumption and degrades
gracefully when it hits that limit. It's likely that
TB --- 2003-09-10 19:49:21 - starting CURRENT tinderbox run for i386/pc98
TB --- 2003-09-10 19:49:21 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/i386/pc98
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-09-10 19:52:23 - building world
TB --- cd
[I'm not presently subscribed to this list so please CC me in any
replies. Thank you]
Hello,
I'm running 5.1-RELEASE-p2 and I just upgraded my machine from a PIII
800 MHz processor with 256 MB RAM to a PIV 2.4 GHz processor and VIA P4B
400 motherboard with 512 MB RAM. The system starts and
On Tue, Sep 09, 2003 at 08:37:17PM +0300, Lefteris Chatzibarbas wrote:
[...]
Most of the time the CDRW drive is not detected and I get:
[...]
After today's commit to src/sys/dev/ata/ata-lowlevel.c (1.11 2003/09/10
09:57:16 sos), the ata1-slave CDRW is always detected correctly:
atapci0:
I'm looking at a call to panic() at line 137 of vm/uma_dbg.c. The
panic string was panic: Most recently used by ACD driver. If the
ACD is the ATA CD driver, it was removed from this laptop (hot
swapped) some time ago. The laptop panic'd while it aparently had
many dirty buffers ... but while it
Tomi Vainio - Sun Finland [EMAIL PROTECTED] writes:
Second trace didn't have anything to do with fs only fork system calls
there so your expanation sounds reasonable. We probably don't see this
problem again because system now has enough memory (256M).
It would be really useful to know where
Dag-Erling Smørgrav writes:
It would be really useful to know where the fault lies. We might even
(God forbid!) figure out a way to fix it. You can easily force the
system to boot with less than the full amount of memory by setting
hw.physmem to e.g. 64m in /boot/loader.conf or at the
On Wed, 2003-09-10 at 14:14, Scott Reese wrote:
[I'm not presently subscribed to this list so please CC me in any
replies. Thank you]
Hello,
I'm running 5.1-RELEASE-p2 and I just upgraded my machine from a PIII
800 MHz processor with 256 MB RAM to a PIV 2.4 GHz processor and VIA P4B
400
On Wed, Sep 10, 2003 at 04:34:31PM -0700, Scott Reese wrote:
On Wed, 2003-09-10 at 14:14, Scott Reese wrote:
[I'm not presently subscribed to this list so please CC me in any
replies. Thank you]
Hello,
I'm running 5.1-RELEASE-p2 and I just upgraded my machine from a PIII
800 MHz
Steve Kargl wrote:
Why? The portmgr can tag the ports collection at any point in
time before or after the -pthread deprecation date.
Steve, ports-freeze dates are set and published ahead of time just as dates
for releases are. It's obviously not a good thing to have to try and be very
On Wed, 2003-09-10 at 16:40, Steve Kargl wrote:
On Wed, Sep 10, 2003 at 04:34:31PM -0700, Scott Reese wrote:
On Wed, 2003-09-10 at 14:14, Scott Reese wrote:
[I'm not presently subscribed to this list so please CC me in any
replies. Thank you]
Hello,
I'm running
Daniel Eischen wrote:
I feel that a FreeBSD that manages to break so many existing configure-scripts
and build systems is degraded in usefulness.
Please, this is -current. If you want less pain then stick
with -stable and you won't be annoyed by the -pthread removal.
Perhaps I should make it
On Tue, 9 Sep 2003, Peter Jeremy wrote:
On Mon, Sep 08, 2003 at 12:59:11PM +0200, Philipp Grau wrote:
Next problem is that /etc/rc.d/ntpd is evaluated before /etc/rc.d/devfs (see
the output of rcorder /etc/rc.d*) So the start of ntpd fails because it is
requires the devfs link. Ntpd likes to
On Wed, Sep 10, 2003 at 04:45:47PM -0700, Scott Reese wrote:
On Wed, 2003-09-10 at 16:40, Steve Kargl wrote:
On Wed, Sep 10, 2003 at 04:34:31PM -0700, Scott Reese wrote:
On Wed, 2003-09-10 at 14:14, Scott Reese wrote:
I'm running 5.1-RELEASE-p2 and I just upgraded my machine from a
On Thu, Sep 11, 2003 at 01:41:05AM +0200, Michael Nottebrock wrote:
Steve Kargl wrote:
Why? The portmgr can tag the ports collection at any point in
time before or after the -pthread deprecation date.
Steve, ports-freeze dates are set and published ahead of time just as dates
for
On Wed, 2003-09-10 at 17:22, Steve Kargl wrote:
On Wed, Sep 10, 2003 at 04:45:47PM -0700, Scott Reese wrote:
On Wed, 2003-09-10 at 16:40, Steve Kargl wrote:
On Wed, Sep 10, 2003 at 04:34:31PM -0700, Scott Reese wrote:
On Wed, 2003-09-10 at 14:14, Scott Reese wrote:
I'm running
FYI, a fresh cvsup from yesterdays sources causes a panic with atapicam
in the kernel. My previous kernel was before ATAng was imported.
Fatal trap 18: integer divide fault while in kernel mode
instruction pointer = 0x8:0xc03dcd5b
stack pointer = 0x10:0xd70977c0
frame pointer
today i tried to compile a snapshot of the kvirc program as of this snapshot
it doesnt know that -pthread is deprecated in freebsd go i edited the
configure script to make -pthread to -lkse seems to go well but when i run
it i get the following:
% kvirc
Fatal error 'Spinlock called when not
This is the first time I've tried to run -current on this little board.
Up-to-date RELENG_4 kernels run fine. The probe message (port memory) values
are the same.
On -current, the kernel gets up to the point in the fxp code where it is
supposedly doing a reset to a stable state and then it
47 matches
Mail list logo
