64 bit kernel - to the best of my understanding, a lot of the device drivers ( well, graphics ards at least ) map their own physical memory to the area just above the 32 bit limit, and when the kernel tries to access it too....
I'm sure someone will have a more exact description of what's happening. Some bioses allow the mapping of this much higher. Can't remember what the operation's called, but it's not available for my mobo ): Steve On Wed, 19 Sep 2007 13:04:04 +1200 Carl Cerecke <[EMAIL PROTECTED]> wrote: > Hi Steve, > > What was the symptoms with > 3G memory? Did the crashes happen on boot > up? Or randomly? > > I ask because I have a machine here (dual-core Intel, 4GB mem) that > has occasional hard freezes (all frozen. No kbd or even ping > response). I thought it might be the nvidia driver (using the latest > for the 8600GT card) and dual-core. And I can't use the nv driver > because it won't do dual-head on this card. So I was in the unusual > position of either having one-core (maxcpus=1 on kernel cmdline) and > two heads, or two-cores and one head. > > However, last night, the machine froze with just the one CPU enabled, > so it must be something else. Frustrating, because I'm running > long-running processes overnight. > > Perhaps if I told the kernel that I only have 3 GB ram it might help? > > Any ideas? > Cheers, > Carl. > > > On 19/09/2007, Steve Holdoway <[EMAIL PROTECTED]> wrote: > > On Wed, 19 Sep 2007 12:24:57 +1200 > > Roger Searle <[EMAIL PROTECTED]> wrote: > > > Following from the various updates and configuration changes made > > > yesterday, ntp is now able to do it's job. I'm happy . . . > > Whopee! I ended up with custom kernels, weird boot parameters and allsorts > > to get mine working. In the end, I think it was a kernel update that fixed > > it. Just a poor choice of motherboard I on my part I think. I still can't > > run more than 3GB memory without crashing, and there are no bios updates > > available ): > > > Roger > > > > > >
pgpBznv1fmGmm.pgp
Description: PGP signature
