At 11:43 PM -0700 11/23/02, M. Warner Losh wrote:
In message: <[EMAIL PROTECTED]>
Giorgos Keramidas <[EMAIL PROTECTED]> writes:
: The one case (so far) where this seemed to make a difference
: was libposix1e. It was disconnected from the build by revision
: 1.119 of src/lib/Makefile b
On Mon, Nov 18, 2002 at 12:24:51PM +0100, Miguel Mendez wrote:
> See attached patch, haven't tested on -STABLE tho, sorry, only have -CURRENT now.
Committed, thanks!
Kris
msg47366/pgp0.pgp
Description: PGP signature
In message: <[EMAIL PROTECTED]>
Giorgos Keramidas <[EMAIL PROTECTED]> writes:
: On 2002-11-23 21:13, "M. Warner Losh" <[EMAIL PROTECTED]> wrote:
: > I've never ever needed to cleanup lib. Are you sure that's absolutely
: > required? Also, for upgrading from 4.x already has the bit abo
On 2002-11-23 21:13, "M. Warner Losh" <[EMAIL PROTECTED]> wrote:
> I've never ever needed to cleanup lib. Are you sure that's absolutely
> required? Also, for upgrading from 4.x already has the bit about
> nuking /usr/include/gcc. I've never needed to do more. What
> libraries are bad that need
Vallo Kallaste wrote:
> On Sat, Nov 23, 2002 at 02:52:27PM -0800, Terry Lambert
> <[EMAIL PROTECTED]> wrote:
> > > Somebody with knowledge and time should generate patches, so it's
> > > possible to at least test and report problems (or success). Given
> > > that enough people give it a try and rep
On Sat, 23 Nov 2002, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Bruce Evans <[EMAIL PROTECTED]> writes:
> : 56k is a silly speed to use. Why not use the normal speed of 57600
> : bps or the faster speed of 115200 bps? I haven't got around to updating
> : the 57600 in t
David O'Brien wrote:
On Sat, Nov 23, 2002 at 07:26:00PM +0100, Miguel Mendez wrote:
Yes, thanks for the info, FWIW I think it's quite against POLA to remove
an option yet keep it documented in the man page :)
The man pages are from 2.95 because the 3.x ones require Perl 5.6 +
texinfo to build
I've never ever needed to cleanup lib. Are you sure that's absolutely
required? Also, for upgrading from 4.x already has the bit about
nuking /usr/include/gcc. I've never needed to do more. What
libraries are bad that need to be removed, specifically? Or is this
just paranoia inspired?
Warner
On Sun, Nov 24, 2002 at 02:34:40PM +1100, Tim Robbins wrote:
> I'd appreciate it if the people who were experiencing problems with
> smbfs could try this patch and let me know how it goes.
>
> The patch adds two sysctls, net.smb.readwritex and net.smb.reqdatasize.
> readwritex controls whether LA
Belling the cat comes from a children's story, and is often referenced in
behavioral economics and game theory. The story goes, the mice decide that
life would be much safer if the cat were stuck with a bell around its neck.
This way the mice would hear the cat approaching. The problem is, which
I'd appreciate it if the people who were experiencing problems with
smbfs could try this patch and let me know how it goes.
The patch adds two sysctls, net.smb.readwritex and net.smb.reqdatasize.
readwritex controls whether LARGE_READX and LARGE_WRITEX requests are
used, and is off by default. req
At 1:53 AM +0200 2002/11/24, Vallo Kallaste wrote:
But who will bell the cat? I vote for Snuffles.
Don't understand. Some inside joke or something based on US centric
TV? What are you trying to tell me? Remember I'm not native.
I am a native US citizen (well, caucasian ;-), and I don't g
At 1:04 PM -0800 2002/11/23, Nate Lawson wrote:
I'd like to see this on in 5.0 for a while, given the number of new users
and problem reports we are already getting and will soon get even more of.
If it's too hard to complete this work, could we add DDB in by default in
GENERIC? (I shudder t
Hi,
forget what i wrote about the acpi stuff, it's triggered by ntpd.
Removing the ntpd options from rc.conf let's me boot through
just fine.
Slab at 0xc282ffc8, freei 23 = 0
panic: Dublicate free of item 0xc282fb80 from zone 0xc0e8d00(128)
Debugger("panic")
Stopped at Debugger+0x54: xchg
At 10:39 PM -0800 2002/11/22, Terry Lambert wrote:
In terms of kernel problems, the absolutely most useful information
is the DDB traceback, followed by a DDB traceback mapped against a
debug kernel, followed by a system dump image and a debug kernel, etc..
By default, the system, as distribu
On Sat, Nov 23, 2002 at 10:17:14AM -0500, Robert Watson wrote:
>
> On Sat, 23 Nov 2002, Christian Brueffer wrote:
>
> > just got this panic on my notebook. Had to manually shut it down after a
> > acpiconf -s 4. At the next bootup, the panic occured. At the moment I'm
> > trying to boot into my
Hi all,
I am trying to fix my ports to be built on -current. Almost all
problems are gone(fix/update/etc...). But I have problem of korean/byeoroo
ports. Can somebody look at more closer?
http://bento.freebsd.org/errorlogs/5-full/ko-byeoroo-0.0.19990605.3_1.log
The problem is that two header
Hi all,
I am trying to fix my ports to be built on -current. Almost all
problems are gone(fix/update/etc...). But I have problem of korean/byeoroo
ports. Can somebody look at more closer?
http://bento.freebsd.org/errorlogs/5-full/ko-byeoroo-0.0.19990605.3_1.log
The problem is that two header
Marc Recht wrote:
>
> > Can you re-cvsup and update just to make sure everything is current?
> I did cvsup everything.
>
> > Every place that pmap_remove_all() is called appears to hold the page
> > queue mutex. The only exception is long-broken code that is compiled
> > under ENABLE_VFS_IOOPT.
Robert Watson writes:
>
> On Thu, 21 Nov 2002, Luigi Rizzo wrote:
<...>
> > The label is 5 ints, the pkthdr a total of 11 ints (and m_hdr takes
> > another 6, for a total of 136 bytes of header info on 64-bit
> > architectures).
> >
> > Of the pkthdr, only 3 fields (rcvif, len, tags) a
On Sat, Nov 23, 2002 at 07:26:00PM +0100, Miguel Mendez wrote:
> Yes, thanks for the info, FWIW I think it's quite against POLA to remove
> an option yet keep it documented in the man page :)
The man pages are from 2.95 because the 3.x ones require Perl 5.6 +
texinfo to build. So we either (1) to
On Sat, Nov 23, 2002 at 02:52:27PM -0800, Terry Lambert
<[EMAIL PROTECTED]> wrote:
> > Somebody with knowledge and time should generate patches, so it's
> > possible to at least test and report problems (or success). Given
> > that enough people give it a try and report, there's possibility for
>
Vallo Kallaste wrote:
> On Fri, Nov 22, 2002 at 10:03:50AM -0800, David O'Brien
> > I would like to see GCC 3.2.1 release be our 5.0-R compiler. However,
> > the GCC 3.2.1 release date kept slipping and in fact was nebulous for a
> > while. The same for our 5.0-R. So this has made it hard to dec
Can you re-cvsup and update just to make sure everything is current?
I did cvsup everything.
Every place that pmap_remove_all() is called appears to hold the page
queue mutex. The only exception is long-broken code that is compiled
under ENABLE_VFS_IOOPT.
ENABLE_VFS_IOOPT (vfs.ioopt=1) was the
Marc Recht wrote:
>
> Hi!
>
> I got this with the latest pmap.c
> Nov 23 17:43:07 leeloo kernel: panic: mutex vm page queue mutex not owned
> at ../../../i386/i386/pmap.c:1881
> Nov 23 17:43:07 leeloo kernel:
> Nov 23 17:43:07 leeloo kernel: syncing disks, buffers remaining... panic:
> bremfree:
On Sat, 23 Nov 2002, Mike Barcroft wrote:
> Nate Lawson <[EMAIL PROTECTED]> writes:
> > On Sat, 23 Nov 2002, Brad Knowles wrote:
> > > At 2:31 PM -0800 2002/11/22, Terry Lambert wrote:
> > >
> > > > A "bug-filing wizard" would be useful. The "send-pr" system
> > > > doesn't cut it, and most peo
In message: <[EMAIL PROTECTED]>
Bruce Evans <[EMAIL PROTECTED]> writes:
: 56k is a silly speed to use. Why not use the normal speed of 57600
: bps or the faster speed of 115200 bps? I haven't got around to updating
: the 57600 in the example in /etc/rc.serial although this example bec
Sat Nov 23 13:00:03 PST 2002
U release/doc/en_US.ISO8859-1/hardware/alpha/proc-alpha.sgml
U share/man/man4/Makefile
U share/man/man4/syncache.4
? sys/alpha/conf/LINT
U sys/kern/vfs_bio.c
cvs [update aborted]: cannot make directory include: File exists
To Unsubscribe: send mail to [EMAIL PROTECTED]
Hi!
I got this with the latest pmap.c
Nov 23 17:43:07 leeloo kernel: panic: mutex vm page queue mutex not owned
at ../../../i386/i386/pmap.c:1881
Nov 23 17:43:07 leeloo kernel:
Nov 23 17:43:07 leeloo kernel: syncing disks, buffers remaining... panic:
bremfree: bp 0xd359d584 not locked
Nov 23 17:
Ack! ^M sends the email. continuing . . .
I came home last night and found my system Hard Locked.
I have a serial console hooked up and used CR~^B to break
into ddb and tried a few things. The previous message
has a log of everything.
Drats! I was hoping that the Hard Locks were gone.
1.) D
I came home last night and found the system Hard Locked.
^
Stopped at siointr1+0xf4: movl$0,brk_state1.0
db>
db> show locks
db> ps
pid proc addruid ppid pgrp flag stat wmesgwchan
cmd
71987 c3557000 d364b000 1006 71985 71985 0004000 norm[LOCK Giant
c03d01a0] for
On Sat, Nov 23, 2002 at 07:26:00PM +0100, Miguel Mendez wrote:
> On Sat, 23 Nov 2002 18:21:09 +0100
> Jens Rehsack <[EMAIL PROTECTED]> wrote:
>
> > You may also read http://gcc.gnu.org/ for details 'bout the new
> > compiler and http://gcc.gnu.org/news/profiledriven.html for
> > information about
On Sat, 23 Nov 2002 18:21:09 +0100
Jens Rehsack <[EMAIL PROTECTED]> wrote:
Hi,
> The "-ax" option generates code for profiling. The "-ax" options
> doesn't appears in the current info documentation, which is an actual
> one (AFAIK). So I assume, "-ax" is not supported anymore.
So the man page ne
> > consider devd. It is somewhat incomplete in DP2, but complete enough
> > for this.
> Thanks, I'll try it.
Is there any documentation for devd.conf? The man page is incomplete
(it only describes the syntax of comments, though admittedly it does
that in great detail) and there's no default /e
On Sat, Nov 23, 2002 at 06:03:17AM +0200, Giorgos Keramidas wrote:
> I tried to get myself a clean /usr/{include,lib} installation after a
> successful buildworld earlier. To make this as clean an installation
> as possible, I did the following before running "make installworld":
>
> # cd /
On 2002-11-23 10:36, Mark Murray <[EMAIL PROTECTED]> wrote:
> > Apparently editors/vim-lite had picked up an old, obsolete libposix*.so
> > from one of the past installations and linked against that. Deleting
> > the port and reinstalling it worked like a charm, which made me think
> > a bit... S
> That's because pccardc and pccardd aren't supported in NEWCARD.
Ok. It might be worth noting that in /etc/defaults/rc.conf, which still
has all the pccard_* variables with no suggestion that they don't work.
> consider devd. It is somewhat incomplete in DP2, but complete enough
> for this.
T
Miguel Mendez wrote:
Hi, subject says it all...
A -CURRENT system as of 11/15:
flynn@christine# cat hello.c
#include
#include
int main(int argc, char **argv)
{
printf("Hello, foo!\n");
exit(0);
}
flynn@christine# env CFLAGS="-pg -ax" make hello
cc -pg -ax -march=pentiumpro h
On Sat, Nov 23, 2002 at 10:36:16AM +, Mark Murray wrote:
> > Apparently editors/vim-lite had picked up an old, obsolete libposix*.so
> > from one of the past installations and linked against that. Deleting
> > the port and reinstalling it worked like a charm, which made me think
> > a bit...
> On Fri, 22 Nov 2002, M. Warner Losh wrote:
>
> > In message: > <[EMAIL PROTECTED]>
> > "Maksim Yevmenkin" <[EMAIL PROTECTED]> writes:
> > :
> > : > In message: > <[EMAIL PROTECTED]>
> > : >"Maksim Yevmenkin" <[EMAIL PROTECTED]> writes:
> > : > : I see a lot of "silo overf
> In message: <[EMAIL PROTECTED]>
> "Maksim Yevmenkin" <[EMAIL PROTECTED]> writes:
> :
> : > In message: <[EMAIL PROTECTED]>
> : >"Maksim Yevmenkin" <[EMAIL PROTECTED]> writes:
> : > : I see a lot of "silo overflow" errors under moderate load.
> : > : As a result bytes get
Hi, subject says it all...
A -CURRENT system as of 11/15:
flynn@christine# cat hello.c
#include
#include
int main(int argc, char **argv)
{
printf("Hello, foo!\n");
exit(0);
}
flynn@christine# env CFLAGS="-pg -ax" make hello
cc -pg -ax -march=pentiumpro hello.c -o hello
cc1:
On Sat, 23 Nov 2002, Ertan Kucukoglu wrote:
> First of all, I do not know much about backtracing, debugging etc.
First advice: we shipped DP2 with two different kernels, the normal kernel
without high debugging features, and then a special debugging kernel
called DEBUG. My first advice when st
Hi Garance,
This happened to me also. The solution was to run fsck on the older
versions, but tell it to use an alternate superblock. See man fsck. I
forget the details, but it worked for me.
Rob.
Garance A Drosihn wrote:
>
> I'm playing around with installing a number of freebsd releases on
Nate Lawson <[EMAIL PROTECTED]> writes:
> On Sat, 23 Nov 2002, Brad Knowles wrote:
> > At 2:31 PM -0800 2002/11/22, Terry Lambert wrote:
> >
> > > A "bug-filing wizard" would be useful. The "send-pr" system
> > > doesn't cut it, and most people are unaware of how to file a
> > > decent bug rep
On Sat, 23 Nov 2002, Christian Brueffer wrote:
> just got this panic on my notebook. Had to manually shut it down after a
> acpiconf -s 4. At the next bootup, the panic occured. At the moment I'm
> trying to boot into my system again to reproduce it.
In general, this panic occurs in the follow
Hi,
One of my FreeBSD-current test machines panicked upon
bootup. The message which appeared before the panic was:
imode = 041777, inum = 61, fs = /var
panic: ffs_valloc: dup alloc
I am attaching the ddb trace, the gdb trace,
and some "Fault trap 12" messages that appeared in the console.
Any i
On Saturday 23 November 2002 13:25, David Holm wrote:
I found the problem. I had accidentally run make install in the pthread dir of
the fbsd source tree before following the recent "libpthread question" thread
on the list which explains that it should not be used.
After removing libpthreads and
On Fri, Nov 22, 2002 at 10:03:50AM -0800, David O'Brien
<[EMAIL PROTECTED]> wrote:
> I would like to see GCC 3.2.1 release be our 5.0-R compiler. However,
> the GCC 3.2.1 release date kept slipping and in fact was nebulous for a
> while. The same for our 5.0-R. So this has made it hard to decid
On Sat, Nov 23, 2002 at 02:50:36AM -0800, Terry Lambert
<[EMAIL PROTECTED]> wrote:
> > Either CPU hardware or software bug, fine. You're claiming to know
> > the bug and possible fix, but don't want to publish it, fine.
>
> I do not object to publication of code that embodies a workaroun
> to the
On Saturday 23 November 2002 07:19, Joe Marcus Clarke wrote:
> On Fri, 2002-11-22 at 19:26, David Holm wrote:
>
> These locales are not valid. Set your locale to:
>
> en_US.ISO_8859-1
This gives the exact same error, locale not supported by C library etc.
> And you should be set. The real probl
Ertan Kucukoglu wrote:
> I want to use the power key to shutdown the system. It is
> compaq evo 300, P4 1.6ghz, 368MB RAM
>
> Yesterday OS was 5.0DP2. I can not power it off. It comes
> to a point when it should cut the power off 'System is
> shutting down using ACPI' like message is displayed and
Garance A Drosihn wrote:
> I have 4.6.2-release, 4.7-release, and 5.0-dp2-release on a single PC.
> After some bouncing between versions, and an occasional 'disklabel'
> command, I seem to have the partitions for 4.6.2 in an odd state.
> Both 4.7 and 5.0-dp2 have no problem mounting them, but if I
Thus spake Bruce Evans <[EMAIL PROTECTED]>:
> On Sat, 23 Nov 2002, David Schultz wrote:
>
> > Thus spake Bruce Evans <[EMAIL PROTECTED]>:
> > > ... C90 has a bogus requirement that
> > > the pointer for malloc(0) be "unique", whatever that means. C99 only
> > > requires that the objects pointed
Garance A Drosihn wrote:
> Hmm. I hadn't really thought much about the specifics of what
> is needed. I was just wondering if we might want to think about
> the "auto size" algorithm a bit more.
The value, by default is 2 * `sysctl hw.physmem`.
This is kind of ugly, because it doesn't include t
Hello,
First of all, I do not know much about backtracing,
debugging etc.
I want to use the power key to shutdown the system. It is
compaq evo 300, P4 1.6ghz, 368MB RAM
Yesterday OS was 5.0DP2. I can not power it off. It comes
to a point when it should cut the power off 'System is
shutting down
On Sat, 23 Nov 2002, David Schultz wrote:
> Thus spake Bruce Evans <[EMAIL PROTECTED]>:
> > ... C90 has a bogus requirement that
> > the pointer for malloc(0) be "unique", whatever that means. C99 only
> > requires that the objects pointed to by the results of malloc() be
> > disjoint, and this
I'm playing around with installing a number of freebsd releases on
the same PC, and something came up which makes me a little uneasy.
I understand why I am seeing what I'm seeing, I'm just uneasy about
what it might mean for people who will pick up 5.0-release and start
testing it on their own mach
Vallo Kallaste wrote:
> You got me wrong. I'm user and do not know and don't want to know
> about any CPU architecture and bugs. But I've got problems and
> simply trying to provide any data possible to gather by myself.
> Either CPU hardware or software bug, fine. You're claiming to know
> the bug
At 1:57 AM -0800 11/23/02, Terry Lambert wrote:
Garance A Drosihn wrote:
This is something I noticed while installing 5.0-dp2. I'm not sure
> how much we'd want to change it.
The default swap size calculation is done on the basis of a multiple
of the physical memory size. Specifically, the
Thus spake Garance A Drosihn <[EMAIL PROTECTED]>:
> I'm installing dp2 on a 4-gig disk. I want to split that in two,
> with "dos" for the first 2 gig and freebsd in the last 2 gig. When
> I got to the disklabel step, I tried the "Auto Defaults" option to
> split up the freebsd partition. It pick
On Fri, Nov 22, 2002 at 03:25:15PM -0800, Terry Lambert
<[EMAIL PROTECTED]> wrote:
> > I have now definitive answer for _my_ case and environment. Just
> > finished full package build for my workstation bundle port (92
> > ports), including XFree-4, KDE3, mozilla-devel and whatnot. It all
> > went
Thus spake Bruce Evans <[EMAIL PROTECTED]>:
> Er, malloc(0) is defined as returning either a null pointer or a pointer
> to 0 bytes of allocated space. Which one it chooses to return is
> implementation-defined, not undefined. C90 has a bogus requirement that
> the pointer for malloc(0) be "uniqu
> Apparently editors/vim-lite had picked up an old, obsolete libposix*.so
> from one of the past installations and linked against that. Deleting
> the port and reinstalling it worked like a charm, which made me think
> a bit... Should we recommend in UPDATING that source upgrades include
> someth
In message <[EMAIL PROTECTED]>, Kyle Martin writes:
>On Sat, Nov 16, 2002 at 10:15:53AM -0500, sven svenskar wrote:
>> I have server i give people shell accounts each in chroot and they need some
>devices. How this work with DEVFS? Should I copy devices from DEVFS with dd or tar?
>Or I mount DEVF
On Fri, 22 Nov 2002, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> "Maksim Yevmenkin" <[EMAIL PROTECTED]> writes:
> :
> : > In message: <[EMAIL PROTECTED]>
> : >"Maksim Yevmenkin" <[EMAIL PROTECTED]> writes:
> : > : I see a lot of "silo overflow" errors under mo
On Sat, Nov 16, 2002 at 10:15:53AM -0500, sven svenskar wrote:
> I have server i give people shell accounts each in chroot and they need some
>devices. How this work with DEVFS? Should I copy devices from DEVFS with dd or tar?
>Or I mount DEVFS in every chroots? Please help!
why not just use jai
Garance A Drosihn wrote:
> This is something I noticed while installing 5.0-dp2. I'm not sure
> how much we'd want to change it.
>
> I'm installing dp2 on a 4-gig disk. I want to split that in two,
> with "dos" for the first 2 gig and freebsd in the last 2 gig. When
> I got to the disklabel ste
Bruce Evans wrote:
> The existence of SYSINIT is a bug, but shouldn't the order of SYSINITs be
> such that they are run before MOD_LOAD events?
>
> SYSINITs have no way to communicate failure, so they are especially broken
> when they are used to allocate resources. Users of the resources have no
Scott Sipe wrote:
> I didn't make a backup copy (or mark down the errors) of the bad file or try
> rebooting which in retrospect would have been a good idea..sorry--I just
> fixed the file and saved it so I could compile some ports--and that worked.
Just FWIW: if it was a transfer error, a backup
On Sat, 23 Nov 2002, Mitsuru IWASAKI wrote:
> > On Fri, Nov 22, 2002 at 04:08:05PM -0500, John Baldwin wrote:
> >
> > > > Can something be done to guard against this?
> > >
> > > It's supposed to do that already:
> >
> > > If that isn't working then there is a bug.
> >
> > There's a bug :-)
>
> Ah
OK. The lightbulb went on this evening on some of the problems we're
having with the pci_allow_unsupported_io_ranges stuff. We weren't
doing the right thing with prefetchable memory, hence the nvida
driver's need to tell people to set this. I'd like to commit the
following change, with re approv
On Fri, 22 Nov 2002, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Marc Recht <[EMAIL PROTECTED]> writes:
> : A malloc(0) returns always 0x800 on my system. This causes some third-party
> : software to fail, because they expect malloc(0) to return NULL. Is this a
> : bug or
Sat Nov 23 01:00:11 PST 2002
...
U sys/alpha/alpha/vm_machdep.c
? sys/alpha/conf/LINT
U sys/cam/scsi/scsi_target.c
U sys/cam/scsi/scsi_targetio.h
U sys/i386/i386/pmap.c
U sys/i386/i386/vm_machdep.c
U sys/ia64/ia64/vm_machdep.c
U sys/kern/kern_thread.c
U sys/modules/cam/Makefile
cvs [update aborted]
On Saturday 23 November 2002 02:38 am, Terry Lambert wrote:
> Scott Sipe wrote:
> > Alright, this is pretty frustrating. I've installed DP2 4 or 5 times now
> > (each time reformatting).
> >
> > The first time the installation program acted really weird and didn't do
> > the install correctly.
>
>
On Sun, Nov 17, 2002 at 12:17:15AM -0800, Arun Sharma wrote:
> Works fine when I don't specify -listen_tcp. Has anyone seen this ?
Sorry for the terse message. Here's some more information. This appears
to be related to int10 initialization. I have a ATI Radeon card.
XFree86.0.log:
(II) RADEON(0
This is something I noticed while installing 5.0-dp2. I'm not sure
how much we'd want to change it.
I'm installing dp2 on a 4-gig disk. I want to split that in two,
with "dos" for the first 2 gig and freebsd in the last 2 gig. When
I got to the disklabel step, I tried the "Auto Defaults" option
77 matches
Mail list logo
