From: Alex Deucher <alexdeucher@gmail.com>
To: jfs-discussion@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ag@m-cam.com
Subject: jfs mount causes oops on sparc64
Date: Fri, 1 Jul 2005 14:13:34 -0400 [thread overview]
Message-ID: <a728f9f905070111133a24590@mail.gmail.com> (raw)
I have a 6.9 TB jfs LVM volume on a sparc64 debian box, however mount
seems to cause an oops when I attempt to mount the volume:
jfs_mount: diMount(ipaimap) failed w/rc = -5
data_access_exception: SFSR[0000000000801009] SFAR[000000000043f770], going.
\|/ ____ \|/
"@'/ .. \`@"
/_| \__/ |_\
\__U_/
mount(3502): Dax [#1]
TSTATE: 0000004411009607 TPC: 000000000051b8d0 TNPC: 000000000051b8d4
Y: 00000000 Not tainted
TPC: <diFree+0x30/0xe20>
g0: fffff800bd24aca1 g1: 0000000000000000 g2: fffff800bdd39800 g3:
fffff800bdd398c8
g4: fffff800bbcce800 g5: 0000000000000000 g6: fffff800bd248000 g7:
fffff80093977d88
o0: 0000000000000000 o1: 0000000000000001 o2: fffff800bd167c10 o3:
0000000000000000
o4: fffffffffffffffa o5: 0000000000000001 sp: fffff800bd24acf1 ret_pc:
00000000004410d4
RPC: <__wake_up_common+0x34/0x80>
l0: 0000000000000000 l1: 0000000000000001 l2: 0000000000444d0c l3:
0000000000000400
l4: 0000000000000000 l5: 0000000000000000 l6: 0000000000000000 l7:
0000000000000008
i0: fffff80093977d68 i1: fffff800bd24b6d0 i2: 0000000000000001 i3:
737400000043f76c
i4: 0000000000000000 i5: 00000000007e1400 i6: fffff800bd24ae61 i7:
000000000050fcd0
I7: <jfs_delete_inode+0x30/0x160>
Caller[000000000050fcd0]: jfs_delete_inode+0x30/0x160
Caller[000000000049f004]: generic_delete_inode+0xc4/0x160
Caller[000000000049f28c]: iput+0x6c/0xc0
Caller[0000000000512c8c]: jfs_mount+0x8c/0x320
Caller[000000000050f3b0]: jfs_fill_super+0xb0/0x2c0
Caller[000000000048bd68]: get_sb_bdev+0x108/0x160
Caller[000000000048bfc0]: do_kern_mount+0x40/0x100
Caller[00000000004a1ca4]: do_new_mount+0x64/0xa0
Caller[00000000004a2338]: do_mount+0x118/0x180
Caller[00000000004ad950]: compat_sys_mount+0xb0/0x160
Caller[0000000000410df4]: linux_sparc_syscall32+0x34/0x40
Caller[0000000000012824]: 0x12824
Instruction DUMP: c2586028 c277a767 f6587f98 <c206e004> 80a58001
16400369 ae100018 f40e3dfa 833da000
kernel is 2.6.12rc3 on debian sparc. Any ideas?
Alex
next reply other threads:[~2005-07-01 18:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-01 18:13 Alex Deucher [this message]
2005-07-01 18:42 ` jfs mount causes oops on sparc64 Luigi Genoni
2005-07-01 22:04 ` Alex Deucher
2005-07-02 23:09 ` [Jfs-discussion] " Dave Kleikamp
2005-07-03 1:45 ` Alex Deucher
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=a728f9f905070111133a24590@mail.gmail.com \
--to=alexdeucher@gmail.com \
--cc=ag@m-cam.com \
--cc=jfs-discussion@lists.sourceforge.net \
--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