> > Oh and I left memtest86 running on that box overnight and it
> > found nothing...
>
> well, it could be a kqemu bug I guess, but your panics look like
> seemingly random memory corruptino as you have stack traces where
> functions are calling other functions that the don't actually call
> in th
On Nov 29, 2007, at 7:34 PM, Yuri wrote:
Quoting Garrett Cooper <[EMAIL PROTECTED]>:
Yes, it's partly caused by pkgdb and/or how Ruby / pkgdb
handles the
DB I think...
1. What type of BDB structure do you use [most likely btree(1) --
says this during the pkgdb rebuild..]?
bdb_btree
Quoting Garrett Cooper <[EMAIL PROTECTED]>:
> Yes, it's partly caused by pkgdb and/or how Ruby / pkgdb handles the
> DB I think...
> 1. What type of BDB structure do you use [most likely btree(1) --
> says this during the pkgdb rebuild..]?
bdb_btree
> 2. What version of BDB are you u
Yuri wrote:
I deleted this file: /var/db/pkg/pkgdb.db and then pkgdb -fu succeeded.
But next time I ran I got the same error with /usr/ports/INDEX-7.db.
Then this error disappear.
So it's most likely the bug with Berkeley DB.
Anybody else has these kind of problems?
Yuri
Quoting Yuri <[EMAIL
I deleted this file: /var/db/pkg/pkgdb.db and then pkgdb -fu succeeded.
But next time I ran I got the same error with /usr/ports/INDEX-7.db.
Then this error disappear.
So it's most likely the bug with Berkeley DB.
Anybody else has these kind of problems?
Yuri
Quoting Yuri <[EMAIL PROTECTED]>:
While doing portupgrade I am sporadically getting the error like below.
After I ran 'pkgdb -fu' few times and this cured tye problem. But then after
a while of portupgrade run I now get the error:
>pkgdb -fu
>---> Updating the pkgdb
>[Rebuilding the pkgdb in /var/db/pkg ...
/var/db/pkg/pkgdb.db:
This diff is a partial MFC (picking parts out of -current)
that makes aio_return() return the error return of a completed AIO
request. (as it does on othe OS's and in 7.x).
The man page for 6.x and other OS's indicate that aio_return
shoud return all the same results as a returning read() or
I tried to build 7.0-BETA3 kernel with DEBUG_REDZONE enabled but it seamed
that this option is unusable on amd64 :( First, it conflicts with INVARIANTS,
then when I'd turned off INVARIANTS kernel started complaining on modules
that could not be found. Like "module named g_dev not found". There
On Wednesday 28 November 2007 06:50:42 pm Juergen Lock wrote:
> On Tue, Nov 27, 2007 at 08:24:55AM -0500, John Baldwin wrote:
> > On Sunday 18 November 2007 05:43:45 pm Juergen Lock wrote:
> > > On Sun, Nov 18, 2007 at 03:05:33AM +0100, Juergen Lock wrote:
> > > > Ok I finally have an amd64 smp box
Yuri wrote:
Quoting Kris Kennaway <[EMAIL PROTECTED]>:
Yes, that's what I am doing.
portupgrade -af
That is what you are doing now, or what you were doing when you found
the problem? It should not occur during a portupgrade -af unless there
is a port that is missing registration on some depe
[EMAIL PROTECTED] wrote:
hi , freebsd-hackers.
I found this reference
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=372365+0+/usr/local/www/db/text/2006/freebsd-hackers/20060226.freebsd-hackers
how is it correct to conduct this procedure ?
beforehand thank you !!
tmpfs is included in Fre
Quoting Kris Kennaway <[EMAIL PROTECTED]>:
> > Yes, that's what I am doing.
> > portupgrade -af
>
> That is what you are doing now, or what you were doing when you found
> the problem? It should not occur during a portupgrade -af unless there
> is a port that is missing registration on some de
Yuri wrote:
Quoting Kris Kennaway <[EMAIL PROTECTED]>:
So do I have to rebuild all ports to be able to run on 7.0?
Yes. You have to do this whenever you upgrade to a new branch of
FreeBSD. The old ports will work until you start upgrading them to new
versions, at which point you will end up
Giorgos Keramidas wrote:
> On 2007-11-27 21:27, Chuck Robey <[EMAIL PROTECTED]> wrote:
> > I need to read about 4 tons of some really sparse pdf specs. I also
> > have a rather inconvenient throwback: I feel hugely more at
> > home-reading documents in paper. What I'd kind of like to do would
>
hi , freebsd-hackers.
I found this reference
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=372365+0+/usr/local/www/db/text/2006/freebsd-hackers/20060226.freebsd-hackers
how is it correct to conduct this procedure ?
beforehand thank you !!
--
With kind regards ,
dn
Quoting Remko Lodder <[EMAIL PROTECTED]> (from Thu, 29 Nov 2007
07:19:36 +0100 (CET)):
On Thu, November 29, 2007 12:01 am, Stefan Sperling wrote:
OK, I've created an account in the wiki.
My login is StefanSperling
Thanks :)
I added you to the list.
I created http://wiki.freebsd.org/Wa
Quoting Kris Kennaway <[EMAIL PROTECTED]>:
> > So do I have to rebuild all ports to be able to run on 7.0?
>
> Yes. You have to do this whenever you upgrade to a new branch of
> FreeBSD. The old ports will work until you start upgrading them to new
> versions, at which point you will end up w
Quoting Stefan Sperling <[EMAIL PROTECTED]>:
>flags=
> mtu 1500
>
> Would that be better?
IMHO, too much info packed in here, making reading difficult.
> Has anyone got better ideas?
What if there was a single line added, right after status for instance:
wol: (magic) unicast link multicast
On Wed, 28 Nov 2007, Gary Jennejohn wrote:
xpdf allows printing of page ranges. I use it all the time.
==
oh yeah... and kprinter, if you have it installed, can also do that, but
can act as a pipe with postscript files as an input ;)
kprinter < file.ps
it has most/all o
On Wed, Nov 28, 2007 at 07:45:45PM +0100, Stefan Sperling wrote:
> On Wed, Nov 28, 2007 at 10:28:24AM -0800, Sam Leffler wrote:
> > I really want to see the WOL support get into the tree.
>
> Cool.
>
> > I looked at it
> > before and had some issues with ifconfig integration which is mostly why
Yuri wrote:
Sorry about that.
Please find the logs below.
My system is upgraded from 6.3. And /lib/libpthread.so.2 is not a symlink.
But when I make it a symlink (ln -s /lib/libthr.so.3 /lib/libpthread.so.2)
I get another error, see log below.
Some requisite libs are compiled with /lib/libpthre
21 matches
Mail list logo
