From: "Andrew Paprocki" <andrew@ishiboo.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.24.3 kernel panic in md raid1d queue_delayed_work_on
Date: Sun, 16 Mar 2008 02:25:21 -0400 [thread overview]
Message-ID: <76366b180803152325x63424d09vb775b5ed44b961e1@mail.gmail.com> (raw)
I had an embedded machine hang last night with a kernel panic in
queue_delayed_work_on. I couldn't scroll back the terminal to get more
of the trace, but I jotted down what I could see on the screen. This
is a Geode LX system running a SATA RAID1 array as md0 on a SiI 3114
controller using libata. Any ideas? If the .config or boot log from
this machine would be useful, let me know and I'll get them.
Thanks,
-Andrew
----- top of scrollback
handle_IRQ_event+0x1a/0x3f
handle_level_irq+0x4f/0x84
do_IRQ+0x53/0x6b
common_interrupt+0x23/0x28
__make_request+0x480/0x48a
generic_make_request+0x1fd/0x22a
common_interrupt+0x23/0x28
__generic_unplug_device+0x14/0x1f
generic_unplug_device+0x6/0x8
blk_remove_plug+0x4e/0x5a
raid1d+0xc3/0xc35
irq_exit+0x40/0x58
do_IRQ+0x58/0x6b
update_curr+0x52/0xc4
schedule+0x1f3/0x20d
schedule_timeout+0x13/0x97
sys_capget+0x54/0xcb
md_thread+0xb5/0xcb
autoremove_wake_function+0x0/0x35
md_thread+0x0/0xcb
kthread+0x36/0x5c
kthread+0x0/0x5c
kernel_thread_helper+0x7/0x10
Code: 8d 50 10 e9 48 ff ff ff 31 d2 e9 41 ff ff ff 57 89 c7 56 89 d6
53 8d 59 3(clipped)
0f ba 29 00 19 c0 31 d2 85 c0 75 61 83 79 10 00 74 04 <0f> 0b eb fe
8d 41 04 3(clipped)
41 04 74 04 0f 0b eb fe 8b 01 8b 16 a8
EIP: [<c022609a>] queue_delayed_work_on+0x1c/0x7d SS:ESP 0068:cf359d80
Kernel panic - not syncing: Fatal exception in interrupt
next reply other threads:[~2008-03-16 6:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-16 6:25 Andrew Paprocki [this message]
2008-03-25 5:29 ` 2.6.24.3 kernel panic in md raid1d queue_delayed_work_on Neil Brown
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=76366b180803152325x63424d09vb775b5ed44b961e1@mail.gmail.com \
--to=andrew@ishiboo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox