Re: 6.1-RELEASE: TIMEOUT - WRITE_DMA retrying

2006-08-16 Thread Vlad

I just got the message it panics with:

ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=380273047
ad4: FAILURE - WRITE_DMA48 status=51
error=10 LBA=380273047
g_vfs_done():ad4s1a[WRITE(offset=194699767808, length=2048)]error = 5
panic: newdirrem: not ATTACHED

Also, you maybe very right about conflict with other hardware - it
seemed to me that it's much less stable when intense HD operation is
combined with network activity (i.e. downloading file via samba). I've
tried to copy 3gig of archives over the net and I could not copy it
after 3 attempts. Same time I've un-tarred those files locally on that
server successfully after my 1st attempt.

Any recommendations on what ~ 30 buck SATA card works OK with 6.1? I
may opt out to take this one back and replace, unless someone willing
to nail this down - I'm open for tests...


On 8/16/06, James Seward <[EMAIL PROTECTED]> wrote:

On 8/16/06, Vlad <[EMAIL PROTECTED]> wrote:
> I get this type of messages in on my FreeBSD.
> ad4: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=70938623
> Under steady IO load it panics, that started when we changed SATA
> controller (FreeBSD detects it as SiI 3512). I've tried to switch
> ports, cable, move card into a different PCI slot, disable ata dma in
> /boot/loader.conf - nothing helps.

I had similar problems under 5.x and 6.x with a SI3112. My testing and
investigations back then suggested that some combinations of hardware
and the SI3112 just "don't get along" and I solved it by getting rid
of it.

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


Re: 6.1-RELEASE: TIMEOUT - WRITE_DMA retrying

2006-08-16 Thread James Seward

On 8/16/06, Vlad <[EMAIL PROTECTED]> wrote:

I get this type of messages in on my FreeBSD.
ad4: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=70938623
Under steady IO load it panics, that started when we changed SATA
controller (FreeBSD detects it as SiI 3512). I've tried to switch
ports, cable, move card into a different PCI slot, disable ata dma in
/boot/loader.conf - nothing helps.


I had similar problems under 5.x and 6.x with a SI3112. My testing and
investigations back then suggested that some combinations of hardware
and the SI3112 just "don't get along" and I solved it by getting rid
of it.

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


6.1-RELEASE: TIMEOUT - WRITE_DMA retrying

2006-08-16 Thread Vlad

Hi,

I get this type of messages in on my FreeBSD.

ad4: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=70938623

Under steady IO load it panics, that started when we changed SATA
controller (FreeBSD detects it as SiI 3512). I've tried to switch
ports, cable, move card into a different PCI slot, disable ata dma in
/boot/loader.conf - nothing helps.



Copyright (c) 1992-2006 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 6.1-RELEASE #6: Tue May  9 11:02:38 CDT 2006
   [EMAIL PROTECTED]:/usr/obj/usr/src/sys/HQ
ACPI APIC Table: 
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) XP 2500+ (1836.13-MHz 686-class CPU)
 Origin = "AuthenticAMD"  Id = 0x6a0  Stepping = 0
 
Features=0x383fbff
 AMD Features=0xc0400800
real memory  = 536805376 (511 MB)
avail memory = 51598 (492 MB)
ioapic0  irqs 0-23 on motherboard
acpi0:  on motherboard
acpi0: Power Button (fixed)
cpu0:  on acpi0
acpi_throttle0:  on cpu0
acpi_button0:  on acpi0
pcib0:  port
0xcf8-0xcff,0x4000-0x407f,0x4080-0x40ff,0x5000-0x500f on acpi0
pci0:  on pcib0
agp0:  mem
0xe000-0xe7ff at device 0.0 on pci0
pcib1:  at device 1.0 on pci0
pci1:  on pcib1
atapci0:  port
0xc000-0xc007,0xc400-0xc403,0xc800-0xc807,0xcc00-0xcc03,0xd000-0xd00f
mem 0xe921-0xe92101ff
irq 18 at device 10.0 on pci0
ata2:  on atapci0
ata3:  on atapci0
pci0:  at device 12.0 (no driver attached)
sis0:  port 0xd400-0xd4ff mem
0xe9211000-0xe9211fff irq 17 at device 13.0 on pci0
sis0: Silicon Revision: DP83815D
miibus0:  on sis0
ukphy0:  on miibus0
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
sis0: Ethernet address: 00:02:e3:14:27:0b
isab0:  at device 17.0 on pci0
isa0:  on isab0
atapci1:  port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe400-0xe40f at device 17.1 on
pci0
ata0:  on atapci1
ata1:  on atapci1
pci0:  at device 17.5 (no driver attached)
rl0:  port 0xec00-0xecff mem
0xe9213000-0xe92130ff irq 18 at device 19.0 on pci0
miibus1:  on rl0
rlphy0:  on miibus1
rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
rl0: Ethernet address: 00:20:ed:b6:e0:6e
fdc0:  port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: [FAST]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0:  port 0x60,0x64 irq 1 on acpi0
atkbd0:  irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
pmtimer0 on isa0
orm0:  at iomem 0xc-0xc7fff,0xc8000-0xcc7ff on isa0
ppc0: parallel port not found.
sc0:  at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 8250 or not responding
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
Timecounter "TSC" frequency 1836128583 Hz quality 800
Timecounters tick every 1.000 msec
ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding
disabled, default to accept, logging unlimited
acd0: CDROM  at ata0-master UDMA33
ad4: 190782MB  at ata2-master SATA150
Trying to mount root from ufs:/dev/ad4s1a
WARNING: / was not properly dismounted
/: mount pending error: blocks 216 files 1
sis0: Applying short cable fix (reg=f8)
rl0: link state changed to UP


--

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