All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: linux@horizon.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.8-rc2 4K stack overflow
Date: Tue, 27 Jul 2004 08:57:15 -0700	[thread overview]
Message-ID: <20040727155715.GD2334@holomorphy.com> (raw)
In-Reply-To: <20040727074813.4596.qmail@science.horizon.com>

On Tue, Jul 27, 2004 at 07:48:13AM -0000, linux@horizon.com wrote:
> Just a crash report.  Machine locked hard - no caps lock, no ping.
> Machine mostly idle.  Amanda network backup was running, but not daily cron.
> Backtrace copied by hand. (I didn't copy the leading addresses.)
> FWIW, only one partition (a RAID-0 non-critical data partition) is
> mounted with ext2.
> .config follows.  Compiler is GCC 3.3.4 (Debian 3.3.4-3)  Hardware is
> Intel Celeron, 440BX motherboard.
> Hopefully it helps someone.  I don't have frame pointers enabled, so I
> assume the confusing bits of the backtrace are clutter misidentified as
> a return address.

It looks like you took invalid opcode exceptions in addition to some
rather suspicious oopsen in/around buffered_rmqueue(). The latter are
likely stack gunk, the former OTOH I suspect may be real.

Could you try to reproduce without CONFIG_REGPARM and turn on frame
pointers? Might help a bit to cut down on ways backtraces might get
misinterpreted.


-- wli

      reply	other threads:[~2004-07-27 15:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-27  7:48 2.6.8-rc2 4K stack overflow linux
2004-07-27 15:57 ` William Lee Irwin III [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=20040727155715.GD2334@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@horizon.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.