From: Oleg Drokin <green@namesys.com>
To: Luigi Genoni <kernel@Expansa.sns.it>
Cc: reiserfs-dev@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: [reiserfs-dev] oops with reiserfs and kernel 2.5.4-pre1 on sparc64
Date: Thu, 7 Feb 2002 13:03:56 +0300 [thread overview]
Message-ID: <20020207130356.A18577@namesys.com> (raw)
In-Reply-To: <20020207092012.C6351@namesys.com> <Pine.LNX.4.44.0202071058010.25208-100000@Expansa.sns.it>
In-Reply-To: <Pine.LNX.4.44.0202071058010.25208-100000@Expansa.sns.it>
Hello!
On Thu, Feb 07, 2002 at 10:58:27AM +0100, Luigi Genoni wrote:
> > Can any of sparc64 people comment on what kind of exception will one
> > get for __builtin_trap?
> > Second BUG() seems to be out of the question, though.
> > Do you have CONFIG_DEBUG_BUGVERBOSE enabled?
> No, I have not
If you'd enable it, you'd get a message on a next crash, where this BUG()
happened exactly (so that we can verify my guess)
Bye,
Oleg
next prev parent reply other threads:[~2002-02-07 10:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-06 17:53 oops with reiserfs and kernel 2.5.4-pre1 on sparc64 Luigi Genoni
2002-02-07 6:20 ` [reiserfs-dev] " Oleg Drokin
2002-02-07 9:58 ` Luigi Genoni
2002-02-07 10:03 ` Oleg Drokin [this message]
2002-02-07 14:59 ` Luigi Genoni
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=20020207130356.A18577@namesys.com \
--to=green@namesys.com \
--cc=kernel@Expansa.sns.it \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-dev@namesys.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.