This mail is not a spam but the automatic reply to your mail;
Subject:
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Thu, 7 Jul 2005 10:04:05 +0900
Message-Id: <[EMAIL PROTECTED]>
---
Sorry, your request
wasn't recognized
To get help, just send a mail
On Wed, 2005-07-06 at 00:29 -0700, Ade Lovett wrote:
> Niki Denev wrote:
> > From what i understand this is not exactly a FreeBSD problem, but rather
> > a consequence of U320 being really hard on the hardware with pushing it
> > to the limits.
>
> Incorrect. The relevant parts of the output you
Gerald wrote:
Summary: 2 Freebsd -stable machines. 1 is NAT/Gateway for the other...
These are from the machine behind the nat/gateway. Notice without
specifying what server to query with dig, it ignores /etc/resolv.conf
and queries localhost. What am I missing? (digs are trimmed to practical
On Wed, 6 Jul 2005, Charles Swiger wrote:
"What you are missing" is the right filename. :-)
That should be /etc/resolv.conf, not /etc/resolve.conf...
In the words of Homer Simpson: "DOH!"
Thanks for the accurate and quick reply.
Gerald
___
freebsd
On Jul 6, 2005, at 1:54 PM, Gerald wrote:
These are from the machine behind the nat/gateway. Notice without
specifying what server to query with dig, it ignores /etc/resolv.conf
and queries localhost. What am I missing? (digs are trimmed to
practical
information for brevity.)
Wed Jul 06 12:3
Summary: 2 Freebsd -stable machines. 1 is NAT/Gateway for the other. The
machine behind the gateway can not resolve DNS for anything that matters
like cvsup, but dig and nslookup resolve fine. By all appearances it's
ignoring /etc/resolv.conf and selectively answering programs. As a test,
a window
On Jul 6, 2005, at 6:29 PM, Blaz Zupan wrote:
On Wed, 6 Jul 2005, Kris Kennaway wrote:
That should be OK as long as you're not cross-compiling for different
architectures.
No, we only have i386 boxes.
Hi,
thanks for doing this work. I was working on preparing a similiar set
of informa
On Wed, 6 Jul 2005, Kris Kennaway wrote:
That should be OK as long as you're not cross-compiling for different
architectures.
No, we only have i386 boxes.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-s
On Wed, Jul 06, 2005 at 06:20:38PM +0200, Blaz Zupan wrote:
> On Wed, 6 Jul 2005, Kris Kennaway wrote:
> >Interesting, this seems to finger the TCP code. Are you compiling
> >your kernel with -O2 though (this causes bogus stack frames like you
> >have here)? If so, recompile with -O and try to ob
On Wed, 6 Jul 2005, Kris Kennaway wrote:
Interesting, this seems to finger the TCP code. Are you compiling
your kernel with -O2 though (this causes bogus stack frames like you
have here)? If so, recompile with -O and try to obtain another trace.
Nope, no funky compile options, all at the defa
On Wed, Jul 06, 2005 at 06:10:20PM +0200, Blaz Zupan wrote:
> On Wed, 6 Jul 2005, Kris Kennaway wrote:
> >Please obtain the backtrace with kgdb.
>
> Here you go:
> #9 0xc1fa0018 in ?? ()
> #10 0xc2a40010 in ?? ()
> #11 0x0010 in ?? ()
> #12 0xc2216000 in ?? ()
> #13 0xc0686a2c in tcbinfo ()
On Wed, 6 Jul 2005, Kris Kennaway wrote:
Please obtain the backtrace with kgdb.
Here you go:
[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.
GDB is free soft
On Wed, Jul 06, 2005 at 09:40:20AM +0200, Blaz Zupan wrote:
> If a developer is willing to investigate, I have:
> - the vmcore file from the crash (its size is 1GB)
> - the corresponding kernel, compiled with debug symbols
Please obtain the backtrace with kgdb.
Kris
pgpoFrkAp3yjc.pgp
Descripti
On Tuesday 05 July 2005 06:38 pm, Anders Nordby wrote:
> Hi John,
>
> From my console:
>
> FreeBSD 5.4-RELEASE-p2 #2: Wed Jul 6 00:01:31 CEST 2005
> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MASTER
> Timecounter "i8254" frequency 1193182 Hz quality 0
> CPU: AMD Opteron(tm) Processor 248 (2193.76-
"Daniel O'Connor" <[EMAIL PROTECTED]> wrote:
> On Tue, 5 Jul 2005 22:49, Fabian Keil wrote:
> > AFAIK, nobody has announced that the "old" way is death,
> > therefore I would like to know if the breakage is intentional
> > and if it is, if there's a technical reason why these methods
> > can no lo
Hi,
this is an automatic reply. Your message to this list
HAS BEEN REGULARLY DELIVERED.
However, some non-textual MIME parts have been stripped from it.
YOU DO NOT NEED TO RESEND THIS MESSAGE.
Most often, this may be due to the following conditions:
*
On Tue, Jul 05, 2005 at 10:48:55PM -0700, snort Snort wrote:
> Can anybody tell me what benefit for building a tap
> pseudo ethernet device driver for some sort of network
> communication? Why not directly communicate thru a
> "real" ethernet device driver like fxp0, xl0, etc.
Sometimes you want t
Since moving from 4.11 to 5.4 I have started seeing the occasional write
to a socket return with EINTR. This puzzles me, as looking at the man page
for siginterrupt it says that restarting the system call is the default
behaviour (and has been since BSD 4.2) if no data has been transferred. If
data
On Tue, Jul 05, 2005 at 10:48:55PM -0700, snort Snort wrote:
> Can anybody tell me what benefit for building a tap
> pseudo ethernet device driver for some sort of network
> communication? Why not directly communicate thru a
> "real" ethernet device driver like fxp0, xl0, etc.
A tap interface can
Have you tried to disable HTT? It's doesn't give you alot, and in some
cases it decreases performance.
Yes, there is absolutely no difference. Disabled HTT in the BIOS and in
FreeBSD, the box still crashes.
___
freebsd-stable@freebsd.org mailing lis
> I'm experiencing the same crashes as Matt, but on 5.4-RELEASE-p3. The machine
> is a HP DL380 G3 and it is heavily loaded (postfix mail server running
> amavisd-new with antivirus and antispam, so it has heavy IO and CPU load). It
> does not survive more than a couple of hours, while it is rock s
On Fri, 1 Jul 2005, Kris Kennaway wrote:
On Tue, Jun 28, 2005 at 11:26:06AM -0400, Matt Juszczak wrote:
After CPUID: 1, the machine locks cold and nothing else is printed to
the screen.
Try two things:
1) adding 'options KDB_STOP_NMI' to your kernel config.
I just learned that you also need
Niki Denev wrote:
> From what i understand this is not exactly a FreeBSD problem, but rather
> a consequence of U320 being really hard on the hardware with pushing it
> to the limits.
Incorrect. The relevant parts of the output you pasted are:
ahd
Seagate drives
Attaching more t
23 matches
Mail list logo
