Re: FreeBSD-AMD64 on Xeon MP

2008-10-20 Thread Eirik Øverby

Hi,


 Hi all,

 I try to run FreeBSD-7-AMD64 on a Quad Xeon (Xeon MP 7320) and  
32GB RAM.

 The Board is a X7QC3 by supermicro and the installation is done on
 another system, updated and plugged to this system. So I have a  
drive

 with 7-STABLE compiled today.

 The last line I see from dmesg is vga0- then the system freezes.

 Anyone using a similar configuration or knows what could be wrong? I
 still have some days left to play with it, before this box gets  
shipped

 to the customer.

This looks very, very similar to what I had once, on similar hardware
(4x Xeon 7xxx, SuperMicro). I didn't find a solution and didn't bother
since the box isn't intended for FreeBSD. I did find (by accident) a
curious workaround: I booted Linux (I used Ubuntu 8.04 amd64 LiveCD -
just to boot it, without installing), then rebooted and booted  
FreeBSD -

worked every time, but it's obviously not a long-term solution. If you
can also verify that this solves the problem, then someone might  
work

with you to produce a patch.


I just received four such servers, all intended for FreeBSD And  
I'm seeing exactly the same problem. I'm going to try booting Linux  
and then back into FreeBSD, but it's obviously not a solution. Anyone  
who might want to work on this can have a box like this to work on via  
remote KVM (including remote boot media capability) any time.


I'm going to go poke the supplier and Supermicro for some updated  
firmware.

Any progress on your end?

Some additional info: Safe mode boot gets a bit further, to the point  
where it tries to mount/read from /dev/md0, but then hangs hard.


/Eirik

___
freebsd-hardware@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Areca vs. ZFS performance testing.

2008-11-16 Thread Eirik Øverby


On Nov 13, 2008, at 21:59, Danny Carroll wrote:


Scott Long wrote:
The Areca controller likely doesn't buffer/cache for disks in JBOD  
mode,

as others in this thread have stated.  Without buffering, simple disk
controllers will almost always be faster than accelerated raid
controllers because the accelerated controllers add more latency  
between

the host and the disk.  A simple controller will directly funnel data
from the host to the disk as soon as it receives a command.  An
accelerated controller, however, has a CPU and a mini-OS on it that  
has
to schedule the work coming from the host and handle its own tasks  
and

interrupts.  This adds latency that quickly adds up under benchmarks.
Your numbers clearly demonstrate this.


That's nice to know.  I'm not sure it tells us why the Non-Cached  
writes

were about 8% faster though.  The other thing about the NoWriteCache
test I performed that I neglected to mention yesterday is that I
actually panic'd the box (running out of memory).   This was the first
time I have had that happen with ZFS even though in previous testing
(with cache enabled) I punished the box for a lot longer.

Perhaps the ZFS caching took over where the disk caching left off?
Could that explain why I did not see a negative difference in the
numbers between Cache enabled and Cache disabled?

One of the questions I wanted to answer for myself was just this:   
Does

a battery-backed cache on an Areca card protect me when I am in JBOD
mode.  If the Areca does not buffer/cache in JBOD mode then that  
means

the answer is no.


I have noticed that my 3ware controllers, after updating firmware  
recently, have removed the JBOD option entirely, classifying it as  
something you wouldn't want to do with that kind of hardware anyway. I  
believed then, and even more so now, they are correct.


Use the RAID-0 disk trick to be able to utilize the controller cache.  
And regarding write-back vs write-through; I believe write-through is  
equvivalent to disabling controller write cache, however it WILL cache  
the writes in order to respond to future reads of the data being  
written. I would guess, but I don't know, that this also goes for disk- 
level caches too, though, so it probably doesn't matter.


/Eirik

___
freebsd-hardware@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Promise SATA300 TX4302 feedback?

2009-01-03 Thread Eirik Øverby

On Jan 2, 2009, at 19:38, Vlad Skvortsov wrote:


Alex Keda wrote:


I'm looking to buy a Promise SATA300 TX4302 (PCI-[e]SATA) card to  
use for external backups on a FreeBSD 6-STABLE system. Can anyone  
share their experiences with this one?

Use Hardware Controllers - such as 3ware



I'm not quite getting what you mean -- can you clarify please?


What he means is use controllers that do RAID in hardware, not  
software-raid cards like that Promise.


/Eirik

___
freebsd-hardware@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to freebsd-hardware-unsubscr...@freebsd.org


Areca 1200 controller panics 7.1

2009-01-21 Thread Eirik Øverby

Hi folks,

see attached screenshot for panic screen. This happens when booting  
from 7.1-release CD. The box is a Sun X2200 M2, the controller is a 2- 
port SATA-II controller with 128mb cache memory. One drive is set as  
single drive (RAID-0), another as passthrough (to get hold of some  
data from pre-areca times).


Another Areca controller in another box (different controller model (4- 
chan sata) and box (tyan transport)) works just fine.


Input welcome.

/Eirik
___
freebsd-hardware@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to freebsd-hardware-unsubscr...@freebsd.org


Re: Areca 1200 controller panics 7.1

2009-01-21 Thread Eirik Øverby

Attachment not getting throuh. Panic transcribed below.
/Eirik

On Jan 21, 2009, at 20:53, Eirik Øverby wrote:


Hi folks,

see attached screenshot for panic screen. This happens when booting  
from 7.1-release CD. The box is a Sun X2200 M2, the controller is a  
2-port SATA-II controller with 128mb cache memory. One drive is set  
as single drive (RAID-0), another as passthrough (to get hold of  
some data from pre-areca times).


Another Areca controller in another box (different controller model  
(4-chan sata) and box (tyan transport)) works just fine.


Input welcome.

/Eirik



(probe16:arcmsr0:0:16:0): inquiry data fails comparison at DV1 step
arcmsr0: isr get an illegal srb command doneacb=´0x8124e000´  
srb=0x
aeb6c420´ srbacb=´0x8124e000´  
startdone=0x3c3csrboutstandingcount=-1



Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x34be2988
fault code = supervisor read data, page not present
instruction pointer = 0x8:0x807914c3
stack pointer = 0x10:0xaecaab60
frame pointer = 0x10:0x8124e000
code segment = base 0x0, limit 0xf, type 0x1b
  = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 36 (irq17: arcmsr0)
trap number = 12
panic: page fault

___
freebsd-hardware@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to freebsd-hardware-unsubscr...@freebsd.org


Areca ARC-1210 abysmal performance

2009-01-26 Thread Eirik Øverby

Hi,

I've just purchased a pile of Areca 1210 controllers, having seen that  
they should perform well with FreeBSD. Now having hooked up a pair of  
them to 4 WD 250gb SATA drives and configured them to RAID1+0, I see  
them perform very, very badly.


Below is a typical test I run on newly created arrays, to see the  
sustained write speeds they can handle. It's nowhere near a real-world  
test, but I've found it to often reveal issues early on.


As you can see, the Areca seems to accept a lump of data (filling its  
write cache) early on, then practically slows to a crawl, and for long  
stretches of time no data is written at all, before another burst is  
written followed by trickling, repeat ad infinitum.


I've repeated this with HDD cache on and off, controller cache on and  
off, NCQ on and off and at both SATA150 and SATA300 speeds. When  
disabling the controller cache (setting it to write-through), I don't  
get the initial burst, but a slow trickle of data ~5-15 mbytes/sec.


While this is going on, the system is basically unresponsive. There is  
nothing else going on, only sshd running.


I've just updated the firmware to the latest as of today, however that  
didn't change anything.


I'm on FreeBSD 7.1-RELEASE. Dmesg output below.

Can anyone point me in the right direction here?

Thanks,
/Eirik

[r...@md-hh-play-01 /usr]# dd if=/dev/zero of=testfile bs=64k  iostat 1
[1] 889
  tty da0pass0 
pass1 cpu
 tin tout  KB/t tps  MB/s   KB/t tps  MB/s   KB/t tps  MB/s  us ni sy  
in id
   1   98 61.81  76  4.60   0.00   0  0.00   0.00   0  0.00   0  0   
0  0 99
   0  231 64.00 3732 233.22   0.00   0  0.00   0.00   0  0.00   0  0  
13  2 85
   0   79 64.00 264 16.48   0.00   0  0.00   0.00   0  0.00   0  0   
0  0 100
   0   78 64.00 394 24.60   0.00   0  0.00   0.00   0  0.00   0  0   
1  0 98
   0   77 64.00 320 19.98   0.00   0  0.00   0.00   0  0.00   0  0   
1  1 98
   0   77 61.74 234 14.10   0.00   0  0.00   0.00   0  0.00   0  0   
0  0 100
   0   78 64.00 180 11.24   0.00   0  0.00   0.00   0  0.00   0  0   
0  0 99
   0   77 60.90  31  1.84   0.00   0  0.00   0.00   0  0.00   0  0   
0  0 100
   0   78  0.00   0  0.00   0.00   0  0.00   0.00   0  0.00   0  0   
0  0 100
   0   78  0.00   0  0.00   0.00   0  0.00   0.00   0  0.00   0  0   
0  0 100



[r...@md-hh-play-01 /usr]# vmstat -i
interrupt  total   rate
irq3: sio0304870198
irq4: sio1 2  0
irq10: ohci0+ 258071167
irq14: ata0   58  0
cpu0: timer  3075904   1999
irq256: nfe02652  1
cpu1: timer  3067930   1994
cpu2: timer  3067899   1994
cpu3: timer  3067930   1994
Total   12845316   8351



DMESG:
Copyright (c) 1992-2009 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.1-RELEASE #0: Thu Jan  1 08:58:24 UTC 2009
r...@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Dual-Core AMD Opteron(tm) Processor 2218 (2600.02-MHz K8-class CPU)
  Origin = AuthenticAMD  Id = 0x40f13  Stepping = 3
   
Features 
= 
0x178bfbff 
 
FPU 
,VME 
,DE 
,PSE 
,TSC 
,MSR 
,PAE 
,MCE 
,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT

  Features2=0x2001SSE3,CX16
  AMD Features=0xea500800SYSCALL,NX,MMX+,FFXSR,RDTSCP,LM,3DNow!+, 
3DNow!

  AMD Features2=0x1fLAHF,CMP,SVM,ExtAPIC,CR8
  Cores per package: 2
usable memory = 4280922112 (4082 MB)
avail memory  = 4115517440 (3924 MB)
ACPI APIC Table: PTLTD   APIC  
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
 cpu2 (AP): APIC ID:  2
 cpu3 (AP): APIC ID:  3
ioapic0 Version 1.1 irqs 0-23 on motherboard
kbd1 at kbdmux0
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413,  
RF5413)

acpi0: PTLTD XSDT on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
Timecounter ACPI-fast frequency 3579545 Hz quality 1000
acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0
acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff  
on acpi0

Timecounter HPET frequency 2500 Hz quality 900
acpi_button0: Power Button on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
pci0: memory, RAM at device 0.0 (no driver attached)
isab0: PCI-ISA bridge port 0x1c00-0x1c7f at device 1.0 on pci0
isa0: ISA bus on isab0
pci0: serial bus, SMBus at device 1.1 (no driver attached)
ohci0: OHCI (generic) USB controller mem 0xc804-0xc8040fff irq  
10 at device 2.0 on pci0