Dear All,
my 6.0-STABLE always panic when "make buildworld"
heres the dump:
lapi# kgdb kernel.debug vmcore.0
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:
Undefined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
On 30 Nov, Dan Charrois wrote:
> This is encouraging - it's the first I've heard of someone who has
> found a way to trigger the problem "on demand". The problems I was
> experiencing were on a dual Xeon with HTT enabled as well.Perhaps
> someone out there who knows much more about the i
On 22 Nov, Greg Rivers wrote:
> On Mon, 21 Nov 2005, Kris Kennaway wrote:
>
>> It may not be the same problem. You should also try to obtain a trace
>> when snapshots are not implicated.
>>
>
> Agreed. I'll do so at the first opportunity.
>
>
>> 'show lockedvnods' is very important for diagn
On 26 Nov, Tor Egge wrote:
>
>> Thanks Kris, these are exactly the clues I needed. Since the deadlock
>> during a snapshot is fairly easy to reproduce, I did so and collected this
>> information below. "alltrace" didn't work as I expected (didn't produce a
>> trace), so I traced each pid asso
> Attempting to catch up with my backlog of unread email, only 12K unread
> messages to go ...
>
> On 24 Nov, Rob wrote:
>
>> I have cvsup'ed the sources to STABLE as of Nov. 23rd
>> 2005.
>> After recompiling/installing world and debug-kernel,
>> I again get a kernel deadlock when using swapfile:
On 26 Nov, Tor Egge wrote:
>
>> Thanks Kris, these are exactly the clues I needed. Since the deadlock
>> during a snapshot is fairly easy to reproduce, I did so and collected this
>> information below. "alltrace" didn't work as I expected (didn't produce a
>> trace), so I traced each pid asso
On 2 January 2006, Jack Raats wrote:
/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:89:in `<<': failed to allocate
memory (NoMemoryError)
from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:89:in `trace'
from /usr/local/sbin/portupgrade:723:in `do_upgrade'
from /usr/local/sbin/
Hey David!
[Mitch says:]
> The handbook document should point to
> ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/ instead (I think there's a
> problem report with a patch under review).
>
> Yes, the -STABLE branch exists. That's how you would patch a 6.0-RELEASE
> system: using cvsup(1) to follow
6.0-Stable as of 12/11.
% netstat -anf inet
% netstat -anf inet6
%
I have connections to several systems and a few daemons listening, both
INET and INET6. Since my last upgrade, I can't see them with netstat.
Has anyone else seen this?
(For the record, I DO see lots of UNIX sockets if I don't s
A few hours ago, my customers graid3 array crashed due one hard-drive
loss and it's unable to recover. The data is easily replaceable so no
loss of sleep for that but I'd really like to hear some ideas what
happened, if possible.
Since this was 'do-it-cheaply', we got 3x160G seagates, all old
Mitch,
On Mon, 2 Jan 2006, Mitch (Bitblock) wrote:
> > > From: "Mitch \(Bitblock\)" <[EMAIL PROTECTED]>
> > > Date: Sun, 1 Jan 2006 16:15:57 -0800
> > > Sender: [EMAIL PROTECTED]
> > >
> > > The handbook
> > > (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-
> > stable.ht
> > >
On 17 Nov, Kris Kennaway wrote:
> On Thu, Nov 17, 2005 at 04:33:50PM -0800, Rob wrote:
>> --- Kris Kennaway <[EMAIL PROTECTED]> wrote:
>> >
>> > I commented on it elsewhere in this thread.
>>
>> Do you mean your comment on the swap_pager error:
>>
>> Quote:
>> "AFAICT that is just a trigger-hap
Attempting to catch up with my backlog of unread email, only 12K unread
messages to go ...
On 24 Nov, Rob wrote:
> I have cvsup'ed the sources to STABLE as of Nov. 23rd
> 2005.
> After recompiling/installing world and debug-kernel,
> I again get a kernel deadlock when using swapfile:
>http://
> > From: "Mitch \(Bitblock\)" <[EMAIL PROTECTED]>
> > Date: Sun, 1 Jan 2006 16:15:57 -0800
> > Sender: [EMAIL PROTECTED]
> >
> > The handbook
> > (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-
> stable.ht
> > ml#STABLE) references
> ftp://snapshots.jp.FreeBSD.org/pub/FreeBSD/s
Hi,
Running the new portupgrade 2.0.0,1 gives the following errors:
orac# portupgrade -Na
[Updating the portsdb in /usr/ports ... - 13945 port
entries found
.1000.2000.3000.4000.5000.6000.7000.8000.9000.1..
Hi,
Running the new portupgrade 2.0.0,1 gives the following errors:
orac# portupgrade -Na
[Updating the portsdb in /usr/ports ... - 13945 port
entries found
.1000.2000.3000.4000.5000.6000.7000.8000.9000.1..
16 matches
Mail list logo
