n this mailing list when somebody looks for
good SATA cards (Re: 3ware, 3ware, ...), I replied myself too.
So are there any success stories with 3ware 9550SX (SATA II) and dual
AMD Opteron server boards, or it's time to go back with Intel?
Regards,
Atanas
Atanas wrote:
Has anyone exper
latest one released as 9.3.0.7 on the 3ware website.
Yesterday flashed and rebooted them all, and this morning I got the next
crash.
Regards,
Atanas
On 11/14/06, Atanas <[EMAIL PROTECTED]> wrote:
Has anyone experiencing this:
twa0: ERROR: (0x05: 0x2018): Passthru request tim
el
> options BREAK_TO_DEBUGGER
> options DDB
> options KDB
> options KDB_UNATTENDED
> options IPFIREWALL
> options DUMMYNET
I'm attaching the dmesg.boot following the latest crash.
Regards,
Atanas
Copyright (c) 1992-2006 The FreeBSD Project.
Copyright (c) 1979, 1
ng once a week or so with QUOTAS
enabled and SNAPSHOTS disabled (i.e. background_fsck="NO" in rc.conf).
Since upgrading to 6-STABLE I got 10 days of uptime and no crashes so far.
Regards,
Atanas
___
freebsd-stable@freebsd.org mailing li
Sergey Matveychuk said the following on 7/12/06 10:57 PM:
Atanas wrote:
Please, don't get me wrong. I'm not asking for help or for a workaround.
I'm actually trying to help identifying a problem or regression.
If this is not a bug, but a feature change, please have it documen
Sergey Matveychuk said the following on 7/12/06 3:24 AM:
Atanas wrote:
Sergey Matveychuk said the following on 7/11/2006 10:08 PM:
Atanas wrote:
Recent portupgrade versions no longer obey the -M command line switch,
i.e. any optional arguments to be prepended to each make command.
How to
Sergey Matveychuk said the following on 7/11/2006 10:08 PM:
Atanas wrote:
Recent portupgrade versions no longer obey the -M command line switch,
i.e. any optional arguments to be prepended to each make command.
How to reproduce:
# portinstall -M "APACHE_HARD_SERVER_LIMIT=1024" ww
Matthias Andree said the following on 7/11/06 1:48 PM:
Atanas <[EMAIL PROTECTED]> writes:
Recent portupgrade versions no longer obey the -M command line switch,
i.e. any optional arguments to be prepended to each make command.
How to reproduce:
# portinstall -M "APACHE_HARD_SERVER
1-RELEASE (2.0.1_1) seems to work as
expected.
I tried all CVS versions after that (with portdowngrade) and found that
the breakage has happened somewhere between 2.1.0 and 2.1.1 (2006/06/02
- 2006/06/04).
Regards,
Atanas
___
freebsd-sta
tched driver enough to see whether it performs as expected.
But in overall it looks good. I guess some more testing might be needed
in order to merge the patch into the source tree.
Regards,
Atanas
Index: if_em.c
==
module I intentionally appended " (patched)" to its version
string in if_em.c, and could see that in dmesg every time I loaded the
module:
em1:
Regards,
Atanas
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailma
;s put that aside for now.
Regards,
Atanas
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
d systems could be a serious
hurdle after a crash or reboot.
Regards,
Atanas
--- if_em.c.origFri May 19 09:19:57 2006
+++ if_em.c Thu Jul 6 11:10:56 2006
@@ -657,8 +657,9 @@
mtx_assert(&a
Pyun YongHyeon said the following on 6/30/06 8:54 PM:
On Fri, Jun 30, 2006 at 12:28:49PM -0700, Atanas wrote:
> User Freebsd said the following on 6/29/06 9:29 PM:
> >
> >The other funny thing about the current em driver is that if you move an
> >IP to it from a
he fsck source and somehow change the
default '-y' behavior. But I wouldn't like to carry such additional
luggage of custom patches on all servers and also I don't think that I
am the most qualified person to do so.
So in case someone still reads this, please advice.
Regards,
At
long as
fxp works, this is a non-issue for me.
Regards,
Atanas
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
#x27;t working as expected, I don't
remember the specifics), while the one coming with 4.x did, so we ended
up installing 4.11 then.
Regards,
Atanas
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
Michael Vince said the following on 6/29/06 8:53 PM:
The thing that have to ask is if Atanas has 100's why can't he just boot
Freebsd have have them all prebound to the interface at startup, why
would you need to add and remove them constantly by the hundreds during
normal server u
ave some newer machines with 2 Broadcom chips on-board. I plan to
give them a try at some point in the future, but I'm not sure how stable
the bge driver is when compared to fxp and em.
Regards,
Atanas
___
freebsd-stable@freebsd.org mailing list
http:/
ded server running
6.1-PRERELEASE (BETA2 based on 6-STABLE) from Mar 1 with manually
patched sys/ufs/ufs/ufs_quota.c (1.74.2.1 2006/01/14) with a similar
diff generated from CURRENT between 1.77 and 1.80.
55 days uptime and no problems so far.
Regards,
Atanas
P.S. Forgot to CC the list, sorry for the d
Regards,
Atanas
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ities that let you manage while the OS is running that folks have had
good luck with? I've been happy with the megaraid series on linux at my
job, but I'm wondering if the management utilities are there on freebsd,
etc.
3ware.
Regards,
Atanas
__
# Delay (in ms) before probing SCSI
> options QUOTA
> options SMP # Symmetric MultiProcessor Kernel
PAE:
> options IPFIREWALL
> options DUMMYNET
Regards,
Atanas
__
If I tell the kernel I've 4 Go the system don't boot (kernel panic).
What can I do.
You might need to compile a PAE enabled kernel, see the pae(4) man page
for more details.
Regards,
Atanas
___
freebsd-stable@freebsd.org mailing list
ht
Mike Tancsa said the following on 02/17/06 11:50:
At 09:17 PM 16/02/2006, Atanas wrote:
Does anybody know whether ipfw (or something else within FreeBSD-4) is
capable of setting connection rate limits?
Why not just launch sshd out of inetd ?
Primarily because of the big scare sign in the
Marian Hettwer said the following on 02/17/06 00:39:
Atanas wrote:
Last year I already had to decrease the LoginGraceTime from 120 to 30
seconds on my production boxes, but it didn't help much, so on top of
that I got to implement (reinvent the wheel again) a script tailing the
auth.lo
Carl Makin said the following on 02/16/06 20:07:
Atanas wrote:
Does anybody know whether ipfw (or something else within FreeBSD-4) is
capable of setting connection rate limits?
I'm using SEC to monitor the auth.log file and block any IP addresses
that fail a password 3 times with
r key (takes seconds and CPU) on every
incoming ssh connection, which would be kind of slow and wasteful.
Regards,
Atanas
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any ma
unately it wasn't available in FreeBSD-4.x, and I still
have plenty of such boxes.
Does anybody know whether ipfw (or something else within FreeBSD-4) is
capable of setting connection rate limits?
Regards,
Atanas
___
freebsd-stable@freebsd.org ma
key length in FreeBSD-6 however just got doubled from
1024 to 2048-bit. I believe there's a reason for that and don't like the
idea of going down.
Regards,
Atanas
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
e to have something like for instance the sendmail's client
and rate connection limits, but I guess this is not the right place to ask.
Regards,
Atanas
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-s
ary/021693.html
All of the possible workarounds I know are limited to the following:
- disable SMP
- disable QUOTA support
- downgrade to 5.4(-STABLE)
This should have been in errata since mid Nov 2005.
Regards,
Atanas
I setup a serial console and go into ddb and get:
KDB: enter: Line break
oxes
running 6-STABLE (SMP with QUOTA enabled) and the only way I found to
stop them crashing was switching back to 5.4.
I hope this will get fixed in 6.1.
Regards,
Atanas
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/l
box from it, and install over the network.
I haven't tried the latter myself, but already used a nanobsd based USB
flash drive as emergency recovery media on a 9550SX based box, and it
worked.
Regards,
Atanas
___
freebsd-stable@freebsd.org mail
s thinking about trying the kernel stress suite first. Or just have
something rsync-ing lots files back and forth (possibly over the
network), run apache bench in a loop and point it to some database
intensive page, etc.
Regards,
Atanas
___
freebsd-stabl
Atanas said the following on 12/12/05 18:57:
Peter Jeremy said the following on 12/12/05 13:40:
>> When it hangs, break into DDB (Ctrl-Alt-Esc on the console or BREAK on
>> a serial console).
>>
> But if I have no keyboard response I won't be able to save it, ri
Atanas said the following on 12/12/05 15:43:
Ronald Klop said the following on 12/12/05 13:27:
What happens if you set one of these sysctl values to 0? (This
disables SMP changes from 5.4 to 6.0.)
debug.mpsafevfs: 1
debug.mpsafenet: 1
debug.mpsafevm: 1
Thanks for the suggestion!
I just
on the downgrade, but most likely I will have at
least one of these 2 machines still running 6.x during the next day or two.
After the downgrade we could eventually set a test bed and start
hammering it with requests. The problem would be how to trigger the
crash and whether we would be able
e problem still persists.
I hope I won't be forced to downgrade to 5.4, though I'm already working
on that (just in case).
Regards,
Atanas
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
nes I have problems with are way less loaded, and are
supposedly faster ones.
Thanks for your suggestions!
Regards,
Atanas
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any ma
w the only reasonable option for me (I mean for production and in
relatively short term) seems going downward to 5.4 and wait until 6.x
get more stable
Two dmesg.boot files attached.
Any comments, suggestions and questions are welcome.
Regards,
Atanas
Copyright (c) 1992-2005 The FreeBSD Project.
C
41 matches
Mail list logo
