From: "Berck E. Nash" <flyboy@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Scheduling while atomic lockups, Reiser4, DAC960
Date: Tue, 17 May 2005 14:07:24 -0500 [thread overview]
Message-ID: <428A40EC.8050206@gmail.com> (raw)
Linux luna 2.6.12-rc4-mm1 i686
Debian unstable, AMD Athlon
The error seems to occur with my reiser4 partition. The physical
device is an 8-disk RAID-0 array on a Mylex Extreme RAID 1100 using the
DAC960 driver. The error is sometimes followed by a lockup, but not always.
Not sure if it's a hardware problem or kernel problem.
There's pages and pages of errors that look like this. If there's
anything I can do to provide more information, I will gladly do so.
Just a user, not a hacker. I'm not subscribed to the list, so cc's on
reply would be appreciated.
Thanks,
Berck
scheduling while atomic: pdflush/0xffffffff/92
May 16 03:36:43 luna kernel: [<c02f6ac4>] schedule+0x604/0x610
May 16 03:36:43 luna kernel: [<c02f6265>] __down+0x85/0x120
May 16 03:36:43 luna kernel: [<c0115020>] default_wake_function+0x0/0x10
May 16 03:36:43 luna kernel: [<c02f645f>] __down_failed+0x7/0xc
May 16 03:36:43 luna kernel: [<c024b420>] blk_backing_dev_unplug+0x0/0x10
May 16 03:36:43 luna kernel: [<c01c5ca3>] .text.lock.flush_queue+0x8/0x25
May 16 03:36:43 luna kernel: [<c01c5524>] finish_fq+0x14/0x40
May 16 03:36:43 luna kernel: [<c01c55ae>] finish_all_fq+0x5e/0xa0
May 16 03:36:43 luna kernel: [<c01c560e>]
current_atom_finish_all_fq+0x1e/0x70
May 16 03:36:43 luna kernel: [<c01c167c>] reiser4_write_logs+0x20c/0x2b0
May 16 03:36:43 luna kernel: [<c01ba599>] commit_current_atom+0x109/0x1e0
May 16 03:36:43 luna kernel: [<c01c5957>] release_prepped_list+0xf7/0x130
May 16 03:36:43 luna kernel: [<c01bae23>] try_commit_txnh+0x113/0x190
May 16 03:36:43 luna kernel: [<c01baec8>] commit_txnh+0x28/0xa0
May 16 03:36:43 luna kernel: [<c01b9d7c>] txn_end+0x2c/0x30
May 16 03:36:43 luna kernel: [<c01bab2b>] flush_some_atom+0x1fb/0x290
May 16 03:36:43 luna kernel: [<c01c9368>] writeout+0x68/0xb0
May 16 03:36:43 luna kernel: [<c01c940b>] reiser4_sync_inodes+0x5b/0xa0
May 16 03:36:43 luna kernel: [<c01c93b0>] reiser4_sync_inodes+0x0/0xa0
May 16 03:36:43 luna kernel: [<c0174a59>] sync_sb_inodes+0x19/0x20
May 16 03:36:43 luna kernel: [<c0174b1e>] writeback_inodes+0xbe/0xd0
May 16 03:36:43 luna kernel: [<c013be15>] background_writeout+0x65/0xa0
May 16 03:36:43 luna kernel: [<c013c748>] __pdflush+0xc8/0x1c0
May 16 03:36:43 luna kernel: [<c013c840>] pdflush+0x0/0x20
May 16 03:36:43 luna kernel: [<c013c85a>] pdflush+0x1a/0x20
May 16 03:36:43 luna kernel: [<c013bdb0>] background_writeout+0x0/0xa0
May 16 03:36:43 luna kernel: [<c013c840>] pdflush+0x0/0x20
May 16 03:36:43 luna kernel: [<c012bb44>] kthread+0x94/0xa0
May 16 03:36:43 luna kernel: [<c012bab0>] kthread+0x0/0xa0
May 16 03:36:43 luna kernel: [<c0100f1d>] kernel_thread_helper+0x5/0x18
next reply other threads:[~2005-05-17 19:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 19:07 Berck E. Nash [this message]
2005-05-17 21:57 ` Scheduling while atomic lockups, Reiser4, DAC960 Hans Reiser
2005-05-19 6:18 ` Vladimir Saveliev
2005-05-19 14:10 ` Berck E. Nash
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=428A40EC.8050206@gmail.com \
--to=flyboy@gmail.com \
--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 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.