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 09:20:12 +0300 [thread overview]
Message-ID: <20020207092012.C6351@namesys.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0202061850060.17669-100000@Expansa.sns.it>
In-Reply-To: <Pine.LNX.4.44.0202061850060.17669-100000@Expansa.sns.it>
Hello!
On Wed, Feb 06, 2002 at 06:53:47PM +0100, Luigi Genoni wrote:
> I was trying 2.5.4-pre1 on sparc64 sun4u ultra2,
> with 1GB memory and scsi controller ess.
> This system has just one CPU.
> >>TPC; 0046cf7c <grow_buffers+5c/e0> <=====
> >>O7; 0046cf38 <grow_buffers+18/e0>
> >>I7; 0046b260 <__getblk+20/60>
> Trace; 0046b260 <__getblk+20/60>
> Trace; 0046b56c <__bread+c/a0>
> Trace; 004d1374 <journal_init+214/8e0>
This looks like VFS have exploded for whatever reson, I think
because one ot these checks failed:
linux/fs/buffer.c:
if (size & (get_hardsect_size(to_kdev_t(bdev->bd_dev))-1))
BUG();
/* Size must be within 512 bytes and PAGE_SIZE */
if (size < 512 || size > PAGE_SIZE)
BUG();
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?
Bye,
Oleg
next prev parent reply other threads:[~2002-02-07 6:20 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 ` Oleg Drokin [this message]
2002-02-07 9:58 ` [reiserfs-dev] " Luigi Genoni
2002-02-07 10:03 ` Oleg Drokin
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=20020207092012.C6351@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.