atom feed21 messages in org.freebsd.freebsd-sparc64E4500 with 24GB RAM
FromSent OnAttachments
Hiroki SatoMay 29, 2005 10:53 am 
Scott LongMay 29, 2005 7:36 pm 
Hiroki SatoJun 6, 2005 5:05 pm 
Marius StroblJun 6, 2005 9:04 pm 
Doug WhiteJun 6, 2005 9:04 pm 
Hiroki SatoJun 10, 2005 3:45 pm 
Kris KennawayJun 10, 2005 9:12 pm 
Scott LongJun 10, 2005 9:22 pm 
Hiroki SatoJun 11, 2005 6:44 am 
Kris KennawayJun 11, 2005 7:07 am 
Pyun YongHyeonJun 11, 2005 7:25 am 
Kris KennawayJun 11, 2005 7:36 am 
Hiroki SatoJun 11, 2005 7:50 am 
Pyun YongHyeonJun 11, 2005 7:54 am 
Kris KennawayJun 11, 2005 7:57 am 
Pyun YongHyeonJun 11, 2005 8:10 am 
Hiroki SatoJun 11, 2005 8:30 am 
John-Mark GurneyJun 11, 2005 8:47 am 
Hiroki SatoJun 11, 2005 8:48 am 
Pyun YongHyeonJun 11, 2005 9:19 am 
Sten SpansJun 13, 2005 10:54 pm 
Subject:E4500 with 24GB RAM
From:Hiroki Sato (hr@FreeBSD.org)
Date:Jun 11, 2005 6:44:05 am
List:org.freebsd.freebsd-sparc64

Kris Kennaway <kr@obsecurity.org> wrote in <2005@xor.obsecurity.org>:

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).

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.

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. Kris, could you try again? I think this is not a disk problem.