Date: Fri, 6 Oct 2000 20:57:47 +0200 From: Stefan `Sec` Zehl <sec@42.org> To: Nik Clayton <nik@FreeBSD.ORG> Cc: Anders Petersson NV98ETe <Anders_Petersson_NV98ETe@teknikum.vaxjo.se>, mobile@FreeBSD.ORG Subject: Re: Vaio F709 resetting when suspending to memory Message-ID: <20001006205747.D25318@matrix.42.org> In-Reply-To: <20001004192158.A373@canyon.nothing-going-on.org>; from nik@FreeBSD.ORG on Wed, Oct 04, 2000 at 07:21:58PM %2B0100 References: <20001004152018.A13393@canyon.nothing-going-on.org> <msg112222.thr-a6751d0e.a2c2a@kungsmadskolan.se> <20001004192158.A373@canyon.nothing-going-on.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 04, 2000 at 07:21:58PM +0100, Nik Clayton wrote:
> If I now run "zzz" or Fn+Esc, it suspends to memory with no problems.
[...]
> Yep, that worked. The machine's been up a few minutes. I suspect it's
> related to uptime, or the load the machine's been subjected to, or similar,
> but I can't see how to track it down.
Were I to speculate, I'd say it might be memory-related. Maybe your BIOS
somehow uses some part of your memory on the 'upper end'. And only when
your computer's run long enough so FreeBSD actually writes something
there suspendig fails.
You could try with a simple 'malloc all avail ram, and write to it
sequentially' Then try to suspend every few MB of overwritten ram.
You could then compile a kernel with an aprropriate
MAXMEM="(128*1024)" option, and see if that fixes it.
I'm speculating about this, because my old Compaq aero, upgraded to 20MB
would crash if you'd access the MB between 15 and 16.
Good Luck,
CU,
Sec
--
I know that you believe that you understand what you think I said.
But I am not sure you realize, that what you heared is not what i meant.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001006205747.D25318>