On Sun, Jan 07, 2007 at 04:52:29PM +0100, Krzysztof Kowalik wrote:
> Hello.
>
> We are running an (IRC) server that under high-rate traffic (ie. DDoS
> attack) stops to respond to the network. The network remains locked up
> even after the original attack stops. However running tcpdump (which
> sw
On Tue, Jan 09, 2007 at 08:50:28AM -0800, Jeremy Chadwick wrote:
> On Tue, Jan 09, 2007 at 02:50:47PM +0100, Bruno Ducrot wrote:
> > On Tue, Jan 09, 2007 at 12:39:45PM +1030, Daniel O'Connor wrote:
> > > Has anyone had any success?
> > > I've tried healthd (0.7.9) but it can't show temps, eg..
> >
On Tue, 9 Jan 2007, John Baldwin wrote:
On Tuesday 09 January 2007 09:37, Sven Willenberger wrote:
On Tue, 2007-01-09 at 12:50 +1100, Bruce Evans wrote:
Oops. I should have asked for the statment in bge_rxeof().
#7 0x801d5f17 in bge_rxeof (sc=0x8836b000)
at /usr/src/sys/de
Just so you don't waste your time downloading, IA64 := Itanium. I don't
think you have one of those in your Gigabyte motherboard... unless
you're REALLY good with a soldering gun!
You should be using AMD64; term used to describe both Intel and AMD 64
bit x86 CPUs.
On Wed, 2007-01-10 at 00:15 +0800
On Tue, 2007-01-09 at 14:09 -0500, John Baldwin wrote:
> On Tuesday 09 January 2007 12:53, Sven Willenberger wrote:
> > On Tue, 2007-01-09 at 11:50 -0500, John Baldwin wrote:
> > > On Tuesday 09 January 2007 09:37, Sven Willenberger wrote:
> > > > On Tue, 2007-01-09 at 12:50 +1100, Bruce Evans wrot
> I'm having problems on one of two identical servers which have dual
> Broadcom BCM5704s onboard. The problem is that one of the servers is
not
> linking at 100baseTX-FDX on the bge0 interface no matter what I do
> (forced, limited advertising on the switch, etc).
>
> Upon further investigation I
On Jan 9, 2007, at 7:39 AM, valiy volodin wrote:
install /usr/ports/emulators/linux_base-fc4/
kldload aac_linux
give linux/cmdline/arcconf from Adaptec CD or ftp://deps.ru/pub/
arcconf
and run arcconf GETCONFIG 1
that doesn't work on aac(4) devices. aaccli usually does, and is
native fre
On Tue, Jan 09, 2007 at 06:37:16PM +0100, Oliver Fromme wrote:
> Guy Helmer wrote:
> > I think we've finally found the cause of the problem - it wasn't just
> > occurring after heavy use, but was visible right after filesystem
> > creation! We regularly built new filesystems with "newfs -U -O
On Tuesday 09 January 2007 12:53, Sven Willenberger wrote:
> On Tue, 2007-01-09 at 11:50 -0500, John Baldwin wrote:
> > On Tuesday 09 January 2007 09:37, Sven Willenberger wrote:
> > > On Tue, 2007-01-09 at 12:50 +1100, Bruce Evans wrote:
> > > > On Mon, 8 Jan 2007, Sven Willenberger wrote:
> > > >
Oliver Fromme wrote:
Guy Helmer wrote:
> I think we've finally found the cause of the problem - it wasn't just
> occurring after heavy use, but was visible right after filesystem
> creation! We regularly built new filesystems with "newfs -U -O 1 -b
> 65536 -f 8192"
Why are you using tho
On Tuesday 09 January 2007 09:37, Sven Willenberger wrote:
> On Tue, 2007-01-09 at 12:50 +1100, Bruce Evans wrote:
> > On Mon, 8 Jan 2007, Sven Willenberger wrote:
> >
> > > On Mon, 2007-01-08 at 16:06 +1100, Bruce Evans wrote:
> > >> On Sun, 7 Jan 2007, Sven Willenberger wrote:
> >
> > >>> The s
On Tue, 2007-01-09 at 11:50 -0500, John Baldwin wrote:
> On Tuesday 09 January 2007 09:37, Sven Willenberger wrote:
> > On Tue, 2007-01-09 at 12:50 +1100, Bruce Evans wrote:
> > > On Mon, 8 Jan 2007, Sven Willenberger wrote:
> > >
> > > > On Mon, 2007-01-08 at 16:06 +1100, Bruce Evans wrote:
> > >
I got an Apple Mac Pro (NOT MacBook Pro) to play with.
I tried to install FreeBSD and succeeded to a high degree of usefulness
on this Mac.
First problem was to open/close the CD tray reliable. Holding
down the 'F12' key while switching on the power makes it open the tray,
but one needs to be p
Guy Helmer wrote:
> I think we've finally found the cause of the problem - it wasn't just
> occurring after heavy use, but was visible right after filesystem
> creation! We regularly built new filesystems with "newfs -U -O 1 -b
> 65536 -f 8192"
Why are you using those blocksize and fragsiz
Bruce A. Mah wrote:
> If memory serves me right, LI Xin wrote:
>> Ken Smith wrote:
>>> On Thu, 2006-12-28 at 16:01 +0100, Thomas Herrlin wrote:
It still runs networking daemons into a frozen zoneli state on
heavy/(D)DOS network loads. Such processes cant be kill-9ed so there is
no wa
On Tue, Jan 09, 2007 at 02:50:47PM +0100, Bruno Ducrot wrote:
> On Tue, Jan 09, 2007 at 12:39:45PM +1030, Daniel O'Connor wrote:
> > Has anyone had any success?
> > I've tried healthd (0.7.9) but it can't show temps, eg..
> > julx2:/usr/src/sys/amd64/conf>sudo healthd -1 -D
>
> It seems we can get
I'm having problems on one of two identical servers which have dual
Broadcom BCM5704s onboard. The problem is that one of the servers is not
linking at 100baseTX-FDX on the bge0 interface no matter what I do
(forced, limited advertising on the switch, etc).
Upon further investigation I noticed th
If memory serves me right, LI Xin wrote:
> Not sure if the snapshot contained the changes, though... IIRC the
> January snapshot is not released yet?
The January CURRENT snapshots are being built and uploaded now. The
mirrors might have some of the architectures, but an announcement will
come o
On 1/9/07, Mars G. Miro <[EMAIL PROTECTED]> wrote:
On 1/9/07, LI Xin <[EMAIL PROTECTED]> wrote:
> Mars G. Miro wrote:
> > Greetz!
> >
> > I happen to play w/ a newish Gigabyte mobo that has an on-board
> > Marvell 8053 GigE NIC. FreeBSD 6.2-BETA2 i386, amd64 does not seem to
> > support it. Does
Mars G. Miro wrote:
> On 1/9/07, LI Xin <[EMAIL PROTECTED]> wrote:
>> Mars G. Miro wrote:
>> > Greetz!
>> >
>> > I happen to play w/ a newish Gigabyte mobo that has an on-board
>> > Marvell 8053 GigE NIC. FreeBSD 6.2-BETA2 i386, amd64 does not seem to
>> > support it. Does anyone know if this is su
On 1/9/07, LI Xin <[EMAIL PROTECTED]> wrote:
Mars G. Miro wrote:
> Greetz!
>
> I happen to play w/ a newish Gigabyte mobo that has an on-board
> Marvell 8053 GigE NIC. FreeBSD 6.2-BETA2 i386, amd64 does not seem to
> support it. Does anyone know if this is supported? I'm currently
> taking a look
If memory serves me right, LI Xin wrote:
> Ken Smith wrote:
>> On Thu, 2006-12-28 at 16:01 +0100, Thomas Herrlin wrote:
>>> It still runs networking daemons into a frozen zoneli state on
>>> heavy/(D)DOS network loads. Such processes cant be kill-9ed so there is
>>> no way to recover from it. (thin
install /usr/ports/emulators/linux_base-fc4/
kldload aac_linux
give linux/cmdline/arcconf from Adaptec CD or ftp://deps.ru/pub/arcconf
and run arcconf GETCONFIG 1
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebs
On Tue, 2007-01-09 at 12:50 +1100, Bruce Evans wrote:
> On Mon, 8 Jan 2007, Sven Willenberger wrote:
>
> > On Mon, 2007-01-08 at 16:06 +1100, Bruce Evans wrote:
> >> On Sun, 7 Jan 2007, Sven Willenberger wrote:
>
> >>> The short and dirty of the dump:
> >>> ...
> >>> --- trap 0xc, rip = 0xfff
Thanks
-- In Response to your message -
> Date: Tue, 09 Jan 2007 21:52:44 +0800
> To: "J. W. Ballantine" <[EMAIL PROTECTED]>
> From: LI Xin <[EMAIL PROTECTED]>
> Subject: Re: Fatal Trap 12 in 6.2-PRERELEASE
>
> This is an OpenPGP/MIME signed message (RFC 2440 and 31
Hi,
On Tue, Jan 09, 2007 at 12:39:45PM +1030, Daniel O'Connor wrote:
> Has anyone had any success?
> I've tried healthd (0.7.9) but it can't show temps, eg..
> julx2:/usr/src/sys/amd64/conf>sudo healthd -1 -D
It seems we can get directly different temperatures from the CPU. At
least this works f
J. W. Ballantine wrote:
> Yes, I saw the thread and I did a cvsup prior to rebuilding everything.
> What I'm asking about is the best way to get the system working again.
>
> Is it a reinstall, or is there a simple way to put a working kernel
> in?
Simplest way would be to boot from /boot/kernel.
Yes, I saw the thread and I did a cvsup prior to rebuilding everything.
What I'm asking about is the best way to get the system working again.
Is it a reinstall, or is there a simple way to put a working kernel
in?
Jim
-- In Response to your message -
> Date: Mon, 8 Jan
Mars G. Miro wrote:
> Greetz!
>
> I happen to play w/ a newish Gigabyte mobo that has an on-board
> Marvell 8053 GigE NIC. FreeBSD 6.2-BETA2 i386, amd64 does not seem to
> support it. Does anyone know if this is supported? I'm currently
> taking a look at http://people.freebsd.org/~yongari/msk/ ,
Greetz!
I happen to play w/ a newish Gigabyte mobo that has an on-board
Marvell 8053 GigE NIC. FreeBSD 6.2-BETA2 i386, amd64 does not seem to
support it. Does anyone know if this is supported? I'm currently
taking a look at http://people.freebsd.org/~yongari/msk/ , tho this
NIC isnt mentioned the
30 matches
Mail list logo
