From: Roman Kononov <kononov@ftml.net>
To: linux-xfs@oss.sgi.com
Subject: failed assertion related to realtime section
Date: Mon, 13 Jul 2009 17:42:43 -0500 [thread overview]
Message-ID: <h3gd94$clb$1@ger.gmane.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 353 bytes --]
Hi,
In 2.6.30.x Linux kernel, the XFS_RT configuration option does not say "This
feature is unsupported at this time..." any more. Nevertheless, when
enabled, the feature crashes the file system in my setup. Is it expected to
be functional?
The attached assertion log happens every time with a clean and empty file
system.
Thanks,
Roman Kononov
[-- Attachment #2: rt-assertion.txt --]
[-- Type: text/plain, Size: 2443 bytes --]
Assertion failed: xfs_trans_get_block_res(tp) > 0, file: /home/stuff/base/linux-2.6.30.1/fs/xfs/xfs_bmap.c, line: 5602
------------[ cut here ]------------
kernel BUG at /home/stuff/base/linux-2.6.30.1/fs/xfs/support/debug.c:109!
invalid opcode: 0000 [#1] SMP
last sysfs file: /sys/devices/pci0000:00/0000:00:01.1/i2c-adapter/i2c-1/1-002e/vrm
CPU 0
Modules linked in: ib_mthca sata_nv
Pid: 1392, comm: ps Not tainted 2.6.30.1 #5
RIP: 0010:[<ffffffff8039f9da>] [<ffffffff8039f9da>] assfail+0x1a/0x20
RSP: 0018:ffff8800a207bbe8 EFLAGS: 00010292
RAX: 000000000000007a RBX: 0000000000001fff RCX: 0000000000000000
RDX: ffff880028022000 RSI: 0000000000000046 RDI: ffffffff8071a854
RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000002
R10: 0000000000000000 R11: ffffffff803cfda0 R12: ffff8800aa296f00
R13: ffff8800aa296f38 R14: ffff8800aa296f58 R15: ffff88013ac1f000
FS: 00007f86318316e0(0000) GS:ffff880028022000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f862f80f000 CR3: 0000000000201000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process ps (pid: 1392, threadinfo ffff8800a207a000, task ffff8800988fc000)
Stack:
0008000000000000 ffffffff80345e9c ffff8800a207bc48 ffff8800a207bcc8
ffff8800aa2971b0 000000000000000e 0000000000000001 0000000000000024
0000000000000000 0000000000000002 0000000000000001 ffff8800a04ed350
Call Trace:
[<ffffffff80345e9c>] ? xfs_bunmapi+0xc5c/0x11e0
[<ffffffff8036dd50>] ? xfs_itruncate_finish+0x2b0/0x5d0
[<ffffffff8038eae1>] ? xfs_free_eofblocks+0x271/0x2c0
[<ffffffff80396f50>] ? xfs_file_release+0x10/0x20
[<ffffffff8029ed22>] ? __fput+0xc2/0x210
[<ffffffff8029b8d6>] ? filp_close+0x56/0x90
[<ffffffff8023a7f6>] ? put_files_struct+0x76/0xf0
[<ffffffff8023c560>] ? do_exit+0x670/0x6e0
[<ffffffff8029e32e>] ? vfs_write+0x11e/0x170
[<ffffffff8023c615>] ? do_group_exit+0x45/0xb0
[<ffffffff8023c692>] ? sys_exit_group+0x12/0x20
[<ffffffff8020bdeb>] ? system_call_fastpath+0x16/0x1b
Code: 08 01 00 00 00 e8 27 19 03 00 48 83 c4 18 c3 66 90 89 d1 48 83 ec 08 48 89 f2 31 c0 48 89 fe 48 c7 c7 e8 d9 5e 80 e8 06 c7 1a 00 <0f> 0b eb fe 66 90 48 83 ec 28 48 89 1c 24 4c 89 6c 24 18 89 fb
RIP [<ffffffff8039f9da>] assfail+0x1a/0x20
RSP <ffff8800a207bbe8>
---[ end trace 97560c5848de56ab ]---
Fixing recursive fault but reboot is needed!
[-- Attachment #3: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2009-07-13 22:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 22:42 Roman Kononov [this message]
2009-07-15 12:23 ` failed assertion related to realtime section Olaf Weber
2009-07-16 0:15 ` Roman Kononov
[not found] ` <bzyfxcxgd3z.fsf@fransum.emea.sgi.com>
2009-08-04 21:04 ` Roman Kononov
[not found] ` <bzyiqh21oab.fsf@fransum.emea.sgi.com>
2009-08-05 23:21 ` Roman Kononov
2009-08-06 0:38 ` Roman Kononov
2009-08-05 3:58 ` Eric Sandeen
2009-08-05 23:07 ` Roman Kononov
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='h3gd94$clb$1@ger.gmane.org' \
--to=kononov@ftml.net \
--cc=linux-xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox