* Brooks Davis <[EMAIL PROTECTED]> [2002-10-22 16:55 -0700]:
> On Wed, Oct 23, 2002 at 01:48:14AM +0200, Gerhard H?ring wrote:
> > * Brooks Davis <[EMAIL PROTECTED]> [2002-10-22 15:01 -0700]:
> > > Are you running a current kernel at this point? If you aren't it's safe
> > > to say it won't work.
On Tue, Oct 22, 2002 at 01:21:09PM -0700, Terry Lambert
<[EMAIL PROTECTED]> wrote:
> > No, I'm doing exactly what I describe. Usual boot to multiuser, then
> > kill all of the processes not strictly necessary (seti, fetchmail,
> > sendmail, you-name-it), mount the smb share -ro from NT4 server, cd
On Tue, 22 Oct 2002, Seigo Tanimura wrote:
> Introduction:
>
> The I/O buffer of the kernel are currently allocated in buffer_map
> sized statically upon boot, and never grows. This limits the scale of
> I/O performance on a host with large physical memory. We used to tune
> NBUF to cope with th
Poul-Henning Kamp wrote:
[requesting 5.0 testers]
>If you don't have the machine-power to run make release yourself,
>I hope the japanese snapshot server is producing good snapshots,
>if that fails, I would appreciate if somebody will produce and put up
>good releases and/or ISO images somewhere.
If I understand correctly, the next opportunity after 5.0R to make a
change of such significance is FreeBSD 6.0. Since I suspect that few
folks will want to have ssh1 enabled by the time 6.0 is released, I
would like to request for the team to please consider disabling ssh1
fallback prior to 5.0R.
If memory serves me right, Kris Kennaway wrote:
> On Tue, Oct 22, 2002 at 10:28:42PM -0700, Kris Kennaway wrote:
>
> > > It's already in UPDATING with the rm -rf /usr/include/g++ line in the
> > > steps for going from 4 to -current.
> >=20
> > Oops, I missed this when I looked for it. Thanks.
>
On Tue, Oct 22, 2002 at 10:28:42PM -0700, Kris Kennaway wrote:
> > It's already in UPDATING with the rm -rf /usr/include/g++ line in the
> > steps for going from 4 to -current.
>
> Oops, I missed this when I looked for it. Thanks.
Actually, I think this is not sufficient..there will be other st
In message <[EMAIL PROTECTED]>, Craig Rodrigues writes:
>
>--sdtB3X0nJg68CQEu
>Content-Type: text/plain; charset=us-ascii
>Content-Disposition: inline
>
>On Tue, Oct 22, 2002 at 05:45:24PM -0400, Craig Rodrigues wrote:
>> Hi,
>>
>> I just did a cvsup and am trying to do a buildworld and
>> am havi
On Tue, Oct 22, 2002 at 03:08:10PM -0700, Nate Lawson wrote:
> On Tue, 22 Oct 2002, Kris Kennaway wrote:
> > On Tue, Oct 22, 2002 at 03:46:04PM -0400, Adam K Kirchhoff wrote:
> > >
> > > I recently (late last week) upgraded my machine from -stable to -current.
> >
> > When you upgraded, you presu
Hi Folks,
I've been running repetitive 'make release's on a box
and it died once (no serial console), and I finally got
it to crash again after about 2 days.
uname: (world and kernel up-to-date as of)
5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Oct 17 02:12:59 GMT 2002
df:
Filesystem 1K
I recently heard a comparison between Linux and FreeBSD that I found amusing.
It goes something like this:
How would you describe the differences between Linux and FreeBSD?
Ok. You've won a car. Completely free - no cost involved. Two Choices:
Daiwoo SunSport
twin-turbo, quad-cam, fuel-injected
Well, I'll send it to you or anyone else if you can provide me with the link
of what you want.
Only thing I ask is that an official Mesa 4.0.4 FSBD port makes it into the
5.0 release as well as the next 4.x release. ;o)
All I ask!
-K
__
* De: Wm Brian McCane <[EMAIL PROTECTED]> [ Data: 2002-10-22 ]
[ Subjecte: Re: 5.0-RUSH: -current install testers wanted! ]
> Wow, spooky, I used to live at:
>
> 8716 W 70th Terr
> Shawnee Mission, KS 66204
>
> Of course, that was back in the early 70's ;). Anyway, I might be
Wow, spooky, I used to live at:
8716 W 70th Terr
Shawnee Mission, KS 66204
Of course, that was back in the early 70's ;). Anyway, I might be able to
get you a copy if you want 1. I have a spare 5.0-DP somewhere at one of
my customers in Lenexa, or I could make a newer version.
* De: Alex Zepeda <[EMAIL PROTECTED]> [ Data: 2002-10-22 ]
[ Subjecte: Re: 5.0-RUSH: -current install testers wanted! ]
> On Tue, Oct 22, 2002 at 08:33:53AM +0200, Poul-Henning Kamp wrote:
>
> > And I want them to do it RSN: 5.0-R is only 9 days away.
>
> If the release is only 9 days awa
On Tue, Oct 22, 2002 at 08:29:01PM -0400, Craig Rodrigues wrote:
> --- sys/crypto/rijndael/rijndael-api-fst.c.orig Tue Oct 22 20:16:28 2002
> +++ sys/crypto/rijndael/rijndael-api-fst.cTue Oct 22 20:29:20 2002
> @@ -22,6 +22,7 @@
Hi,
I apologize. I had version 1.3 of rijndael-api-fst.c
On Tue, Oct 22, 2002 at 08:33:53AM +0200, Poul-Henning Kamp wrote:
> And I want them to do it RSN: 5.0-R is only 9 days away.
If the release is only 9 days away, what will be done about the signal/FPU
register stuff? As it stands, [x]emacs still hangs often enough, and KDE
managed to destabilize
I hope this problem is fixed now. Let me know if I am sadly mistaken
about that :)
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
In the last episode (Oct 23), Daniel Rock said:
> Daniel Rock schrieb:
> >I found an interesting problem during tracing my perl-5.8 problem I
> >mailed some days ago.
> >
> >Sometimes - I cannot forcibly reproduce this event - while I'm
> >trying to truss a process, I first get the following error
Lars Eggert wrote:
Hi,
the following produces a bootable CF card under 4.7:
dd if=/dev/zero of=/dev/da2 bs=512 count=32
fdisk -BI da2
disklabel -w -B da2s1 auto
disklabel -r da2s1 > /tmp/da2s1
Turns out that the "disklabel -r" output after this step differs between
-current a
On Tue, Oct 22, 2002 at 05:45:24PM -0400, Craig Rodrigues wrote:
> Hi,
>
> I just did a cvsup and am trying to do a buildworld and
> am having a problem:
>
>
>=
* Brooks Davis <[EMAIL PROTECTED]> [2002-10-22 15:01 -0700]:
> On Tue, Oct 22, 2002 at 11:52:11PM +0200, Gerhard Häring wrote:
> > * Ruslan Ermilov <[EMAIL PROTECTED]> [2002-10-22 12:23 +0300]:
> > > On Tue, Oct 22, 2002 at 04:25:23AM +0200, Gerhard Haering wrote:
> > > > Is it possible, or do I ne
Hi,
the following produces a bootable CF card under 4.7:
dd if=/dev/zero of=/dev/da2 bs=512 count=32
fdisk -BI da2
disklabel -w -B da2s1 auto
disklabel -r da2s1 > /tmp/da2s1
disklabel -r da2s1 | grep ' c:' | sed 's/c:/a:/' >> /tmp/da2s1
disklabel -R -B da2s1 /tmp/da2s1
newfs /dev/da2s1a
W
On Wed, Oct 23, 2002 at 01:48:14AM +0200, Gerhard Häring wrote:
> * Brooks Davis <[EMAIL PROTECTED]> [2002-10-22 15:01 -0700]:
> > Are you running a current kernel at this point? If you aren't it's safe
> > to say it won't work.
>
> No, this is 4.5-RELEASE, as I said. By "current kernel", do you
I'm running a 5.0-CURRENT from earlier this morning and receive this
notice:
/usr/src/sys/kern/kern_sysctl.c:1000: could sleep with "drm memory" locked from
@/dev/drm/drm_memory.h:217
I have 'device agp' in my kernel and I've got mga.ko loaded. The notice
is raised when doing 'sysctl -a'.
If I
John Baldwin wrote:
On 22-Oct-2002 walt wrote:
Alexander Kabaev wrote:
On Tue, 22 Oct 2002 11:08:29 -0700
walt <[EMAIL PROTECTED]> wrote:
I'm confused about the -CURRENT emacs breakage...
...could be worked around by linking
[x]emacs binary with -znocombreloc.
Hmm. I tried make LDFL
Mike Barcroft wrote:
> > > This is because we lack the
> > >
> > > long double fabsl(long double);
> > >
> > > in -lm and .
> >
> > OK, thanks for tracking it down. This looks like an important
> > omission that should be fixed for 5.0-R.
>
> No one has started work on any of the C99 math functio
Daniel Rock schrieb:
Hi,
I found an interesting problem during tracing my perl-5.8 problem I
mailed some days ago.
Sometimes - I cannot forcibly reproduce this event - while I'm trying
to truss a process, I first get the following error message:
/usr/ports/lang/perl5.8/work/perl-5.8.0# truss
Hi,
I found an interesting problem during tracing my perl-5.8 problem I
mailed some days ago.
Sometimes - I cannot forcibly reproduce this event - while I'm trying to
truss a process, I first get the following error message:
/usr/ports/lang/perl5.8/work/perl-5.8.0# truss ./perl
truss: cannot o
On Tue, 22 Oct 2002, Kris Kennaway wrote:
> On Tue, Oct 22, 2002 at 03:46:04PM -0400, Adam K Kirchhoff wrote:
> >
> > I recently (late last week) upgraded my machine from -stable to -current.
>
> When you upgraded, you presumably didn't clear out stale headers from
> /usr/include. This needs to
On Tue, Oct 22, 2002 at 11:52:11PM +0200, Gerhard Häring wrote:
> * Ruslan Ermilov <[EMAIL PROTECTED]> [2002-10-22 12:23 +0300]:
> > On Tue, Oct 22, 2002 at 04:25:23AM +0200, Gerhard Haering wrote:
> > > Is it possible, or do I need to use a more recent installation to be able to
> > > build -CURRE
On Tue, Oct 22, 2002 at 10:23:06AM -0700, Lars Eggert wrote:
> Bernd Walter wrote:
>
> >It's just the Name that don't exist.
> >Some time ago I was told to just open the device even if there is no
> >node listable in /dev.
> >E.g. mount_msdosfs /dev/da2s1 /mnt
>
> Yes, this works (Terry also poin
* Ruslan Ermilov <[EMAIL PROTECTED]> [2002-10-22 12:23 +0300]:
> On Tue, Oct 22, 2002 at 04:25:23AM +0200, Gerhard Haering wrote:
> > Is it possible, or do I need to use a more recent installation to be able to
> > build -CURRENT?
> >
> Yes, it is. It should even be possible to build -CURRENT wit
On Tue, Oct 22, 2002 at 03:46:04PM -0400, Adam K Kirchhoff wrote:
>
> I recently (late last week) upgraded my machine from -stable to -current.
When you upgraded, you presumably didn't clear out stale headers from
/usr/include. This needs to be added as a step in UPDATING because it
will bite ev
Hi,
I just did a cvsup and am trying to do a buildworld and
am having a problem:
===
===> sbin/gbde
cc -O -pipe -mcpu=pentiumpro -I/u
Kris Kennaway <[EMAIL PROTECTED]> writes:
> On Tue, Oct 22, 2002 at 11:22:41AM +0300, Ruslan Ermilov wrote:
> > On Sat, Oct 19, 2002 at 07:54:01PM -0700, Kris Kennaway wrote:
> > > World is broken if you try and build with -fno-builtin:
> > >
> > > c++ -O -pipe -ggdb -fno-builtin -march=pentium3
pcic doesn't work with NEWCARD. I'm working on it..
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
* De: [EMAIL PROTECTED] [ Data: 2002-10-22 ]
[ Subjecte: Re: 5.0-RUSH: -current install testers wanted! ]
> On Tue, Oct 22, 2002 at 10:39:32PM +0200, Poul-Henning Kamp wrote:
> >
> > That is intentional
> >
>
> Is it ok then that the sysinstall in /stand of the 0917-JPSNAP
> immediately
On Tue, Oct 22, 2002 at 04:40:12PM -0400, Brian F. Feldman wrote:
> For what it's worth; I'm also using a dual-Athlon that gets spontaneous
> reboots once in a while and seems like it could possibly have to do with
> ACPI activating while the system is trying to cool itself down. Do you have
>
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
libstdc++ is supposed to provide crude replacements for missing -l functions
in its libmath/stubs.c file. Apparently, missing fabsl is an omission and
should be fixed in FSF sources.
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body
Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> .de writes:
> >
> >Is sysinstall still supposed to copy the contents of the mfsroot-
> >image to /stand ? This at least results in two copies of sysinstall,
> >one in /stand and the other one in /usr/sbin.
>
> That is i
In message <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
.de writes:
>On Tue, Oct 22, 2002 at 10:39:32PM +0200, Poul-Henning Kamp wrote:
>>
>> That is intentional
>>
>
>Is it ok then that the sysinstall in /stand of the 0917-JPSNAP
>immediately dumps core with signal 10 when run on a 1017 -current ?
Cu
On Tue, Oct 22, 2002 at 10:39:32PM +0200, Poul-Henning Kamp wrote:
>
> That is intentional
>
Is it ok then that the sysinstall in /stand of the 0917-JPSNAP
immediately dumps core with signal 10 when run on a 1017 -current ?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freeb
On 22-Oct-2002 walt wrote:
> Alexander Kabaev wrote:
>> On Tue, 22 Oct 2002 11:08:29 -0700
>> walt <[EMAIL PROTECTED]> wrote:
>>
>>
>>>I'm confused about the -CURRENT emacs breakage...
>
>> ...The code
>> in [x]emacs is not prepared to deal with the change in format and thus will
>> have to be
On Tue, Oct 22, 2002 at 01:28:56PM -0700, Terry Lambert wrote:
> Stefan Farfeleder wrote:
> [ ... fabsl() ... ]
> > > What standard defines this thing, which g++ has as a built-in?
> > >
> > > Alternately, the use could avoid adding the "-fno-builtin", and
> > > the problem would go away.
> >
> >
For what it's worth; I'm also using a dual-Athlon that gets spontaneous
reboots once in a while and seems like it could possibly have to do with
ACPI activating while the system is trying to cool itself down. Do you have
any more hints here on where the problem may lie so I can attempt to track
In message <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
.de writes:
>
>Is sysinstall still supposed to copy the contents of the mfsroot-
>image to /stand ? This at least results in two copies of sysinstall,
>one in /stand and the other one in /usr/sbin.
That is intentional
--
Poul-Henning Kamp |
Kris Kennaway wrote:
> Yes, because as it stands this function is supplied by gcc as a
> built-in function, and the source tree will not compile without it
> (e.g. with a non-gcc compiler).
>
> > Alternately, the use could avoid adding the "-fno-builtin", and
> > the problem would go away.
>
> -f
Is sysinstall still supposed to copy the contents of the mfsroot-
image to /stand ? This at least results in two copies of sysinstall,
one in /stand and the other one in /usr/sbin.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Stefan Farfeleder wrote:
[ ... fabsl() ... ]
> > What standard defines this thing, which g++ has as a built-in?
> >
> > Alternately, the use could avoid adding the "-fno-builtin", and
> > the problem would go away.
>
> ISO C99
>
> 7.12.7.2 The fabs functions
> Synopsis
> #include
> doubl
If memory serves me right, Steve Kargl wrote:
> I've noticed many commits on cvs-all include an "Approved by: re"
> line, but I haven't seen an official code slush/freeze announcement.
Feature freeze started 16 October. New feature commits (as opposed to
bugfix or doc commits) should have RE ap
Alexander Kabaev wrote:
On Tue, 22 Oct 2002 11:08:29 -0700
walt <[EMAIL PROTECTED]> wrote:
I'm confused about the -CURRENT emacs breakage...
...The code
in [x]emacs is not prepared to deal with the change in format and thus will
have to be fixed, or the while issue could be worked around by
Vallo Kallaste wrote:
> > It would be nice if you could give us more information as to exactly
> > what it is you are doing, logically, to cause this problem; as things
> > sit, it seems you are doing some evil things.
>
> No, I'm doing exactly what I describe. Usual boot to multiuser, then
> kill
On Tue, Oct 22, 2002 at 12:40:38PM -0700, Terry Lambert wrote:
> Is it?
Yes, because as it stands this function is supplied by gcc as a
built-in function, and the source tree will not compile without it
(e.g. with a non-gcc compiler).
> Alternately, the use could avoid adding the "-fno-builtin",
On Tue, Oct 22, 2002 at 01:07:50PM -0700, Bruce A. Mah wrote:
> If memory serves me right, The Anarcat wrote:
> > On Tue Oct 22, 2002 at 08:33:53AM +0200, Poul-Henning Kamp wrote:
> > >
> > > And I want them to do it RSN: 5.0-R is only 9 days away.
> >
> > 9 days??? There won't be another DP?
>
On Tue, Oct 22, 2002 at 12:40:38PM -0700, Terry Lambert wrote:
> Kris Kennaway wrote:
> > > > /usr/src/contrib/gperf/src/bool-array.icc:81: warning: rand() does not produce
>high-quality random numbers and should not generally be used
> > > > /usr/obj/usr/src/i386/usr/lib/libstdc++.so: undefined r
If memory serves me right, The Anarcat wrote:
> On Tue Oct 22, 2002 at 08:33:53AM +0200, Poul-Henning Kamp wrote:
> [...]
> >
> > And I want them to do it RSN: 5.0-R is only 9 days away.
> [...]
>
> 9 days??? There won't be another DP?
Um, not exactly. The current release date isn't until 20 No
On Tue Oct 22, 2002 at 08:33:53AM +0200, Poul-Henning Kamp wrote:
[...]
>
> And I want them to do it RSN: 5.0-R is only 9 days away.
[...]
9 days??? There won't be another DP?
A.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Tue, Oct 22, 2002 at 12:15:09PM -0700, Terry Lambert
<[EMAIL PROTECTED]> wrote:
> > #14 0xc455a66e in ?? ()
> > #15 0xc455a072 in ?? ()
> > #16 0xc4559e87 in ?? ()
> > #17 0xc45609f8 in ?? ()
>
> If you are running the smbfs.ko, either load the module symbols into
> gdb before asking for the t
I recently (late last week) upgraded my machine from -stable to -current.
I immediately had an issue with __sF errors from various libraries and saw
that it was fixed as of this past weekend, so I cvsuped and made world
yesterday morning, too.
Knowing that c++ apps would start to break till they
Kris Kennaway wrote:
> > > /usr/src/contrib/gperf/src/bool-array.icc:81: warning: rand() does not produce
>high-quality random numbers and should not generally be used
> > > /usr/obj/usr/src/i386/usr/lib/libstdc++.so: undefined reference to `fabsl'
> > > *** Error code 1
> > >
> > This is because
I have two \\_SB_.PCI0 related warnings being output at boot. The one
about AE_BAD_DATA is fairly recent, but I don't know what kernel it
appeared with. I moved recently and haven't have a smooth upgrade path.
The FDC0 - AE_AML_UNINITIALIZED_LOCAL warning has been around for some time.
Copyrigh
On Tue, 22 Oct 2002 11:08:29 -0700
walt <[EMAIL PROTECTED]> wrote:
> I'm confused about the -CURRENT emacs breakage. Is this
> an O.S. breakage which will eventually be fixed, or a
> permanent change which will require a patch to emacs?
>
> Thanks.
This is a permanent change. The new binutils d
On Tue, 22 Oct 2002, Seigo Tanimura wrote:
> Introduction:
>
[...]
>
> The patch at:
>
> http://people.FreeBSD.org/~tanimura/patches/dynamicbuf.diff.gz
Cool..
>
>
> -jbaselinew/ my patch
> realusersys realusersys
> 1 1608.21 1387.94 125.9
Vallo Kallaste wrote:
> On Tue, Oct 22, 2002 at 04:23:20AM -0700, Maxime Henrion
> <[EMAIL PROTECTED]> wrote:
>
> [snip]
> > It would help a lot if you could provide a traceback.
>
> This is the one I'm seeing everytime while trying to copy file from
> ro smbfs mount. -current is about four days
--On mardi 22 octobre 2002 10:08 +0100 Ceri Davies <[EMAIL PROTECTED]>
wrote:
> On Tue, Oct 22, 2002 at 08:33:53AM +0200, Poul-Henning Kamp wrote:
>
>> If you don't have the machine-power to run make release yourself,
>> I hope the japanese snapshot server is producing good snapshots,
>> if tha
On 22-Oct-2002 Vallo Kallaste wrote:
> On Tue, Oct 22, 2002 at 10:48:58AM -0400, John Baldwin <[EMAIL PROTECTED]> wrote:
>
>> Can you compile smbfs into your kernel 'options SMBFS' instead of as a
>> module and then get a dump and provide a trace?
>
>> >#13 0xc0383f58 in calltrap () at {standard
On Tue, Oct 22, 2002 at 11:22:41AM +0300, Ruslan Ermilov wrote:
> On Sat, Oct 19, 2002 at 07:54:01PM -0700, Kris Kennaway wrote:
> > World is broken if you try and build with -fno-builtin:
> >
> > c++ -O -pipe -ggdb -fno-builtin -march=pentium3
>-I/usr/src/gnu/usr.bin/gperf/../../../contrib/g
I'm confused about the -CURRENT emacs breakage. Is this
an O.S. breakage which will eventually be fixed, or a
permanent change which will require a patch to emacs?
Thanks.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
hi, there!
cross-building -CURRENT on RELENG_4 is broken in src/usr.bin/xlint/lint1:
--- cut here ---
...
sh /usr/fbsd/HEAD/src/usr.bin/xlint/lint1/makeman /usr/libexec/lint1 -m >lint.7
lint1: illegal option -- m
usage: lint1 [-abcdeghprstuvyzF] src dest
gzip -cn lint.7 > lint.7.gz
--- cut here -
On Tue, Oct 22, 2002 at 10:48:58AM -0400, John Baldwin <[EMAIL PROTECTED]> wrote:
> Can you compile smbfs into your kernel 'options SMBFS' instead of as a
> module and then get a dump and provide a trace?
> >#13 0xc0383f58 in calltrap () at {standard input}:99
> >#14 0xc455a66e in ?? ()
> >#15 0x
Last week I replace a broken mainboard with a dual-Athlon one (Tyan
Tiger s2466n-4m) and decided to upgrade that box from 4-stable to
-current by installing the 0917-jpsnap via the floppies and passive
ftp. I hit several sysinstall-problems some of which my already be
fixed:
- The hd I install -c
Bernd Walter wrote:
It's just the Name that don't exist.
Some time ago I was told to just open the device even if there is no
node listable in /dev.
E.g. mount_msdosfs /dev/da2s1 /mnt
Yes, this works (Terry also pointed this out.) I wish this could be
wired to the media change signal somehow.
Alexander Kabaev writes:
> On Tue, 22 Oct 2002 11:39:43 -0400
> Alexander Kabaev <[EMAIL PROTECTED]> wrote:
>
> > Anyone cares to post a ktrace?
> >
> > --
> > Alexander Kabaev
>
> If this is a case of a brk(2) failing, then I have a patch in testing to fix
> that. Give me some time
On Tue, 22 Oct 2002 11:39:43 -0400
Alexander Kabaev <[EMAIL PROTECTED]> wrote:
> Anyone cares to post a ktrace?
>
> --
> Alexander Kabaev
If this is a case of a brk(2) failing, then I have a patch in testing to fix
that. Give me some time to finish.
--
Alexander Kabaev
To Unsubscribe: send m
Anyone cares to post a ktrace?
--
Alexander Kabaev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
>From a tree that I updated last night, building on a 4.7-stable
system:
as -o boot2.o boot2.s
as --defsym SIOPRT=0x3f8 --defsym SIOFMT=0x3 --defsym SIOSPD=9600
/home/imp/FreeBSD/src/sys/boot/i386/boot2/sio.s -o sio.o
ld -nostdlib -static -N -Ttext 0x2000 -o boot2.out
/usr/obj/home/imp/Fre
Ruslan Ermilov writes:
> Well, I tried this on beast. It is easily reproduceable.
>
> It turned out that if you build groff with -DNO_CPU_CFLAGS
> (the way it is built during the bootstrap-tools stage of
> buildworld), it fails with the `out of memory' error in
> contrib/groff/src/libs/lib
On Tue, Oct 22, 2002 at 05:29:29PM +0300, Ruslan Ermilov wrote:
> On Mon, Oct 21, 2002 at 02:10:01PM -0400, Andrew Gallatin wrote:
> >
> > Ruslan,
> >
> > Can you help with this, please? I think you're the best candidate
> > since you know so much about the build system and you are the groff
>
On Tue, Oct 22, 2002 at 11:59:54PM +1000, Tim Robbins wrote:
> It seems groff is failing to format most of the roff documentation
> in src/share/doc, for example psd/15.yacc. Here is the output
> that groff -Tascii -ms produces on -current:
>
> ss..:44: warning: number register `0:LL' not defined
At the request of another developer who has since been swamped and
unable to actually test it, I converted the rc(4) driver over to
new-bus. If anyone can test it I would appreciate it. Download
the tarball http://www.FreeBSD.org/~jhb/patches/rc.tgz and unpack
it into a -current kernel source tre
On Tue, Oct 22, 2002 at 10:45:52AM -0400, Andrew Gallatin wrote:
>
> Ruslan Ermilov writes:
> > If you remove -fno-exceptions from gnu/usr.bin/groff/Makefile.inc and
> > recompile libgroff and groff, it seems to work (I did not check it
> > thoroughly). But I think this only has a side effect,
On (2002/10/22 10:48), John Baldwin wrote:
> > This is the one I'm seeing everytime while trying to copy file from
> > ro smbfs mount. -current is about four days old, smbfs.ko _is_
> > compiled with -DSMP and in sync with kernel.
>
> Can you compile smbfs into your kernel 'options SMBFS' instead
On 22-Oct-2002 Vallo Kallaste wrote:
> On Tue, Oct 22, 2002 at 04:23:20AM -0700, Maxime Henrion
> <[EMAIL PROTECTED]> wrote:
>
> [snip]
>> It would help a lot if you could provide a traceback.
>
> This is the one I'm seeing everytime while trying to copy file from
> ro smbfs mount. -current is a
Ruslan Ermilov writes:
> If you remove -fno-exceptions from gnu/usr.bin/groff/Makefile.inc and
> recompile libgroff and groff, it seems to work (I did not check it
> thoroughly). But I think this only has a side effect, because Groff
> does not seem to have any exception code (please correct
On Tue, Oct 22, 2002 at 04:23:20AM -0700, Maxime Henrion
<[EMAIL PROTECTED]> wrote:
[snip]
> It would help a lot if you could provide a traceback.
This is the one I'm seeing everytime while trying to copy file from
ro smbfs mount. -current is about four days old, smbfs.ko _is_
compiled with -DSMP
On Mon, Oct 21, 2002 at 02:10:01PM -0400, Andrew Gallatin wrote:
>
> Ruslan,
>
> Can you help with this, please? I think you're the best candidate
> since you know so much about the build system and you are the groff
> maintainer.
>
> I've found that if I just cd to /usr/src/share/doc and
> d
Noticed a bunch of:
> Expensive timeout(9) function: 0xc0170e40(0xc274c000) 0.001114387
from running (yesterday's) -CURRENT, so I thought I'd check against
(yesterday's kernel.debug (before I replaced it with today's).
Per "nm -lan kernel.debug", I see:
c0170420 T an_attach/usr/src/sys/dev/
It seems groff is failing to format most of the roff documentation
in src/share/doc, for example psd/15.yacc. Here is the output
that groff -Tascii -ms produces on -current:
ss..:44: warning: number register `0:LL' not defined
ss..:44: warning: number register `0:ri' not defined
ss..:44: warning:
In message <[EMAIL PROTECTED]>, "Kyle R.Green" wr
ites:
>Hello.
>
>I downloaded the floppies for 5.0-20021021-SNAP from ftp2.freebsd.org.
>
>When I perform the install it complains a few times about not being
>able to create /tmp, due to a read-only filesystem, and, later in the
>install, cannot
Hello.
I downloaded the floppies for 5.0-20021021-SNAP from ftp2.freebsd.org.
When I perform the install it complains a few times about not being
able to create /tmp, due to a read-only filesystem, and, later in the
install, cannot write /etc/resolv.conf, stopping the install dead in
its track
In message <[EMAIL PROTECTED]>, Vitaly Markitantov writes:
>Where i can found performance comparison of -CURRENT over -STABLE systems?
Very little has been done yet, -CURRENT is not expected to perform
particularly well until more of the kernel is out from under the
Giant lock.
--
Poul-Henning
On 22-Oct-2002 Vitaly Markitantov wrote:
> When i tries to copy a file from smbfs share mounted by mount_smbfs
> i get an error:
> cp: ./filename: Bad address
>
> But when i copy a file to share i get kernel panic like this:
>
> Fatal trap 12: page fault while in kernel mode
> fault virtual a
Where i can found performance comparison of -CURRENT over -STABLE systems?
--
Vitaly Markitantov mailto: [EMAIL PROTECTED]
icq: 117438950 phone: (062)332-23-90
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Vitaly Markitantov wrote:
> When i tries to copy a file from smbfs share mounted by mount_smbfs
> i get an error:
> cp: ./filename: Bad address
>
> But when i copy a file to share i get kernel panic like this:
>
> Fatal trap 12: page fault while in kernel mode
> fault virtual address=
On Tue, Oct 22, 2002 at 02:01:35PM +0300, Vitaly Markitantov
<[EMAIL PROTECTED]> wrote:
> When i tries to copy a file from smbfs share mounted by mount_smbfs
> i get an error:
> cp: ./filename: Bad address
>
> But when i copy a file to share i get kernel panic like this:
>
> Fatal trap 12: pag
When i tries to copy a file from smbfs share mounted by mount_smbfs
i get an error:
cp: ./filename: Bad address
But when i copy a file to share i get kernel panic like this:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x0
fault code = supervisor write,
In message <[EMAIL PROTECTED]>, Seigo Tanimur
a writes:
>The patch at:
>
>http://people.FreeBSD.org/~tanimura/patches/dynamicbuf.diff.gz
>Comments and flames are welcome. Thanks a lot.
This looks very very interesting!
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED]
Introduction:
The I/O buffer of the kernel are currently allocated in buffer_map
sized statically upon boot, and never grows. This limits the scale of
I/O performance on a host with large physical memory. We used to tune
NBUF to cope with that problem. This workaround, however, results in
a lot
1 - 100 of 115 matches
Mail list logo
