Date: Sat, 11 Jun 2005 03:36:41 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Pyun YongHyeon <yongari@rndsoft.co.kr> Cc: Hiroki Sato <hrs@freebsd.org>, sparc64@freebsd.org Subject: Re: E4500 with 24GB RAM Message-ID: <20050611073640.GA34243@xor.obsecurity.org> In-Reply-To: <20050611072632.GB19976@rndsoft.co.kr> References: <20050606132756.X16994@carver.gumbysoft.com> <20050611.004435.59726356.hrs@allbsd.org> <20050610211239.GA59402@xor.obsecurity.org> <20050611.154028.102195481.hrs@allbsd.org> <20050611072632.GB19976@rndsoft.co.kr>
next in thread | previous in thread | raw e-mail | index | archive | help
--T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jun 11, 2005 at 04:26:32PM +0900, Pyun YongHyeon wrote: > On Sat, Jun 11, 2005 at 03:40:28PM +0900, Hiroki Sato wrote: > > Kris Kennaway <kris@obsecurity.org> wrote > > in <20050610211239.GA59402@xor.obsecurity.org>: > >=20 > > kr> I wonder if it's disk related. I tried to check out a ports tree = on > > kr> this machine and it hung in a few seconds (although this was also > > kr> checking out using the network via nfs). > >=20 > > I do not know why but the freeze occurs only when displaying "invalid > > packet size xxx; dropping". When I tried "vmstat 1" on the serial > > console and fetching a large file via ftp at the same time > > with 12GB RAM configuration, the freeze did not occur. > > Once "hme0: too may errors; not reporting any more" is displayed, > > the box seems to work fine and I can check out the ports tree via NFS > > without problems. > >=20 >=20 > Normally the "invalid packet size" message comes from link mismatch. > If your HME's PHY is DP83840 there are known issues on link neogotiation. > AFAIK the issue has nothing to do with panic as I always see that on my > Ultra2 which has DP83840 PHY too. This is on e450 and e4500 machines. I don't think there's a link mismatch. > I wonder how you can use NFS reliably on sparc64. Due to failure of > alignment(both server and client) it's really easy to get panic on sparc6= 4. AFAICR I've never seen a problem with this (except with an i386 4.x server, which can be panicked by a sparc64 client)..I don't rely on NFS heavily in most cases, but I do use it on a number of machines (including two package build machines that netboot and access their ports trees over NFS, and have been in continuous operation with an uptime of 110 days). > > I tried to comment out the HME_WHINE line of hme_read() in if_hme.c, > > and it seems to make the box work fine so far. >=20 > HME_WHINE() just prints a message. I can't think removing the function > can cure your problem. It does seem to have helped though..before it would reliably lock up in seconds, and DDB break was non-responsive. Kris --T4sUOijqQbZv57TR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCqpSIWry0BWjoQKURAnxQAKCI/8BOuX7BXWUry8s8EOEFID0SpwCg4069 B4ZNjye2F2kWzkTfLXYyhyk= =vMKr -----END PGP SIGNATURE----- --T4sUOijqQbZv57TR--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050611073640.GA34243>