Date: 03 Nov 2007 04:08:28 +0100 From: "Arno J. Klaassen" <arno@heho.snv.jussieu.fr> To: =?iso-8859-1?q?S=F8ren_Schmidt?= <sos@deepcore.dk> Cc: Thierry Herbelot <thierry@herbelot.com>, freebsd-hackers@freebsd.org, Alexander Sabourenkov <screwdriver@lxnt.info>, "Matthew D. Fuller" <fullermd@over-yonder.net>, sos@freebsd.org Subject: Re: Patch RFC: Promise SATA300 TX4 hardware bug workaround. Message-ID: <wptzo4yqj7.fsf@heho.snv.jussieu.fr> In-Reply-To: <472B9EA1.6060205@deepcore.dk> References: <472A548B.50406@lxnt.info> <wpsl3oe7h9.fsf@heho.snv.jussieu.fr> <472B9EA1.6060205@deepcore.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello,
> [ ... ]
> > I will test again with "#define PDC_MAXLASTSGSIZE 32*4" (just to see
> > if that makes a difference)
> >
> One thing to try is to loose any geom raid, if raid needed use ataraid
> instead.
Nope : i did a "newfs ad6" (the disk at the Promise TX4) and then an
rsync on it panics the same way as the geom_concat case did.
> I'm shuffeling boards and controllers here to try to reproduce, so far
> no luck it "just works(tm)", it seems to depend quite heavily on the
> "right" combination of possibly marginal HW....
Rather than the marginal HW part, it seems, for me, closely related to
MB/BIOS (as well (Alexander apperently has about the same setup as I
have for this test)):
a while ago (using releng_6) i tried the same setup on three different
MBs: ahd-controller + scsi-boot-disk and TX4 and three disks in
geom_mirror; results :
- on ASUS A8? board (I use plenty of them without the sligthest
problem for years; not really expensive but not marginal IMHO) :
just look at it and it would crash (g_vfs_done)
- on Tyan S28?? : rock stable, unable to crash however
hard I tried
- on some MSI K8 (I usually run Vista on for testing; this one I
really bought "as cheap as possible" ) : would run OK, even
under rather heavy load, but when pushing really hard it
finaly deliveres the lovely g_vfs_done ...
I vaguely remember from another PR that the Promise card does
something with PCI-bursting which fbsd does not detect and/or
handle correctly (and beyond my simple skills as dumb tester, but
maybe the linux-sources contain a clue about that as well).
Regards and thanx for your efforts
Arno
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?wptzo4yqj7.fsf>