From: Jan Kara <jack@suse.cz>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@digeo.com>
Subject: Oops in ext3 in 2.5.64
Date: Fri, 21 Mar 2003 17:12:06 +0100 [thread overview]
Message-ID: <20030321161206.GA5476@atrey.karlin.mff.cuni.cz> (raw)
[-- Attachment #1: Type: text/plain, Size: 2191 bytes --]
Hello,
I got a following oops from the friend of mine:
The kernel oopsed while doing 'sync' after compiling wine.
The system is 2.5.64 with two Athlons, acls & extended attributes
enabled.
The system also has problems (both on 2.5.64 and 2.5.65) when
running 'make -j4 install' in wine - processes get stuck in D state -
probably because pdflush is stuck in __make_request and other processes
are waiting on locks it's holding... Trace of stuck processes is
attached.
Honza
Assertion failure in journal_stop() at fs/jbd/transaction.c:1334: "transaction->t_updates > 0"
------------[ cut here ]------------
kernel BUG at fs/jbd/transaction.c:1334!
invalid operand: 0000
CPU: 0
EIP: 0060:[journal_stop+473/496] Not tainted
EFLAGS: 00010286
EIP is at journal_stop+0x1d9/0x1f0
eax: 00000062 ebx: 00000000 ecx: 00000012 edx: c03f2580
esi: df09c3c0 edi: 00000000 ebp: dba7de00 esp: dfdadd60
ds: 007b es: 007b ss: 0068
Process pdflush (pid: 11, threadinfo=dfdac000 task=dfdae680)
Stack: c03a3080 c0389ba1 c03a0d77 00000536 c03a0d8c dfc8da00 00000000 dba7de00
00000000 dbd8c6c8 c019a5b1 dba7de00 d6b3a570 00000000 00001000 00000000
c019a370 00000001 d6b3a570 c1373c50 dbd8c75c dfdac000 dfdadf80 c017b6ac
Call Trace:
[ext3_writepage+561/848] ext3_writepage+0x231/0x350
[bput_one+0/16] bput_one+0x0/0x10
[mpage_writepages+684/896] mpage_writepages+0x2ac/0x380
[mpage_writepages+684/896] mpage_writepages+0x2ac/0x380
[ext3_writepage+0/848] ext3_writepage+0x0/0x350
[do_writepages+54/64] do_writepages+0x36/0x40
[__sync_single_inode+271/688] __sync_single_inode+0x10f/0x2b0
[sync_sb_inodes+419/656] sync_sb_inodes+0x1a3/0x290
[writeback_inodes+136/304] writeback_inodes+0x88/0x130
[background_writeout+198/272] background_writeout+0xc6/0x110
[__pdflush+254/528] __pdflush+0xfe/0x210
[pdflush+0/32] pdflush+0x0/0x20
[pdflush+15/32] pdflush+0xf/0x20
[background_writeout+0/272] background_writeout+0x0/0x110
[kernel_thread_helper+0/24] kernel_thread_helper+0x0/0x18
[kernel_thread_helper+5/24] kernel_thread_helper+0x5/0x18
Code: 0f 0b 36 05 77 0d 3a c0 e9 39 fe ff ff 8d 76 00 8d bc 27 00
--
Jan Kara <jack@suse.cz>
SuSE CR Labs
[-- Attachment #2: tasks.out.bz2 --]
[-- Type: application/octet-stream, Size: 4515 bytes --]
next reply other threads:[~2003-03-21 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-21 16:12 Jan Kara [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-20 16:55 Oops in ext3 in 2.5.64 Jan Kara
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=20030321161206.GA5476@atrey.karlin.mff.cuni.cz \
--to=jack@suse.cz \
--cc=akpm@digeo.com \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).