Well you don't have dma on wd2.

Include the output of pcidump -v and I'll try cook up a diff.

cheers, pcidump below
0:0:0: NVIDIA unknown

        0x0000: Vendor ID: 10de Product ID: 07c1

        0x0004: Command: 0006 Status ID: 00a0

        0x0008: Class: 06 Subclass: 00 Interface: 00 Revision: a2

        0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line Size:

00

        0x0010: BAR empty (00000000)

        0x0014: BAR empty (00000000)

        0x0018: BAR empty (00000000)

        0x001c: BAR empty (00000000)

        0x0020: BAR empty (00000000)

        0x0024: BAR empty (00000000)

        0x0028: Cardbus CIS: 00000000

        0x002c: Subsystem Vendor ID: 0000 Product ID: 0000

        0x0030: Expansion ROM Base Address: 00000000

        0x0038: 00000000

        0x003c: Interrupt Pin: 00 Line: 00 Min Gnt: 00 Max Lat: 00

0:0:1: NVIDIA MCP73 Memory

        0x0000: Vendor ID: 10de Product ID: 07cb

        0x0004: Command: 0004 Status ID: 00a0

        0x0008: Class: 05 Subclass: 00 Interface: 00 Revision: a2

        0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line Size:

00

        0x0010: BAR empty (00000000)

        0x0014: BAR empty (00000000)

        0x0018: BAR empty (00000000)

        0x001c: BAR empty (00000000)

        0x0020: BAR empty (00000000)

        0x0024: BAR empty (00000000)

        0x0028: Cardbus CIS: 00000000

        0x002c: Subsystem Vendor ID: 0000 Product ID: 0000

        0x0030: Expansion ROM Base Address: 00000000

        0x0038: 00000000

        0x003c: Interrupt Pin: 00 Line: 00 Min Gnt: 00 Max Lat: 00

0:1:0: NVIDIA MCP73 Memory

        0x0000: Vendor ID: 10de Product ID: 07cd

        0x0004: Command: 0000 Status ID: 0020

        0x0008: Class: 05 Subclass: 00 Interface: 00 Revision: a1

        0x000c: BIST: 00 Header Type: 80 Latency Timer: 00 Cache Line Size:

00

        0x0010: BAR empty (00000000)

        0x0014: BAR empty (00000000)

        0x0018: BAR empty (00000000)

        0x001c: BAR empty (00000000)

        0x0020: BAR empty (00000000)

        0x0024: BAR empty (00000000)

        0x0028: Cardbus CIS: 00...
[ message continues ]

sata disks normally (if not always) show up as sd's. You have 3 wd's.

That makes me confused and lead to believe you might be running a very

old OpenBSD version, something I cannot conclude from the partial dmesg

you included. Since you obviously have some issues you do not know how

to handle,
  ALWAYS INCLUDE THE ENTIRE DMESG
and do not make any assumptions of what would be necessary or not.
Cheers,

Hi Alexander,
I was more than happy to dump the whole dmesg, but I just didn't want to put

too much into my first message.
Please find the full dmesg below:
OpenBSD 4.4 (GENERIC) #1021: Tue Aug 12 17:16:55 MDT 2008

    deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC

cpu0: Intel(R) Core(TM)2 Duo CPU E7200 @ 2.53GHz ("GenuineIntel" 686-class)

2.54 GHz

cpu0:

FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,EST,TM2,CX16,xTPR

cpu0: unknown i686 EBL_CR_POWERON value 3 (0x424c0000)

real mem  = 2010673152 (1917MB)

avail mem = 1935548416 (1845MB)

mainbus0 at root

bios0 at mainbus0: AT/286+ BIOS, date 09/02/08, BIOS32 rev. 0 @ 0xf1df0,

SMBIOS rev. 2.5 @ 0xf0000 (50 entries)

bios0: vendor Phoenix Technologies, LTD version "ASUS P5N-EM HDMI ACPI BIOS

Revision 0401" date 09/02/2008

bios0: ASUSTeK Computer INC. P5N-EM HDMI

apm0 at bios0: Power Management spec V1.2 (slowidle)

apm0: AC on, battery charge unknown

acpi at bios0 function 0x0 not configured

pcibios0 at bios0: rev 3.0 @ 0xf0000/0xde74

pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfddb0/192 (10 entries)

pcibios0: PCI Exclusive IRQs: 5 10 11

pcibios0: no compatible PCI ICU found

pcibios0: Warning, unable to fix up PCI interrupt routing

pcibios0: PCI bus #4 is the last bus

bios0: ROM list: 0xc0000/0xde00 0xd0000/0x4000! 0xd4000/0x1000

cpu0 at mainbus0

cpu0: EST: unknown system bus clock

pci0 at mainbus0 bus 0: configuration mode 1 (no bios)

pchb0 at pci0 dev 0 function 0 vendor "NVIDIA", unknown product 0x07c1 rev

0xa2

"NVIDIA MCP73 Memory" rev 0xa2 at pci0 dev 0 function 1 not configured

"NVIDIA MCP73 Memory" rev 0xa1 at pci0 dev 1 function 0 not configured

"NVIDIA MCP73 Memory" rev 0xa1 at pci0 dev 1 function 1 not configured

"NVIDIA MCP73 Memory" rev 0xa1 at pci0 dev 1 function 2 not configured

"NVIDIA MCP73 Memory" rev 0xa1 at pci0 dev 1 function 3 not configured

"NVIDIA MCP73 Memory" rev 0xa1 at pci0 dev 1 function 4 not...
[ message continues ]

My 2cents worth:
On Apr 20, 2009 12:58am, Kristian Rooke <kristianr@gmail.com> wrote:
I have no idea how you configured your network. Which interface is pointing

to LAN where you're copying from?
I had a 4.4 samba issue as well until I completely dropped the realtek

network cards and bought an intel GigE card. Do yourself a favor and do the

same, even if you have to disable the onboard LAN (realtek PHY - same

problem as mine) to do it.
My ports/misc thread:

http://marc.info/?l=openbsd-ports&m=122703016321404&w=2

http://marc.info/?l=openbsd-misc&m=122719611210846&w=2
best I can think of is something changed between 4.3 or 4.2 (I can't

remember which version I was running before 4.4) in the realtek driver that

made the card interupt crazy. I ran out bought the intel/em card and

haven't had a problem since.
agian though this is the ramblings of some lurker trying to offer his 2

cents worth of experience, thus "your milage may vary". Cheers & good luck.

[Quote]

pciide1 at pci0 dev 14 function 0 "NVIDIA MCP73 AHCI" rev 0xa2: DMA

(unsupported), channel 0 wired to native-PCI, channel 1 wired to native-PCI

[end quote]
The AHCI implementation on your mb is not supported by the version of

OpenBSD

you are using.
That, or it is configured to something other than true AHCI by the bios. I'd

suggest checking to see if you have mode options for it in your bios and see

if that moves it from being a wd? drive (driven by pciide) to a sd? drive

(driven by the AHCI driver)

Thanks for the suggestions.
I checked the BIOS configuration and it appears that the SATA controller was

set to IDE (not sure how that happened). I have now set it to AHCI, but I am

seeing another error in dmesg....
ahci0 at pci0 dev 14 function 0 "NVIDIA MCP73 AHCI" rev 0xa2: irq 11, AHCI

1.1

ahci0: failed to start command DMA on port 0, disabling

ahci0: failed to start command DMA on port 2, disabling

scsibus0 at ahci0: 32 targets, initiator 32
Does this mean that AHCI on my m/b is not supported in OpenBSD?

Any other thoughts?

I'm not an expert by any means when it comes to OpenBSD,

AHCI, or SATA, but here are some shots in the dark.
Does your machine have four SATA ports on it?  Can you

identify which of the four ports your two SATA drives are

plugged into?  Can you add additional SATA drives and see

if these errors are resolved or multiplied?
First guess is that the AHCI method for deciding which ports

have SATA devices attached is not working properly on your

motherboard/chipset.  Second guess is that the chipset or

motherboard has some problems with DMA happening the way

that the ahci device expects it to work.
Are there any sd devices listed after the scsibus0 line?
something like this?
scsibus1 at umass0: 2 targets, initiator 0

sd0 at scsibus1 targ 1 lun 0: <Y-E DATA, USB HS-CF Card,

4.08> SCSI0 0/direct removable

sd0: drive offline

sd1 at scsibus1 targ 1 lun 1: <Y-E DATA, USB HS-xD/SM,

4.08> SCSI0 0/direct removable

sd1: drive offline

sd2 at scsibus1 targ 1 lun 2: <Y-E DATA, USB HS-MS Card,

4.08> SCSI0 0/direct removable

sd2: drive offline

sd3 at scsibus1 targ 1 lun 3: <Y-E DATA, USB HS-SD Card,

4.08> SCSI0 0/direct removable

sd3: drive offline

The 2 SATA drives are currently connected to SATA port 1 & 2 (so the BIOS

tells me).

I just connected another SATA drive to port number 4 and the same occured

for that drive too.
There are no further details following the scsibus0 line.
ahci0 at pci0 dev 14 function 0 "NVIDIA MCP73 AHCI" rev 0xa2: irq 11, AHCI

1.1

ahci0: failed to start command DMA on port 0, disabling

ahci0: failed to start command DMA on port 2, disabling

ahci0: failed to start command DMA on port 3, disabling <-----

scsibus0 at ahci0: 32 targets, initiator 32
I found some information about a bug with my Nvidia chipset and FreeBSD,

which refers to SATA drives -

http://www.nabble.com/i386-129542:-FreeBSD-7.1-RC1-installer-cannot-find-WD-SATA-hard-drive-with-MCP73M01H1-mainboard-(MCP73-SATA-controller)-td20928904.html

Do you think there could be a relationship there (even though it's a

different plaform?

MCP77 is also unsupported.  but there was a patch floating about

on tech@ regarding ahci.  my notebook is quite unusable at the

moment so i can't test patches.  it has 44k interrupts a second

and everything takes forever.
some of the devs really need to give up their thinkpads and start

buying cheap msi or other stuff with amd and nvidia monstrosities :]
-f

--

raising your voice does not reinforce your argument.

Right, dealing with hardware that is unreliable on a daily basis is

exactly what I need.  I mean I am totally not busy at all so what is a

random reboot here and there anyway.

all hw is unrealible to some degree, that's why we make backups.

i am sure there are lenovo models that pack some shitty components..

my thinkpad had it's own peculiarities (apm not working was one of them).
and once again, for the record.  that was a joke.  there is a smiley.

geez.  i know it's monday but loosen up a bit....
-f

--

windows error: 004 erroneous error.  nothing wrong.

... and all degrees of unreliability are equivalent?

Methinks some people like stuff that is LESS unreliable.

Even going so far as to make an OS that is LESS unreliable.

not that i disagree, but sometimes, it is enough to be unreliable once.
and reliable hw tends to make one sloppy and not think of

worst case scenarios :]
-f

--

want to forget all your troubles?  wear tight shoes.

Thank you!

The voice of experience?

You need to go write some acpi code and tell me again to loosen up.

Once you have taken a few bites of that shittaco tell me again how funny

So from what I can tell... my chipset is crap and nobody wants to develop/fix

AHCI support for it, so I either buy a new motherboard, or give up and use

IDE rather than AHCI? :)
--

View this message in context: http://www.nabble.com/Slow-SATA-write-speeds-with-SMB-tp23130953p2314639...

Sent from the openbsd user - misc mailing list archive at Nabble.com.

Or write the support yourself...
-----Original Message-----

From: owner-misc@openbsd.org [mailto:owner-misc@openbsd.org] On Behalf Of

Syntic

Sent: Monday, April 20, 2009 4:50 PM

To: misc@openbsd.org

Subject: Re: Slow SATA write speeds with SMB
So from what I can tell... my chipset is crap and nobody wants to develop/fix

AHCI support for it, so I either buy a new motherboard, or give up and use

IDE rather than AHCI? :)
--

View this message in context:

http://www.nabble.com/Slow-SATA-write-speeds-with-SMB-tp23130953p2314639...

l

Sent from the openbsd user - misc mailing list archive at Nabble.com.

If i had the skills required, I would try.. but at this stage I have enough

trouble configuring OpenBSD to perform basic tasks. So I think it may be a

little out of my reach.

Yeah... you're like... the guy who is sits outside the estwing

factory hitting his balls with an estwing hammer - telling everyone

who comes in and out that it fucking hurts like hell and they shold

give up on those nails and things and start hitting their balls so

they can fix the hammer so it hurts less...
We'll get right on that.. 
Hope your balls get better soon.

Bob, always the funny guy.
if you can't let a joke go, you are the one hitting your balls.
-f

--

bad is never good until worse happens.

estwing? i think not. more like some low grade foundry in China..
--

Christopher Linn <celinn at mtu.edu>  | By no means shall either the CEC

System Administrator II               | or MTU be held in any way liable

  Center for Experimental Computation | for any opinions or conjecture I

    Michigan Technological University | hold to or imply to hold herein.

Just noticed this, thought I'd quickly give you the following tip :
On Mon, Apr 20, 2009 at 03:40:35AM -0600, Anathae Townsend wrote:

| [Quote]

| pciide1 at pci0 dev 14 function 0 "NVIDIA MCP73 AHCI" rev 0xa2: DMA

| (unsupported), channel 0 wired to native-PCI, channel 1 wired to native-PCI

| [end quote]
Try forcing the pciide driver to use DMA by setting flags to 0x0001.

See pciide(4) for details (and the caveats listed there). Procede with

care to avoid dataloss (make backups etc), but this has helped me a

couple of times already.
To set this, boot -c and in UKC use 'change pciide' to alter the flags

value (keep all other things as they are). If this works for your

machine, you can use config(8) from your booted machine to configure

this permanently (remember to re-do this step after each upgrade).
Paul 'WEiRD' de Weerd
+++++++++++>-]<.>++[<------------>-]<+.--------------.[-]

                 http://www.weirdnet.nl/

I have yet to see anyone complaining about too much information. ;-)
Nevertheless, AFAICS (which is rather limited), it seems your wd2 disk

(which I assume is the problematic one) is attached as an IDE device but

is missing the corresponding wd0/wd1 line:
   wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 5
My guess would be that the mainboard is using some (possibly crappy)

IDE/SATA converter that, at least from OpenBSD's point of view, does not

support anything but the basics, causing the bad result.
Regarding FTP/SMB differences, I guess that could come from differences

in the protocols and how they do their disk access etc.
As noted, my knowledge is not great at these kind of things, so ACK's,

NAK's and/or corrections would still be appreciated. :-)