twa breakage on AMD64 with9.1.5.23wareversionand2005-01-1103:00:49 UTC RELENG_5 commit

[jhs at berklix.org (Julian H. Stacey)]

Jean-Yves Avenard wrote:
	Cc: freebsd stable <freebsd-stable_(_at_)_freebsd_(_dot_)_org>
	Cc: freebsd-amd64_(_at_)_freebsd_(_dot_)_org
	Cc: freebsd-scsi_(_at_)_freebsd_(_dot_)_org
Header breaches rules:
	http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html#ERESOURCES-MAIL
	No posting should be made to more than 2 mailing lists,
	and only to 2 when ...
Stripped to freebsd-amd64@


> I'm just about to revert to FreeBSD i386 this week-end as i can't put 
> up with the constant amd64 crashes anymore...
> 
> It's not just the twa driver ; the NFS server often start to take 100% 
> of CPU time and various network utilities crashes once a week.

I also see crashes after heavy NFS on amd64 
(the box is my main X terminal - painful !)
	FreeBSD fire.jhs.private 5.3-RELEASE FreeBSD 5.3-RELEASE
	#0: Sat Feb 26 21:47:28 CET 2005
	jhs_(_at_)_fire_(_dot_)_jhs_(_dot_)_private:/usr1/src/sys/amd64/compile/FIRE64.small amd64
	http://lists.freebsd.org/pipermail/freebsd-fs/2005-March/000936.html

Dropping back to i386 would avoid i386/amd ports compat issues. It
might bring stability (don't know, not tried), or not I've also had
crashes on a new 686 box runing 5.3-RELEASE (not always heavy NFS
related, maybe &/or dvdrip related, but maybe it's hardware, that
686 host is newly arrived)...

I'll be aiming for stable next, & if I still have probs, then kernel
trace & send-pr, & finally current if I must :-)

PS re.
> can't wait to test..

Fortunately I built both my crashing hosts with the luxury of dual boot
partitions (F1 & 2) & a large common F3 of /usr1 for common data,
so I can take 1 slice up, & leave one at release for rescue :-)

-
Julian Stacey        Net & Sys Eng Consultant, Munich       http://berklix.com
Mail in Ascii (Html=Spam).  Ihr Rauch = mein allergischer Kopfschmerz.