Re: SiI 3114 woes
On 9/8/05, Søren Schmidt [EMAIL PROTECTED] wrote:
On 08/09/2005, at 13:37, Mars G. Miro wrote:
Yo list/Soren!
Has anybody successfully installed FreeBSD on the dual-Opteron TYAN
ThunderK8W S2885 ( http://www.tyan.com/products/html/thunderk8w.html )
using the onboard SiI 3114 SATA controller? This mobo is supposedly
supported:
http://www.freebsd.org/cgi/query-pr.cgi?pr=80857
But I have never been able to successfully install
FreeBSD({5.3/5.4/6.0Beta3/4} amd64/i386) on it, using SATA.
In my last attempt at installing 6.0Beta4 AMD64 on it, I get:
ad4: FAILURE - WRITE_DMA status=51READY,DSC,ERROR error=4ABORTED
LBA=105819039
g_vfs_done():ad4s1e[WRITE(offset=23695114240, length=2048)]error = 5
The drive apparently aborts the write, however this cant be the first
operation to it, so something else might have happend before this.
On my (granted UP AMD64) it works like a charm, so does it on x86 so
the driver is not completely broken at least :)
Get me the output from dmesg so I can see whats under the hood, might
help explain things.
It's attached.
I should also mention that the BIOS is teh latest version (2.05) w/
the SiI 3114 flash version to be 5.049.
Thanks!
Søren Schmidt
[EMAIL PROTECTED]
cheers
mars
Copyright (c) 1992-2005 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.0-BETA4 #0: Tue Sep 6 20:00:59 UTC 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
WARNING: WITNESS option enabled, expect reduced performance.
Preloaded elf kernel /boot/kernel/kernel at 0x80de4000.
Preloaded mfs_root /boot/mfsroot at 0x80de41a8.
Calibrating clock(s) ... i8254 clock: 1193155 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter i8254 frequency 1193182 Hz quality 0
Calibrating TSC clock ... TSC clock: 1793188253 Hz
CPU: AMD Opteron(tm) Processor 244 (1793.19-MHz K8-class CPU)
Origin = AuthenticAMD Id = 0xf5a Stepping = 10
Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2
AMD Features=0xe0500800SYSCALL,NX,MMX+,LM,3DNow+,3DNow
L1 2MB data TLB: 8 entries, fully associative
L1 2MB instruction TLB: 8 entries, fully associative
L1 4KB data TLB: 32 entries, fully associative
L1 4KB instruction TLB: 32 entries, fully associative
L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative
L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative
L2 2MB unified TLB: 0 entries, disabled/not present
L2 4KB data TLB: 512 entries, 4-way associative
L2 4KB instruction TLB: 512 entries, 4-way associative
L2 unified cache: 1024 kbytes, 64 bytes/line, 1 lines/tag, 16-way associative
real memory = 2147418112 (2047 MB)
Physical memory chunk(s):
0x1000 - 0x0009bfff, 634880 bytes (155 pages)
0x00ee1000 - 0x7c3a, 2068639744 bytes (505039 pages)
avail memory = 2058506240 (1963 MB)
wlan: 802.11 Link Layer
null: null device, zero device
random: entropy source, Software, Yarrow
nfslock: pseudo-device
mem: memory
io: I/O
acpi0: A M I OEMXSDT on motherboard
acpi0: [MPSAFE]
pci_open(1):mode 1 addr port (0x0cf8) is 0x8000cb80
pci_open(1a): mode1res=0x8000 (0x8000)
pci_cfgcheck: device 0 1 2 3 4 5 6 [class=060400] [hdr=01] is there
(id=74601022)
AcpiOsDerivePciId: bus 0 dev 7 func 0
AcpiOsDerivePciId: bus 0 dev 7 func 1
AcpiOsDerivePciId: bus 0 dev 7 func 3
acpi0: Power Button (fixed)
pci_link0: ACPI PCI Link LNKA irq 9 on acpi0
pci_link0: Links after initial probe:
Index IRQ Rtd Ref IRQs
09 N 0 3 4 5 6 7 9 10 11 12 14 15
pci_link0: Links after initial validation:
Index IRQ Rtd Ref IRQs
09 N 0 3 4 5 6 7 9 10 11 12 14 15
pci_link0: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 6 7 9 10 11 12 14 15
pci_link1: ACPI PCI Link LNKB irq 11 on acpi0
pci_link1: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 11 N 0 3 4 5 6 7 9 10 11 12 14 15
pci_link1: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 11 N 0 3 4 5 6 7 9 10 11 12 14 15
pci_link1: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 6 7 9 10 11 12 14 15
pci_link2: ACPI PCI Link LNKC irq 0 on acpi0
pci_link2: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 6 7 9 10 11 12 14 15
pci_link2: Links after initial validation:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 6 7 9 10 11 12 14 15
pci_link2: Links after disable:
Index IRQ Rtd Ref IRQs
0 255 N 0 3 4 5 6 7 9 10 11 12 14 15
pci_link3: ACPI PCI Link LNKD irq 10 on acpi0
pci_link3: Links after initial probe:
Index IRQ Rtd Ref IRQs
0 10 N 0 3 4 5 6 7 9 10 11 12 14 15
pci_link3: Links after initial validation:
Index IRQ Rtd
Re: SiI 3114 woes
On 9/9/05, Jon Dama [EMAIL PROTECTED] wrote:
Yes, but only in a configuration =3GB. But I thought those problems were
ironed out? I've been looking to switch that machine back to
FreeBSD/amd64 but haven't had a chance yet. Would love to know if there
are issues ahead.
This machine only has 2G of RAM. See my previous post on the full dmesg.
Thanks.
-Jon
On Thu, 8 Sep 2005, Mars G. Miro wrote:
Yo list/Soren!
Has anybody successfully installed FreeBSD on the dual-Opteron TYAN
ThunderK8W S2885 ( http://www.tyan.com/products/html/thunderk8w.html )
using the onboard SiI 3114 SATA controller? This mobo is supposedly
supported:
http://www.freebsd.org/cgi/query-pr.cgi?pr=80857
But I have never been able to successfully install
FreeBSD({5.3/5.4/6.0Beta3/4} amd64/i386) on it, using SATA.
In my last attempt at installing 6.0Beta4 AMD64 on it, I get:
ad4: FAILURE - WRITE_DMA status=51READY,DSC,ERROR error=4ABORTED
LBA=105819039
g_vfs_done():ad4s1e[WRITE(offset=23695114240, length=2048)]error = 5
at the debugging console
and
panic:bundirty: buffer 0x9a7faff0 still on queue 1
cpuid = 0
KDB: enter: panic
[ thread pid 3 tid 100021 ]
Stopped at kdb_enter+0x2f: nop
db trace
Tracing pid 3 tid 100021 td 0xff007ba14be0
kdb_enter() at kdb_enter+0x2f
panic() at panic+0x249
bundirty() at bundirty+0x128
brelse() at brelse+0x831
bufdone() at bufdone+0x225
ffs_backgroundwritedone() at ffs_backgroundwritedone+0xa7
bufdone() at bufdone+0x2ad
g_vfs_done() at g_gvfs_done+0x63
g_io_schedule_up() at g_io_schedule_up+0xd4
g_up_procbody() at g_up_procbody+0x7a
fork_exit() at fork_exit+0xbb
fork_trampoline() at fork_tramploine+0xe
--- trap 0, rip = 0, rsp = 0xb2160d00, rbp = 0 ---
db
Some months ago, I did successfully install FreeBSD 5.4/amd64 on it,
using PATA IDE drives, and no problems whatsoever, so I think this has
something to do w/ the SiI 3114 driver.
Any help is much appreciated.
I do apologize for cross-posting but this concerns -stable and -amd64.
Thanks!
cheers
mars
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
cheers
mars
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SiI 3114 woes
On 08/09/2005, at 13:37, Mars G. Miro wrote:
Yo list/Soren!
Has anybody successfully installed FreeBSD on the dual-Opteron TYAN
ThunderK8W S2885 ( http://www.tyan.com/products/html/thunderk8w.html )
using the onboard SiI 3114 SATA controller? This mobo is supposedly
supported:
http://www.freebsd.org/cgi/query-pr.cgi?pr=80857
But I have never been able to successfully install
FreeBSD({5.3/5.4/6.0Beta3/4} amd64/i386) on it, using SATA.
In my last attempt at installing 6.0Beta4 AMD64 on it, I get:
ad4: FAILURE - WRITE_DMA status=51READY,DSC,ERROR error=4ABORTED
LBA=105819039
g_vfs_done():ad4s1e[WRITE(offset=23695114240, length=2048)]error = 5
The drive apparently aborts the write, however this cant be the first
operation to it, so something else might have happend before this.
On my (granted UP AMD64) it works like a charm, so does it on x86 so
the driver is not completely broken at least :)
Get me the output from dmesg so I can see whats under the hood, might
help explain things.
Søren Schmidt
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SiI 3114 woes
Yes, but only in a configuration =3GB. But I thought those problems were
ironed out? I've been looking to switch that machine back to
FreeBSD/amd64 but haven't had a chance yet. Would love to know if there
are issues ahead.
-Jon
On Thu, 8 Sep 2005, Mars G. Miro wrote:
Yo list/Soren!
Has anybody successfully installed FreeBSD on the dual-Opteron TYAN
ThunderK8W S2885 ( http://www.tyan.com/products/html/thunderk8w.html )
using the onboard SiI 3114 SATA controller? This mobo is supposedly
supported:
http://www.freebsd.org/cgi/query-pr.cgi?pr=80857
But I have never been able to successfully install
FreeBSD({5.3/5.4/6.0Beta3/4} amd64/i386) on it, using SATA.
In my last attempt at installing 6.0Beta4 AMD64 on it, I get:
ad4: FAILURE - WRITE_DMA status=51READY,DSC,ERROR error=4ABORTED
LBA=105819039
g_vfs_done():ad4s1e[WRITE(offset=23695114240, length=2048)]error = 5
at the debugging console
and
panic:bundirty: buffer 0x9a7faff0 still on queue 1
cpuid = 0
KDB: enter: panic
[ thread pid 3 tid 100021 ]
Stopped at kdb_enter+0x2f: nop
db trace
Tracing pid 3 tid 100021 td 0xff007ba14be0
kdb_enter() at kdb_enter+0x2f
panic() at panic+0x249
bundirty() at bundirty+0x128
brelse() at brelse+0x831
bufdone() at bufdone+0x225
ffs_backgroundwritedone() at ffs_backgroundwritedone+0xa7
bufdone() at bufdone+0x2ad
g_vfs_done() at g_gvfs_done+0x63
g_io_schedule_up() at g_io_schedule_up+0xd4
g_up_procbody() at g_up_procbody+0x7a
fork_exit() at fork_exit+0xbb
fork_trampoline() at fork_tramploine+0xe
--- trap 0, rip = 0, rsp = 0xb2160d00, rbp = 0 ---
db
Some months ago, I did successfully install FreeBSD 5.4/amd64 on it,
using PATA IDE drives, and no problems whatsoever, so I think this has
something to do w/ the SiI 3114 driver.
Any help is much appreciated.
I do apologize for cross-posting but this concerns -stable and -amd64.
Thanks!
cheers
mars
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SiI 3114 woes
Jon Dama wrote:
Yes, but only in a configuration =3GB. But I thought those problems were
ironed out? I've been looking to switch that machine back to
FreeBSD/amd64 but haven't had a chance yet. Would love to know if there
are issues ahead.
-Jon
On Thu, 8 Sep 2005, Mars G. Miro wrote:
Yo list/Soren!
Has anybody successfully installed FreeBSD on the dual-Opteron TYAN
ThunderK8W S2885 ( http://www.tyan.com/products/html/thunderk8w.html )
using the onboard SiI 3114 SATA controller? This mobo is supposedly
supported:
http://www.freebsd.org/cgi/query-pr.cgi?pr=80857
But I have never been able to successfully install
FreeBSD({5.3/5.4/6.0Beta3/4} amd64/i386) on it, using SATA.
In my last attempt at installing 6.0Beta4 AMD64 on it, I get:
ad4: FAILURE - WRITE_DMA status=51READY,DSC,ERROR error=4ABORTED
LBA=105819039
g_vfs_done():ad4s1e[WRITE(offset=23695114240, length=2048)]error = 5
at the debugging console
and
panic:bundirty: buffer 0x9a7faff0 still on queue 1
cpuid = 0
KDB: enter: panic
[ thread pid 3 tid 100021 ]
Stopped at kdb_enter+0x2f: nop
db trace
Tracing pid 3 tid 100021 td 0xff007ba14be0
kdb_enter() at kdb_enter+0x2f
panic() at panic+0x249
bundirty() at bundirty+0x128
brelse() at brelse+0x831
bufdone() at bufdone+0x225
ffs_backgroundwritedone() at ffs_backgroundwritedone+0xa7
bufdone() at bufdone+0x2ad
g_vfs_done() at g_gvfs_done+0x63
g_io_schedule_up() at g_io_schedule_up+0xd4
g_up_procbody() at g_up_procbody+0x7a
fork_exit() at fork_exit+0xbb
fork_trampoline() at fork_tramploine+0xe
--- trap 0, rip = 0, rsp = 0xb2160d00, rbp = 0 ---
db
Some months ago, I did successfully install FreeBSD 5.4/amd64 on it,
using PATA IDE drives, and no problems whatsoever, so I think this has
something to do w/ the SiI 3114 driver.
Any help is much appreciated.
I do apologize for cross-posting but this concerns -stable and -amd64.
It looks like the same issue that we have been complaining
about irt the ATA driver in 5.4/stable.. Several people have also found
it to be a problem under 6.0. In my case, it happens with a plain old
PATA drive (via 8235 controller). It runs fine under PIO4 mode, any
DMA modes result in the same errors you got.
I was working on updating and installing the ataMkIII patches since
that's the only version that is being supported :^ But they are
supposed to merge the beta code that is in 6.0 into 5.stable and
it sound like the same errors are occurring.
I'm seriously considering installing Gentoo and wash my hands of it.
John FreeBSD since '94, ver 2.0.x
--
John T. FarmerOwner CTOGoldSword Systems
[EMAIL PROTECTED] 865-691-6498 Knoxville TN
Consulting, Design, Development of Networks Software
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
