Date: Wed, 16 Mar 2005 03:43:55 +0000 From: Jason Henson <jason@ec.rr.com> To: Jean Lagarde <jlagarde@bigfoot.com> Cc: freebsd-questions@freebsd.org Subject: Re: 5.3-release fine with 512MB RAM, reboots at times with 1.5GB (but no panic) Message-ID: <1110944635l.25764l.0l@BARTON> In-Reply-To: <4237A3A3.3040704@bigfoot.com> (from jlagarde@bigfoot.com on Tue Mar 15 22:10:27 2005) References: <4237A3A3.3040704@bigfoot.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/15/05 22:10:27, Jean Lagarde wrote: > I have been troubleshooting reboots over the last weekend, I think I =20 > might have enough clues now to get some useful hints from an expert. >=20 > FreeBSD 5.3-release (see dmesg below for details) >=20 > The problem seems to be with trying to run with 1.5GB vice 512MB of =20 > RAM. The system has not had problems so far when I only leave the =20 > 512MB stick in. When I add the 1GB stick the system will reboot at =20 > specific times, for example, while trying to launch KDE3 or trying to =20 > make OpenOffice (always reboots at "Extracting for =20 > openoffice-1.1.2-1"). I do not see any panic in the messages log, the =20 > system just silently reboots. >=20 > I initially installed FreeBSD with only the 512MB stick in. >=20 > The memory itself seems fine; memtest86 detects no errors. >=20 > At boot time all the memory is detected: >=20 > real memory =3D 1610547200 (1535 MB) > avail memory =3D 1568432128 (1495 MB) >=20 > Running "memtest all" only seems to find 512MB to use. It evidently =20 > makes no assumption about how much memory is there, starting by =20 > trying to malloc 4GB and reducing the amount gradually until it =20 > finally successfully mallocs 512 MB and eventually manages to lock =20 > 413 MB (failed due to "insufficient resources" above that). The tests =20 > on the 413 MB do pass. >=20 > I have rebuilt the kernel with VM_KMEM_SIZE_MAX=3D419430400 as =20 > suggested in the FAQ. No change. >=20 > Would setting MAXMEM to 1572864 help? I am not sure since the correct =20 > amount is reported by FreeBSD at boot, and right now trying to make =20 > the kernel with that option seems to be another case that reboots the =20 > machine (i.e. the make process itself reboots the machine) so I have =20 > not tried it yet (guess I would have to remove the 1GB stick to make =20 > the new kernel and then put it back to try it out). >=20 > Thank you for any help. > What happens with just the gig stcik? What happens when you switch the =20 slots the sticks are in? Are the sticks the sam brand? Are the =20 brands/brand supported? http://www.sis.com/support/support_memory_3.htm Are you overclocking? intersresting read on the sis memory controller http://www.lostcircuits.com/motherboard/asus_p4s333/ I also find it hard to believe you have a bad mptable. Maybe you could =20 check for a new bios? It is kind of funny if sis used the ms acpi =20 tools and not intels for an intel system. I say this because I have =20 never heard of problems from the intel acpi tools, and ms is the only =20 other set I know of. > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > dmesg > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > FreeBSD 5.3-RELEASE #1: Sun Mar 13 20:01:36 PST 2005 > xxxxxxxxxxxxxxxxx:/usr/src/sys/i386/compile/KERNEL_JEAN > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Pentium(R) 4 CPU 2.20GHz (2205.01-MHz 686-class CPU) > Origin =3D "GenuineIntel" Id =3D 0xf24 Stepping =3D 4 > =20 > Features=3D0x3febfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PG= E,MCA,C > MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM> > real memory =3D 1610547200 (1535 MB) > avail memory =3D 1568432128 (1495 MB) > mptable_probe: MP Config Table has bad signature: .\M^K\M-@
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1110944635l.25764l.0l>