Date: Mon, 27 Jan 2003 15:57:34 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: Vincent Poy <vince@oahu.WURLDLINK.NET> Cc: Eric Jones <fpicard@bellsouth.net>, walt <wa1ter@hotmail.com>, freebsd-current@FreeBSD.ORG Subject: Re: Options MAXMEM added to GENERIC kernel config causes kernelpanicin -current Message-ID: <3E35C76E.ACE90A92@mindspring.com> References: <20030126232934.T3206-100000@oahu.WURLDLINK.NET>
next in thread | previous in thread | raw e-mail | index | archive | help
Vincent Poy wrote: > > > MAXMEM is useful for testing configurations with less memory, > > > without having to open up your box and yank SIMMs, or to have > > > a bunch of different sized pairs of SIMMs lying around. > > > > For uses such as testing I can understand, but I don't see a use under > > normal conditions, at least on newer systems. I haven't dug into the > > source yet today, but there must be a reason why ACPI doesn't play nice > > on certain systems when MAXMEM is specified. > > > > I wonder if it is just AMD systems? Mine's a 900MHz Duron, and IIRC I > > think someone else in earlier in the thread was using an AMD also. > > I posted the original thread and can say the problem occurs on > both PII366 notebook, P4m-2Ghz, P4-1.7Ghz as well as PIII1Ghz systems and > various AMD Athlon XP's. This is a well known problem with the TLB implementation; the answer is that, were you to yank out real physical memory, so that you had the same amount of memory as your were telling the machine you had, you would end up with the same problem. In other words, the setting is exposing a bug in FreeBSD, and this is what it's supposed to be doing, so please leave it alone in the source code, so that someone who wants to fix it can reproduce the problem locally on their machine. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E35C76E.ACE90A92>