On Thu, 19 Sep 2002, Daniel Eischen wrote:
> On Wed, 18 Sep 2002, Julian Elischer wrote:
>
> > threads is broken right now..
> > due to a miscommunicatin,. the kernel and the threads library have
> > a disagreement regarding something..
> > Unfortunatly the person to slap up over this is offli
I need a little bit of help/advise. I am trying to install -CURRENT on a
toshiba 3005-s304. for -release or stable, I needed to turn off eisa
probing before I could boot/install. I did this by going into boot -c
and then entering eisa 0.
boot -c on DP1, and the latest snapshots doesnt seem to do
On Wed, 18 Sep 2002, Julian Elischer wrote:
> threads is broken right now..
> due to a miscommunicatin,. the kernel and the threads library have
> a disagreement regarding something..
> Unfortunatly the person to slap up over this is offline for aday or
> so..
> please be patient for a day or so
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
Boot from a kernel from a day or two ago and you should be fine. Unless
you build every day, your kernel.old/kernel should be in agreement with
libc_r
On Wed, 18 Sep 2002, Julian Elischer wrote:
> threads is broken right now..
> due to a miscommunicatin,. the kernel and the threads library have
threads is broken right now..
due to a miscommunicatin,. the kernel and the threads library have
a disagreement regarding something..
Unfortunatly the person to slap up over this is offline for aday or
so..
please be patient for a day or so (we hope).
On Wed, 18 Sep 2002, Edwin Culp wrote:
> I
On Thu, 2002-09-19 at 00:32, Edwin Culp wrote:
> I just realized that slapd dumps core with:
>
> Fatal error '_pq_insert_head: prioq not protected!' at line 185 in file
> /usr/src/lib/libc_r/uthread/uthread_priority_queue.c (errno = 22)
> Abort (core dumped)
>
> I have recompiled openldap and d
Dag-Erling Smorgrav wrote:
> >>> Kernel build for LINT started on Wed Sep 18 15:43:20 PDT 2002
> --
> ===> vinum
> ./aicasm: 877 instructions used
> ./aicasm: 658 instructions used
> In file included from /h/des/src/sys/dev/dgb/dgb.c:89:
I just realized that slapd dumps core with:
Fatal error '_pq_insert_head: prioq not protected!' at line 185 in file
/usr/src/lib/libc_r/uthread/uthread_priority_queue.c (errno = 22)
Abort (core dumped)
I have recompiled openldap and db3 but it didn't help. Any suggestions
would be appreciated.
> On Wed, 18 Sep 2002 21:44:33 -0400 (EDT),
> Trish Lynch <[EMAIL PROTECTED]> said:
> sysctl net.inet6.ip6.v6only=0
This should also work:
*** foo.c.orig Thu Sep 19 12:05:04 2002
--- foo.c Thu Sep 19 12:05:56 2002
***
*** 14,19
--- 14,20
struct sockaddr
I have just updated kernel from freefall and compiling failed:
c -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
-fformat-extensions -ansi -g -nostdinc -I- -I. -I../../.. -I../../../dev
-I..
sysctl net.inet6.ip6.v6only=0
-Trish
--
Trish Lynch[EMAIL PROTECTED]
Ecartis Core Team [EMAIL PROTECTED]
Key fingerprint = C44E 8E63 6E3C 18BD 608F E004 9DC7 C2E9 0E24 DFBD
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
THis works fine on DP-1.
So it broke somewhere between then and now.
-Trish
--
Trish Lynch[EMAIL PROTECTED]
Ecartis Core Team [EMAIL PROTECTED]
Key fingerprint = C44E 8E63 6E3C 18BD 608F E004 9DC7 C2E9 0E24 DFBD
To Unsubscr
On Thu, Sep 19, 2002 at 08:30:23AM +0800, Huang wen hui wrote:
> hi,
> I could not use pppd under -CURRENT, may be pppd driver could not link
> into kernel?
> I am sure I include ppp driver in system config file.
>
> # uname -a
> FreeBSD hwh.gddsn.org.cn 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Tue Se
hi,
I could not use pppd under -CURRENT, may be pppd driver could not link
into kernel?
I am sure I include ppp driver in system config file.
# uname -a
FreeBSD hwh.gddsn.org.cn 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Tue Sep 17
20:56:16
CST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/HWH i386
# ppp
FreeBSD femme.sapphite.org 5.0-CURRENT FreeBSD 5.0-CURRENT #16: Mon Sep 9
10:23:22 EDT 2002
[EMAIL PROTECTED]:/admins/obj/admins/src/sys/FEMME i386
foo.c:
#include
#include
#include
#include
#include
#include
#include
#include
#include
int
main(int argc, char *argv[])
{
struct sock
On 18 Sep, Doug White wrote:
> On Wed, 18 Sep 2002, Don Lewis wrote:
>
>> I needed to configure my -current box to use a serial console so that I
>> could get to ddb while the system was running the X11 server on the main
>> console, so I hooked up the serial cable and rebooted with the -h option
On Wed, 18 Sep 2002, Don Lewis wrote:
> I needed to configure my -current box to use a serial console so that I
> could get to ddb while the system was running the X11 server on the main
> console, so I hooked up the serial cable and rebooted with the -h option
> in boot.config. After I did this
I needed to configure my -current box to use a serial console so that I
could get to ddb while the system was running the X11 server on the main
console, so I hooked up the serial cable and rebooted with the -h option
in boot.config. After I did this, I noticed that the green_saver kld
would no l
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
On 18 Sep, Garrett Wollman wrote:
> < said:
>
>> 10. Upgraded to gcc3.2. I was seeing now some SIG11 during builds,
>> and - panics ! Softupdates and fs panics mostly. I turned off
>> softupdates. The panic was different, but all the time it was
>> in mmap.
>
> I'm not seeing panics,
Being a user of ipfilter, I always longed for it to benefit from
the same treatment as ipfw in daily security checks, so I
undertook the implementation of an ipf equivalent of 500.ipfwdenied.
In the course of that, I noticed that much of that script was
non-trivial *and* duplicated wrt 600.ip6fwde
On Wed, 18 Sep 2002, Martin Blapp wrote:
>
> Hi,
>
> > One thing you didn't mention was trying a different power supply. A
> > marginal power supply can cause strange errors. Increasing your memory
> > size from 512 MB to 1 GB might add just enough load to the supply to
> > push it over the edg
No update on the cpp0 error but I can get bind9 to stay running if I disable
threads in the Makefile... no more signal 6.
-Steve
> New datapoint:
>
> If I compile the kernel in the old fashion (config SB; cd ../compile/SB;
> make depend all install) then the kernel compiles and installs fine.
>
your include files are out of date..
libkvm uses a lot of kernel derived includes.
TDS_INHIBITED is in /sys/sys/proc.h --> /usr/include/sys/proc.h
On Wed, 18 Sep 2002, Radko Keves wrote:
> i try to compile kvm library with today's source on i386 tree and have found this
>error:
>
> [...]
> c
On Fri, Sep 13, 2002 at 03:35:32PM +0300, Vallo Kallaste wrote:
> As promised I did some further testing and found that either of the
> problematic ports will build fine in case that:
> 1. both world and kernel are built without any CPU specific
> optimisation beforehand (with kan's patch)
> 2.
i try to compile kvm library with today's source on i386 tree and have found this
error:
[...]
cc -O -pipe -mcpu=pentiumpro -DLIBC_SCCS -I/usr/src/lib/libkvm -c
/usr/src/lib/libkvm/kvm.c -o kvm.o
In file included from /usr/src/lib/libkvm/kvm.c:63:
/usr/src/lib/libkvm/kvm.h:49: syntax error bef
New datapoint:
If I compile the kernel in the old fashion (config SB; cd ../compile/SB;
make depend all install) then the kernel compiles and installs fine.
However I get the error below when doing a 'make kernel' from /usr/src.
Also even after rebooting onto the new kernel bind9 and mysql-ser
Fixed already.
>/local0/scratch/des/src/sys/netsmb/smb_usr.c: In function `smb_usr_t2request':
>/local0/scratch/des/src/sys/netsmb/smb_usr.c:332: warning: implicit declaration of
>function `m_fixhdr'
>/local0/scratch/des/src/sys/netsmb/smb_usr.c:345: warning: redundant redeclaration of
>`m_fix
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
This started yesterday after an upgrade to a recent -CURRENT (prior
version was perhaps 4 days old). Some programs (specifically bind9
and mysql-server) starting aborting with a sig6.
Figuring maybe I just caught an update in the middle or some such
I updated the source again and rebuilt world.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hi,
> I'm not seeing panics, but I am seeing memory corruption causing about
> every third buildworld to fail. Usually this affects `cc1' or `ld',
> but last night I saw corruption in a source file.
Before new gcc3.2 import I also have not seen panics. Panics started after
latest 3.2.1 import.
< said:
> 10. Upgraded to gcc3.2. I was seeing now some SIG11 during builds,
> and - panics ! Softupdates and fs panics mostly. I turned off
> softupdates. The panic was different, but all the time it was
> in mmap.
I'm not seeing panics, but I am seeing memory corruption causing abo
On Wed, 18 Sep 2002, Maxim Konovalov wrote:
> On 07:10+0400, Sep 18, 2002, David O'Brien wrote:
>
> > On Tue, Sep 17, 2002 at 11:39:50AM +0200, Robert Suetterlin wrote:
> > > Hello!
> > >
> > > I currently upgraded my 4.4 to 4.7-PRE and now tried to get from
> > > there to -CURRENT.
> > >
> > >
On Tue, 17 Sep 2002, Dag-Erling Smorgrav wrote:
> --
> >>> Kernel build for LINT started on Tue Sep 17 15:31:39 PDT 2002
> --
> ===> vinum
> ./aicasm: 877 instructions used
> ./
Hi,
> Which Asus? Does it support ECC memory? Do you have ECC memory and
> have ECC enabled in the BIOS?
I used 3 boards:
1. ASUS P4B533-V 1GB DRAM 2100
2. Intel BG485 512MB DRAM 2100
3. Intel BG485 512MB DRAM 2100 ECC
>
> The thing that scared me about these reports was that I was under t
On Wed, 18 Sep 2002 [EMAIL PROTECTED] wrote:
> btw, this box is connected via a serial console at 9600 bps and while typing
> at the ddb-prompt it swallowed most characters, i.e. i had to type single
> characters up to four times.
That and the "Context switches not allowed in the debugger." mess
Martin Blapp writes:
> 8. I changed again the mobo. This time ASUS, but same I845 chipset.
> The system run fine.
Which Asus? Does it support ECC memory? Do you have ECC memory and
have ECC enabled in the BIOS?
The thing that scared me about these reports was that I was under the
impr
Hi,
I've decided to try the uvisor USB module to play with my Palm and tried to
load the module. Loading it manually fails with an undefined symbol (found
in the usb module). I'll try to link it statically.
link_elf: symbol usb_match_device undefined
When I try to load it from loader.conf, I ge
We're looking at it..
On Tue, 17 Sep 2002, walt wrote:
> Joe Marcus Clarke wrote:
>
> > I just cvsup'd -CURRENT two hours ago, built world and kernel, then
> > rebooted...same as always. Now, nautilus-2.0.7 fails to start with a
> > thread abort...
>
> I saw the same error starting last nig
Hi,
Can someone else to and try this on PIV system ?
Thanks
> did this on my Celeron2 on a 440BX and a Samsung SpinPoint 80GB drive
> (limited to UDMA33). softupdates enabled and no errors after hours of
> patching/cleaning.
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
On Tue, 17 Sep 2002 00:42:13 +0200 (CEST), you wrote:
>I and Michael can kill CURRENT quite simple with
>
>cd /usr/ports/www/mozilla
>make clean
>make patch
>make clean
>
>after 7-10 times we crash.
>
>This is on IDE disks. And I even turned softupdates
>of. The panic trace is then similar, but n
--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
Hi,
> One thing you didn't mention was trying a different power supply. A
> marginal power supply can cause strange errors. Increasing your memory
> size from 512 MB to 1 GB might add just enough load to the supply to
> push it over the edge ...
Yes. I've replaced the power supply. But only o
On 07:10+0400, Sep 18, 2002, David O'Brien wrote:
> On Tue, Sep 17, 2002 at 11:39:50AM +0200, Robert Suetterlin wrote:
> > Hello!
> >
> > I currently upgraded my 4.4 to 4.7-PRE and now tried to get from
> > there to -CURRENT.
> >
> > Unfortunately ``make buildworld'' fails during stage 2 when
On 18 Sep, Martin Blapp wrote:
>
> Hi Robert,
>
>> Chances are, if you change an important variable such as memory size, it
>> will change the failure mode for this bug. Carefully marking the memory
>
> Sigh.
>
> Looks like you are right. After running the system now for 8 hours,
> I got exac
Hi all,
To get always the same panic (not softupdate or ffs crashes) one
has to do the following:
- sysctl kern.sync_on_panic=0
- Disable softupdates on the filesystem in question.
The panics are more informative then.
To get the panics more often:
Set in loader.conf:
- hw.physmem=131072 or
48 matches
Mail list logo