On Feb 7, 2008 8:40 AM, Joe [EMAIL PROTECTED] wrote:
On Feb 6, 2008, at 5:45 PM, Need Coffee wrote:
Does anyone run OpenBSD on blade servers? I don't mean
Sun Blade 150 kind of hardware, but rather blade chassis
with server blades (a la Sun Blade 8000, HP, Dell, etc.).
I'd appreciate
On Nov 6, 2007 2:08 PM, Chris Harper [EMAIL PROTECTED] wrote:
I recently installed 4.2 release on my evga 680i based motherboard ,
which uses nfe(4) for the onboard gig NIC's.
There seems to be an issue in the handling of the autodetection of
media types and the speed it can run at when
On 7/6/07, Todd Pytel [EMAIL PROTECTED] wrote:
I'm going to be running a few OpenBSD virtual machines and was wondering
whether there was any performance difference between using IDE or SCSI
virtual disks. From what I can tell, the SCSI option has been supported
longer, though IDE has also been
On 7/2/07, David Burau [EMAIL PROTECTED] wrote:
Hi,
I'm shure it's just a very small problem, but i can't figure out, what to do.
Im runnig OpenBSD 4.0 and i don't know how to set the PATH in xterm. I want to
set it to $HOME/bin. The Shell is ksh. In the console it works, but not in
xterm.
On 6/24/07, patrick keshishian [EMAIL PROTECTED] wrote:
Hi,
I've been noticing some strange problems with the built-in nfe0
interface on my desktop. Actually I've seen it on two such
computers, but the description below is for my current desktop PC.
The PC is running `cvs up -dP
As some of you know, there is a hardware compatibility list at
http://www.armorlogic.com/oscl which provides information about
major/stock hardware and OpenBSD compatibility.
Some of the previously tested configuration are badly out-of-date or
are misinformative. Especially the configurations
i am considering a Dell PE 860 1u rack server for usage as my network
storage server (nfs).
I wonder about reports from the openbsd comunity using it with openbsd
4.0/4.1 on stability and performance. What you guys/girls have to
report? It is worth its price?
I don't run one myself, but got
On 5/9/07, Daniel Ouellet [EMAIL PROTECTED] wrote:
I increase the number of contiguous connection only by 5, from 305 to
310, and you get 3 times slower response for always the same thing and
repeated all the time. Very consistent and from different clients as well.
You can do any variation of
On 5/3/07, Daniel Ouellet [EMAIL PROTECTED] wrote:
If I may ask, how the Sun Integrated Lights Out Manager (ILOM) on this
X4100 box compare to the regular LOM of the Sparc 64 series?
Power cycle and possible to do full remote install via console as well
like the regular Sun?
I don't know
On 3/31/07, Eric Dillenseger [EMAIL PROTECTED] wrote:
I tried different ModeLine generators from the net, and tried to do it
myself using Xorg' logfile. Not helping me out.
I have a Dell 20 inch monitor and it works fine with it's native
1680x1050. I had to tweak the Modeline manually but
On 3/2/07, Victor Abeytua [EMAIL PROTECTED] wrote:
Trying to solve this problems I've noticed that the /sys link is
broken. In other words, directory /usr/sys doesn't exist. Probably this
has to be an installation error, but I would like to know if there is
someway to fix, that is, without
On 3/1/07, Brian Martinez [EMAIL PROTECTED] wrote:
I was curious about the maximum amount of RAM an OpenBSD system will
recognize. Is there any way at all to get it to recognize more? Kernel
recompile? Sysctl options?
No. However, you can compile an i386 kernel with PAE which should
I have a 326m running 3.9/amd64 for months without a glitch. Dmesg
below. Perhaps something changed after 3.9 that causes the before
mentioned problems.
OpenBSD 3.9-stable (GENERIC.MP) #7: Mon Aug 21 10:28:18 CEST 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem =
On 2/21/07, Craig Barraclough [EMAIL PROTECTED] wrote:
Running inside VMware ESX2.5.1, kernel from 16FEB, I was just getting
ready to gather info on why the box was crashing with vic(4) enabled,
and this crash happened.
vic(4) apparently has issues. It crashes on VMware Server 1.01 running
According to VMware, you'll need AMD64 CPUs that are made using 90nm.
That should be the only requirement. I too test my 64-bit OpenBSD
guests on a Linux host running CentOS 4.4 (2.6.9-42.0.2.EL kernel).
i386 works like a charm. amd64 performs like a VAX.
However, I've tested NetBSD/amd64 (2.0 I
Just to follow up with some basic numbers. I run a perl program which
executes uname -a 20 times while running vmstat 1 in another
terminal. Notice vmstat reporting blocked processes in the run. Output
below.
$ time perl -e 'for($i=0;$i20;$i++) { print $i: .`uname -a`; }'
0: OpenBSD
tried i386 with PAE, during dmesg it has:
real mem = 12884197376 (12582224K)
avail mem = 2784165888 (2718912K)
You should have all the RAM (from real mem) available. It's just
reporting on avail mem on boot that's not entirely correct. That's
what mickey@ told me at least.
On 12/1/06, jared r r spiegel [EMAIL PROTECTED] wrote:
working on getting a dual core dual cpu 64b 2MB cache
xeon 2.8GHz w/12GB RAM and dual copper em(4) put
in place in front of our MX vip for a greylisting spamd(8).
i've got a similar machine with faster CPU ( 3.0 GHz / 4MB )
but
The system seems to run stable until I put load on the multiport fiber
adapter. I recompiled the entire operating system with no issues.
Try moving the adapter to another port. Also, some fixes went into
-current recently fixing some em(4) issues. You could be hitting a
bug.
Did you get
I have deployed several X4200 on 3.9 (with mpi(4) backported from
4.0). AFAIK, X4200 == X4100. It just has some more PCI slots.
When booting, RTC BIOS diagnostic error 2 is displayed, I'm not sure if
that's relevant.
You might want to investigate that. Not sure, but I don't remember
seeing
IBM changed their entire (almost) lineup of X-series servers. It seems
that most of the SCSI/SAS variants now have ServeRAID/Adaptec chips,
which makes them unusable on OpenBSD. X3455, oddly, has an LSI1064 SAS
and should work fine.
Anyways, I got my hands on one with SATA. And it just works.
IBM changed their entire (almost) lineup of X-series servers. It seems
that most of the SCSI/SAS variants now have ServeRAID/Adaptec chips,
which makes them unusable on OpenBSD. X3455, oddly, has an LSI1064 SAS
and should work fine.
Just to correct myself. x3200 and x3250 (both available with
#ifdef DIAGNOSTIC
if (scd-sc_in_rep_size != cc)
printf(%s: bad input length %d != %d\n,USBDEVNAME(sc-sc_dev),
scd-sc_in_rep_size, cc);
#endif
A more correct fix is to change the line to something like this. It's
still not the most correct fix, but
On 9/20/06, Rafael Morales [EMAIL PROTECTED] wrote:
I use OpenBSD 3.8 on a Powerbook G4, and when I
connect my USB external hard drive, this is my output:
Sep 20 12:10:41 Apocalypsis /bsd: umass0 at uhub0 port
1 configuration 1 interface 0
Sep 20 12:10:43 Apocalypsis /bsd:
Sep 20 12:10:43
On 8/10/06, Russell McGregor [EMAIL PROTECTED] wrote:
Having said that, I will still try loading an amd64 snapshot and see
if that boots MP.
Unless something changed after 3.9, it both boots and runs MP fine,
also under heavy load. I tested on x4200, but it should be the same
for 4100.
Have
You can try netperf. It works fine. Snippet below shows the results of
the network thruput between 2 Opteron boxes running 3.9 with bge/em
gigabit cards.
[EMAIL PROTECTED]:/home/ssehic$ netperf -H x2100 -l 300 -- -s 64K -m 64K -M
64K -S 64K
TCP STREAM TEST to 192.168.0.61
Recv SendSend
On 8/9/06, Russell McGregor [EMAIL PROTECTED] wrote:
I am doing some testing on a Sun x4100 on loan to us from a vendor, I
have loaded up a snapshot from about 20060803 and everything seems to
run fine from the standard /bsd kernel image, but it panics when
trying to boot bsd.mp. I updated src
This is know. Workaround is to install via FTP (with pcibios disabled)
or use amd64 version. That, AFAIK, works fine.
More details at
http://www.armorlogic.com/openbsd_information_server_compatibility_list.html?action=detailid=x336
On 8/1/06, riwanlky [EMAIL PROTECTED] wrote:
Hai All,
I am
On 6/8/06, stan [EMAIL PROTECTED] wrote:
Has anyone gotten teh nfe port on a Sun 2100 to work on 19M? I have one of
these, that I am setting up as a firewall between 2 legacy networks, both
of which are 10M, and when I plug that port into the 10M hub, I get
continuing kernel error messages.
I'm
Try to disable pcibios via boot -c bsd.mp. Worked for me in several occasions.
On 5/28/06, Antoine Jacoutot [EMAIL PROTECTED] wrote:
On Sun, 28 May 2006, Christian Pedaschus wrote:
Just finished fun/test installing 3.9 mp on a x4000 and seeing the same
message.
Glad to know I'm not the only
Just wanted to let you know that OpenBSD server compatibility list has
recently been updated with our 3.9-stable (and some -current) test
results on a couple of standard servers.
Boxes updated with 3.9 test results include:
- IBM xServer 336 (new entry)
- IBM eServer 326m
- Sun x2100
- Dell
On 5/11/06, Didier Wiroth [EMAIL PROTECTED] wrote:
Hello,
I'm currently using a thinkpad 60s
Dual booting between xp and current, yes currently still required ;-)) see below
Here is a short rundown:
a) Performance is nice with bsd kernel, performance is degraded with bsd.mp
b) sound chip
I can confirm that PS/2 keyboard also stops responding with MP kernels
(3.9-STABLE/amd64) on Dell SC1425. However, USB keyboards work fine.
Use that instead.
On 5/2/06, Okan Demirmen [EMAIL PROTECTED] wrote:
Hi - So I have this wierd problem, which is duplicated on 3 identical
machines, where I get a bunch of bmc_io_wait fails messages (see the
end of the dmesg). The longer the machine is on, the more messages get
tacked on. I'm wondering what this
While booting bsd.mp I noticed the following output:
ioapic0: pin 11 shares different IPL interrupts (40..50), degraded performance
Disable pcibios (boot bsd.mp -c; disable pcibios; quit;) and see if
the degraded performance message goes away. I bet it will, and your
bsd.mp performance problems
Look at:
http://www.armorlogic.com/openbsd_information_server_compatibility_list.html?action=detailid=x2100
The only *real* issue left is the nvidia network card puking under
major load, but that might have been solved by the last commit (past
3.9-STABLE) by [EMAIL PROTECTED] I haven't got my
On 4/19/06, Jonathan Gray [EMAIL PROTECTED] wrote:
That is totally out of date for 3.9, everything except the x4200 should
be fine.
Yes. Especially the HP hardware, since most of the problems were
caused by missing PCI bridges that should be fixed now.
As soon as I get my 3.9 CDs from Wim,
On 4/15/06, Jurjen Oskam [EMAIL PROTECTED] wrote:
nfe0: tx v2 error 0x6004
nfe0 at pci0 dev 10 function 0 NVIDIA CK804 LAN rev 0xa3: irq 3, address
00:13:d4:ae:99:b7
eephy0 at nfe0 phy 9: Marvell 88E Gigabit PHY, rev. 2
That's weird, since nfe(4) worked fine in the X2100 Sun box I
On 4/14/06, Nick Holland [EMAIL PROTECTED] wrote:
http://www.openbsd.org/cgi-bin/cvsweb/src/gnu/usr.sbin/sendmail/libsm/fflush.c
OPENBSD_3_9_BASE is tagged...and that's it. (well..usually. I'm sure
there's some exception somewhere...)
The patches were put into OPENBSD_3_9 (a.k.a.,
On 4/14/06, Nick Holland [EMAIL PROTECTED] wrote:
No. All patches past the _BASE tag always go into -STABLE. In this
case, correctly into OPENBSD_3_9. This is not special AFAIK.
*sigh*
HELLO... Topic is WHEN they go in.
3.9 is not official yet. This patch set went into -stable already.
On 4/3/06, Brian [EMAIL PROTECTED] wrote:
I just did a fresh install of 3.9-current. And part of the dmesg is coming
across oddly. I am not sure what else to say about it. It's the iic0 and
iic1.
It's just the new sensors framework telling you that it has
encountered an unsupported sensor
I personally tested a DL360 G4 with SAS/P600 and it worked like a
charm (after a small patch I've sent; this is in 3.9-STABLE).
Actually, ciss(4) doesn't really care if the controller is SAS or not.
It just works, unlike LSI mpt(4). There is some hacking going on to
add SAS support for it. If all
Has anybody a 'High performance IPSec and SSL accelerator PCI card with Cavium
CN1010' running on OpenBSD?
I am looking for a crypto card and it could be an option but it isn't in the
hardware supported list in http://www.openbsd.org/i386.html#hardware
Some crypto cards are based on a
Who wins in the OpenBSD world? DRAC (Dell Remote Admin Card) or iLo
(HP's Integrated Lights Out)? We're looking at new servers and are
wondering if these are worth the cash, or which is the one to go for?
I've never used DRAC, but ILO (the real deal, like in HP360G4) is
pretty solid. Stay
Is anyone working on supporting the SAS-versions of the LSI controllers
at the moment, or should I look for a different server for the time being?
AFAIK, dlg@ is working on it.
On 3/14/06, edgarz [EMAIL PROTECTED] wrote:
Looks good!
but what is that:
Compaq iLO rev 0x01 at pci1 dev 2 function 0 not configured
Compaq iLO rev 0x01 at pci1 dev 2 function 2 not configured
That's just Integrated Lights Out stuff. You don't need that from OpenBSD.
And yes, we are
On 3/14/06, Bryan Allen [EMAIL PROTECTED] wrote:
Sunfire X2100? They're Opterons, not Pentiums, but...
Has issues, but has no showstoppers. Unless you put your nfe(4) card
under stress.
Look at http://www.armorlogic.com/oscl/ for all the details.
On 3/14/06, edgarz [EMAIL PROTECTED] wrote:
I will be a very happy if those two servers (DL 145 and DL 385) will
work. Means hardware will detect and work without strange things, like a
slow hdd system, unusable raid or similar crap :)
I would choose the SCSI version of DL145 G2, since SATA
You're lucky that your RAID1 array even works, since integrated
mirroring (IM) is currently not supported by mpt(4) driver. If it
works, it is slow like hell.
If you want speed, remove the RAID1 array and run with 2 normal disks.
On 3/13/06, Adam Papai [EMAIL PROTECTED] wrote:
Hi misc,
I've
On 2/22/06, Jonathan Gray [EMAIL PROTECTED] wrote:
2) nfe(4) shows a constant 100/interrupts a seconds without having
a link; only configured with ifconfig nfe0 127.0.0.1 255.0.0.0; it also has
the same interrupt rate when configured normally
This should be fixed in -current by damien.
For those interested, here are the preliminary results of my Sun x2100
tests. More hardware tests results available at
http://www.armorlogic.com/oscl/
Issues with Sun X2100 running OpenBSD/amd64 (-current from 22/02/2006)
1) possible bsd.mp issues due to misconfigured apic's
ioapic0 at mainbus0
Look at http://www.armorlogic.com/oscl/. There is an dmesg for
e326m/SCSI version.
To answer your question. Don't create any kind of logical volume
(RAID0/1), just use the physical disks. In short, IM (integrated
mirroring) is _not_ supported. It is, however, being worked on.
My e326m/SCSI
The latest, which is, AFAIK, 2.58.
On 2/8/06, Jason Houx [EMAIL PROTECTED] wrote:
Srebrenko,
What firmware are you using on your controller?
Jason
On Wed, 8 Feb 2006, Srebrenko Sehic wrote:
You can also try to update to -rOPENBSD_3_8. All noticeable
performance problems went away
You can also try to update to -rOPENBSD_3_8. All noticeable
performance problems went away with some important patches since the
release.
I bet you'll see the load go away. And yes, as Henning said, 200
interrupts/second is nothing. My ciss(4) controllers go up to 5000
interrupts/seconds. But
On 2/3/06, Badbanchi Hossein [EMAIL PROTECTED] wrote:
Hi,
This morning I installed the kernel from the snapshot.
The only (cosmetic) difference is that the time-out values are reduced, so
it doesn't take that long as before for the system to boot, but
the BCM5752 NIC is still not
Try a -current snapshot. Some important bge(4) fixes went into the
tree after 3.8.
On 2/2/06, Badbanchi Hossein [EMAIL PROTECTED] wrote:
Actually the NIC doesn't work properly. I can ssh to the box, but even output
of
a simple ls command takes seconds to appear on the screen, and gets
Damn, talk about beeing unlucky. My test came 1 day before the new
patch. I started to look into this myself. I guess Brad beat me to it.
Great work, less work for me :)
I'll update the OSCL. Thanks to Daniel as well for testing.
On 2/1/06, Brad [EMAIL PROTECTED] wrote:
Hey, update the bge
I finally got a hold of a new Sun X4200 Opetron server. Bad news for
anybody how likes Sun hardware: our mpt(8) driver doesn't support the
SAS/SCSI controller resulting in no go condition. Everything else
seems to work.
OSCL (OpenBSD Server Compatibilty List) is updated with this
information.
On 1/17/06, Bill Marquette [EMAIL PROTECTED] wrote:
OSCL (OpenBSD Server Compatibilty List) is updated with this
information. Find it at:
http://www.armorlogic.com/openbsd_information_server_compatibility_list.html
You might want to retest the DL380 G4 - I have dozens of these running
On 12/29/05, Jon Hart [EMAIL PROTECTED] wrote:
Great, I'll give that a shot today after I see if I can repeat the
crash. Do you happen to know what date the commit was done? I checked
MARC and couldn't seem to find the commit from Pedro after 3.8-stable.
brad@ is the -STABLE maintainer so
Also, run a netstat -m and look at peak usage. If that number is
reaching max, increase kern.maxclusters with sysctl.
$ netstat -m
1543 mbufs in use:
1539 mbufs allocated to data
1 mbuf allocated to packet headers
3 mbufs allocated to socket names and addresses
Try to increase kern.maxclusters. It is possible that the box crashed
due to network buffer shortage. pedro@ commited a fix to both
-currentand 3.8-STABLE which increases buffer on-the-fly without
panic.
Also, run a netstat -m and look at peak usage. If that number is
reaching max, increase
On 12/9/05, Uwe Dippel [EMAIL PROTECTED] wrote:
So you probably saw mine as well, Proliant 350.
I have no solution yet, but a few more boxes rolling in that need more
than that single Broadcom on-board piece.
Is this a HP problem or an OpenBSD problem ? I'll try Linux on the next
box; but
On 12/9/05, Pete Vickers [EMAIL PROTECTED] wrote:
for my DL145 (pretty new) I get a reasonable-ish disk I/O of ~60Mb/s
( with CPU at 99% idle)
[EMAIL PROTECTED] /root dd if=/dev/rwd0a of=/dev/null bs=1m count=1000
1000+0 records in
1000+0 records out
1048576000 bytes transferred in 17.645
64 matches
Mail list logo
