On Mon, Sep 02, 2002 at 08:05:48PM -0700, Alex Zepeda wrote:
>
> And how does one do that?
>
You never posted any error messages you were getting, so I can
only guess what is going on. The patch below gets rpm to compile
on my -current. Never tested it on -stable though, it might
break compiles
On Sat, May 11, 2002 at 11:18:40AM -0700, Julian Elischer wrote:
>
> seems something broke in the networking side of things using host-only
> networking.. vmnet1 doesn;t show up any more..
>
VMWare is working fine on -CURRENT from May 7th. As Garance A Drosihn
has pointed out, the vmware startup
The following check added into kern_linker.c seems wrong somehow:
if (securelevel_gt(td->td_ucred, 0) == 0) {
error = EPERM;
goto out;
}
The last thing securelevel_gt does is to perform this check:
return (active_securelevel > level ? EPERM
> Alex are you still workin' for a patch?
Yes, I am. But as I write before I am not familiar with this particular
part of GCC at all, so I cannot give any estimates and even promize to
produce a working patch. If some other more knowledgeable person
is feeling like beating me to it, please feel f
> Interesting. Is the DF_TEXTREL flag set in DT_FLAGS instead? Is the
> library linked w/ -enable-new-dtags? Are the new dtags enabled by
> default in the new binutils? Someting in elf32.em?
No. DT_FLAGS entry is not created regardless of whether the
--enable-new-dtags parameter has been passed t
> This suggests a problem with the runtime-linker (rtld), not binutils.
Actually, the bug is somewhere in the new binutils code, and I am very
close to finding where it is exactly. The new liker fails to set
DT_TEXTREL property in the shared library header even though its relocation
table contain
I had this problem with telnet some time ago. See PR bin/32591 at
http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/32591 for a patch
which fixes the problem for me. The memory block is being freed
twice in the Heimdal code.
Unfortunately, PR got no attention whatsoever for over a month now.
It is
= 0xbfbff50c, tf_ss = 0x2f}) at
../../../i386/i386/trap.c:1140
#19 0xc02dfc1d in syscall_with_err_pushed ()
#20 0x8094e81 in ?? ()
#21 0x809a0ec in ?? ()
#22 0x8064dfb in ?? ()
#23 0x806d38c in ?? ()
#24 0x804d841 in ?? ()
(kgdb)
----
E-Mail: Alexander N. Kaba
v = pcibios_get_version();
if (v > 0)
printf("pcibios: BIOS version %x.%02x\n", (v & 0xff00) >> 8,
E-Mail: Alexander N. Kabaev <[EMAIL PROTECTED]>
Date: 03-Oct-2001
Time: 10:55:24
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I am trying to install -CURRENT on ThinkPad 770ED with a limited success
so far. I noticed that when the kernel boots on this notebook, it
complains about PCI BIOS entry call point not being available. The
following is a boot -v output from my kernel file(see below for further
comments):
Copyrigh
x27;t set guest privileges.
ftp: Login failed.
--- End ---
Does anyone know any other mirror with a reasonably recent -CURRENT
snapshot?
E-Mail: Alexander N. Kabaev <[EMAIL PROTECTED]>
Date: 26-Sep-2001
Tim
It appears that nfs_msg function in nfsclient/nfs_socket.c file
is not prepared to deal with NULL thread pointer passed to it
and bogusly tries to reference td->td_proc.
I had to add this simple patch to avoid panics:
Index: nfs_socket.c
=
Freshly cvsuped kernel fails to build trying to find acpi_isa.c file, which
does not exist anymore.
On 30-Aug-2001 Mike Smith wrote:
>
> I have just committed some changes to the way that ACPI works in
> current. This has an impact on all -current users, so please
> take a few seconds to read
ld only is not sufficient. ld + all libraries it depends on (read: binutils)
should be recompiled.
On 17-Aug-2001 Ollivier Robert wrote:
> According to Alexander N. Kabaev:
>> ld had a nasty bug in -CURRENT which resulted exactly in this kind of
>> errors.
>> David O
6:41 /usr/X11R6/bin/uic*
> -r--r--r-- 1 root wheel 621 Jun 15 17:03 /usr/lib/crtn.o
>
> The same package compiled fine on my 4.4-PRERELEASE system.
>
> Any idea?
----
E-Mail: Alexander N. Kabaev <[EMAIL PROTECTED]>
Date: 17-Aug-2001
Ti
-CURRENT kernel panics when booting with debug.witness_watch tunable set to 0
in loader. It looks like witness_assert function should not do anything in
this case. Attached patch fixes the problem for me.
The panic I am getting looks like that:
panic: Lock (sx) fork list not locked @ ../../kern/
"unsubscribe freebsd-current" in the body of the message
----
E-Mail: Alexander N. Kabaev <[EMAIL PROTECTED]>
Date: 22-Jun-2001
Time: 11:41:47
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> That's Paul Richards, not Bill Paul.
My apologies, I should have checked before pressing that 'Send' button :(
> I don't quite understand Paul's reasoning, though; it's not actually
> useful to unload/reload parts of a device's bus attachment without
> unloading/reloading all the downstream
.
>
> However, he maybe too busy working, there is no response from him. Are
> there any committers to check my patch and fix the driver?
>
> -- -
> Makoto MATSUSHITA
----------
E-Mail: Alexander N. Kabaev <[EMAIL PROTECTED
>
> Just don't use the skipspin stuff, it shouldn't hurt at all. The new witness
> code will hopefully be in by the end of the week. *crosses fingers*
Cool. WITNESS_SKIPSPIN was quite useful for NETGRAPH users because of some
unregistered spin mutexes there. Julian fixed the problem already, s
skipspin counter
if debug.witness_skipspin is non-zero.
--
E-Mail: Alexander N. Kabaev <[EMAIL PROTECTED]>
Date: 12-Mar-2001
Time: 12:40:36
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe free
> But I remember some posts about a lpt panic some days ago. I tried to
> compile a new kernel because I think this is resolved, but I have to
> solve some problems with my system at the moment.
My -CURRENT used to crash every time lpr has been used but the panic went away
when John Baldwin commi
> However, your problems with lpr are a known problem and one
> that is in the process of being fixed.
That was me who reported lpr problems in this thread. I just found it curious
that Andrea's panics look absolutely identical to ones I am getting here when
attempting to use lpr. Do you really th
> Re: the strace db trace above, is it possible that it might be because I
> have:
>
> CFLAGS ?= -O -pipe -mcpu=i686 -march=i686
> COPTFLAGS ?= -O -pipe -mcpu=i686 -march=i686
No, I was getting the same panic with the kernel, compiled with stock flags.
To Unsubscribe: send mail
is used to change console resolution to the VESA_800x600 mode.
I was able to get the crash dump, but unfortunately it seems like the stack is
becoming corrupt and so there is no useful information to report.
--
E-Mail: Alexander N. Kabaev <[EMAIL PROTECTED]>
>
> I don't think it is allowed to do that. See the SUSv2 description:
>
> http://www.opengroup.org/onlinepubs/007908799/xsh/dlerror.html
>
Sorry, you are right of course. The attached patch removes the _rtld_error
call at the end of the symlook_default function which seems to be unnecessar
John,
I think dymanic loader should clear it's error_string variable before returning
success to the caller. I am halfway done preparing the patch to do that. Is
that the bug you mentioned or there is something else? Anyway, do you want to
see my patch when it is ready or you prefer to take care
> Nope, explicitly linking shared module with -lgcc doesn't solve this problem.
>
> -Maxim
Then it is not new crt* code that is broken
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Why FreeBSD does not link libgcc into shared libraries by default? Everyone
else is doing that. Linking shared libraries with libgcc seems to be the
ultimate work-around. Are there any compatibility problems which are keeping
FreeBSD from doing that?
> OK, thanks. I'll take a look at it as soo
I've spent couple hours already trying to reproduce the error and so far
failed miserably. Am I the only one who does not see this problem at all?
On 06-Nov-00 Maxim Sobolev wrote:
> After the crt changes the following piece of code, which worked previously,
> gives a 'host: dlopen() failed: ./
>
> What caused such a change? I mean, what the purpose of it, what set of
> problems should it (probably?) solve?
>
http://www.FreeBSD.org/cgi/query-pr.cgi?pr=20966
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Aug 22 13:07:40 kanpc /kernel: tag VT_UFS, ino 349296, on dev #ad/0x30005 (116,
196613) lock type inode: EXCL (count 1) by pid 5
--
E-Mail: Alexander N. Kabaev <[EMAIL PROTECTED]>
Date: 22-Aug-00
Time: 13:09:40
--
To Unsub
There was a patch floating around which fixed these mouse problems for me.
XFree86-patch
After today's buildworld, I am seeing lots of warning messages from libc like:
expr in free(): warning: modified (chunk-) pointer
Does it happen to anyone else on this list?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
make -j8 buildworld fails with these messages for a second day in a row:
cd /usr/src/secure/lib/libssl; make _EXTRADEPEND
===> librsausa
mkdir: openssl: File exists
*** Error code 1
cp /usr/src/secure/lib/librsausa/../libcrypto/opensslconf-i386.h \
openssl/opensslconf.h
1 error
*** Error code 2
1
decode
> 5 min long song).
>
> FreeBSD Audio Driver (newpcm) Apr 19 2000 09:43:52
> Installed devices:
> pcm0: at io 0x220 irq 5 drq 1:5 (1p/1r channels duplex)
>
----------
E-Mail: Alexander N. Kabaev <[EMAIL PR
:43:52
Installed devices:
pcm0: at io 0x220 irq 5 drq 1:5 (1p/1r channels duplex)
--
E-Mail: Alexander N. Kabaev <[EMAIL PROTECTED]>
Date: 19-Apr-00
Time: 12:16:37
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "
Actually, it seems that Java borrowed a whole lot of ideas from Modula-3. And
C++ experience can even hurt instead helping when switching to Java. Java
inherits some parts of C++ syntax but is based on rather different design.
On 19-Apr-00 Donn Miller wrote:
> Donn
To Unsubscribe: send mail t
-----
E-Mail: Alexander N. Kabaev <[EMAIL PROTECTED]>
Date: 07-Apr-00
Time: 15:44:39
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ssages for the 0 addresses. Easy enough to
> cause though:
>
> ifconfig xx0 0.0.0.0 up
>
> should do the trick...
>
--
E-Mail: Alexander N. Kabaev <[EMAIL PROTECTED]>
Date: 07-Apr-00
Time: 14:35:14
--
To Un
Trivial patch attached :)
On 07-Apr-00 John Polstra wrote:
> In article <[EMAIL PROTECTED]>,
> Alexander N. Kabaev <[EMAIL PROTECTED]> wrote:
>> The message in question can be extremely useful in case there is IP address
>> clash on the local network. I sugg
/* log(LOG_ERR,
>"arp: %6D is using my IP address %s!\n",
> - ea->arp_sha, ":", inet_ntoa(isaddr));
> + ea->arp_sha, ":", inet_ntoa(isaddr)); */
> itaddr = myaddr;
>
I am perfectly aware of the way OpenBSD builds contrib software. I am just
making a point that they have found perl 5.6.0 is stable enough to be
included into their OS.
On 07-Apr-00 Kris Kennaway wrote:
> On Thu, 6 Apr 2000, Alexander N. Kabaev wrote:
>
>> According to OpenBSD
According to OpenBSD ournal site, OpenBSD-current has perl 5.6.0 in it's source
tree already.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
x. That one also did not load PIC register R2 in setjmp and suffered exactly
the same consequences :)
On 18-Jan-00 David O'Brien wrote:
> On Mon, Jan 17, 2000 at 09:07:28PM -0500, Alexander N. Kabaev wrote:
>> Compiled without -fsjlj-exceptions, it dumps core.
>
> Ex
I will be greatly surprised if OpenBSD will survive the test
since their egcs looks like stock egcs 1.1.2 version which has not been heavily
patched from original Cygnus version.
--
E-Mail: Alexander N. Kabaev <[EMAIL PROTECTED]>
Date:
or branch. Any help would be
> appreciated.
>
> --
> -- David([EMAIL PROTECTED])
--
E-Mail: Alexander N. Kabaev <[EMAIL PROTECTED]>
Date: 17-Jan-00
Time: 14:57:58
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
: Alexander N. Kabaev <[EMAIL PROTECTED]>
Date: 17-Jan-00
Time: 14:11:19
--
Index: config/i386/i386.md
===
RCS file: /home/ncvs/src/contrib/gcc/config/i386/i386.md,v
retrieving revision 1.5
diff -u -r1.5 i
As promised, I tried to look into the problem little futher. The following
patch fixes all crashes for me and I was unable to reproduce the bug anymore. I
would really like to hear if it works for you too. I am especially interested
to know if it works on Alpha, because I cannot test it myself.
P
: Alexander N. Kabaev <[EMAIL PROTECTED]>
Date: 13-Jan-00
Time: 22:35:50
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
x27;m not one of the "compiler gurus", so it would be almost
> impossible for me to fix this problem.
>
> -Maxim
>
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
--
These are my results:
% ifconfig -a
xl0: flags=8843 mtu 1500
inet6 fe80:1::250:daff:fe20:495b prefixlen 64
inet 24.218.93.188 netmask 0xfc00 broadcast 24.218.95.255
ether 00:50:da:20:49:5b
media: autoselect (10baseT/UTP) status: act
I have TOSHIBA DVD-ROM SD-M1201 1R08 on Adaptec 2440U2W and tosha works fine
with it. I used to get the same error messages from tosha just a
couple weeks ago. cdd2wav worked OK. I upgraded to the latest firmware
on both the controller and the drive and error messages disappeared.
Kernel and wo
Well, it seems like RPCMNT_UMNTALL call always fails with RPC_SYSTEMERROR on
all systems except FreeBSD. I tested HP/UX, AIX and Solaris boxes - they all
behave identically as follows:
rpc.umntall -h $HOST always fails
rpc.umntall -h $HOST -p $DIR - works just fine since it is using RPCMNT_UMOUNT
direction.
--
E-Mail: Alexander N. Kabaev <[EMAIL PROTECTED]>
Date: 01-Dec-99
Time: 17:53:48
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Bad address
>
> Any idea?
>
> Jean-Marc
>
> --
> Jean-Marc ZucconiPGP Key: finger [EMAIL PROTECTED]
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
vmstat -s reports these numbers on my computer:
3649151 copy-on-write faults
1 copy-on-write optimized faults
On 29-Oct-99 Alan Cox wrote:
> I would appreciate it if people running -current would run a "vmstat -s"
> and tell me if they see a NON-ZERO value for copy-on-write optimized
>
Current (cvsupped and build today) fails to attach to the intpm0 device. The
following is my dmesg message:
Copyright (c) 1992-1999 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #0: Tu
The following script reliably causes FreeBSD 4.0-CURRENT (and 3.1-STABLE
as of today) to lookup. Shortly after this script is started, all disk activity
stops and any attempt to create new process causes system to freese. While in
DDB, ps command
shows, that all ten fgrep processes are sleeping
There is no need to fix kernel if the same result could be achieved by simple
rc.network file modification. Yes, solution proposed in conf/14913 is
not complete and only works in network_interfaces="auto" case, but the
modification to make it work in 100% cases is pretty trivial.
On 19-Nov-99 L
on the output
> queue of an ethernet card. It happens only if I run amd, I could telnet
> to localhost without any problem. Any idea?
>
> -lq
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
t;unsubscribe freebsd-current" in the body of the message
--
E-Mail: Alexander N. Kabaev <[EMAIL PROTECTED]>
Date: 19-Nov-99
Time: 09:37:48
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
62 matches
Mail list logo
