From: Petro <petro@auctionwatch.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Probable Memory/VM issue.
Date: Wed, 6 Mar 2002 18:25:07 -0800 [thread overview]
Message-ID: <20020307022507.GE32504@auctionwatch.com> (raw)
In-Reply-To: <20020306054143.GN22934@auctionwatch.com> <E16ikLn-00004q-00@the-village.bc.nu>
In-Reply-To: <E16ikLn-00004q-00@the-village.bc.nu>
On Wed, Mar 06, 2002 at 10:57:35PM +0000, Alan Cox wrote:
> > Bogus stack limit or frame pointer, fp=0xbfabf8c0, stack_bottom=0xbfc7fcb8, thread_stack=65536, aborting backtrace.
> > Trying to get some variables.
> > Some pointers may be invalid and cause the dump to abort...
> > thd->query at (nil) is invalid pointer
> > thd->thread_id=20479119
> Which says nothing alas - nothing about user or kernel space. If the system
> had run out of memory and killed it you'd have seen "killed" and an OOM
> entry logged
It definately did not run out of memory--we monitor that pretty
close, and the memory usage was pretty constant for the 90+ hours
prior to the crash.
--
Share and Enjoy.
prev parent reply other threads:[~2002-03-07 2:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-06 5:41 Probable Memory/VM issue Petro
2002-03-06 22:57 ` Alan Cox
2002-03-07 2:25 ` Petro [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020307022507.GE32504@auctionwatch.com \
--to=petro@auctionwatch.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox