From: Tom Wirschell <Tom@Wirschell.nl>
To: linux-ide@vger.kernel.org
Cc: Mark Lord <liml@rtr.ca>, Greg Freemyer <greg.freemyer@gmail.com>
Subject: Re: BUG() with MV88SX6081 and other problems
Date: Wed, 21 Jun 2006 17:32:10 +0200 [thread overview]
Message-ID: <20060621173210.6a7b3a83@localhost> (raw)
In-Reply-To: <20060621090734.5c237bad@localhost>
On 21 Jun 2006, Tom Wirschell wrote:
>
> I'm running my standard test now. I'll post the trace once it goes
> down.
And that one looks like this:
md: unbind<sdi2>
md: export_rdev(sdi2)
BUG: warning at fs/block_dev.c:1109/__blkdev_put()
[<c0103316>] show_trace_log_lvl+0x11d/0x137
[<c01039f7>] show_trace+0x12/0x14
[<c0103b17>] dump_stack+0x19/0x1b
[<c015f136>] __blkdev_put+0x174/0x1b7
[<c015f186>] blkdev_put_partition+0xd/0xf
[<c028cb80>] unlock_rdev+0x23/0x4c
[<c028cc1c>] export_rdev+0x73/0x81
[<c028cccb>] kick_rdev_from_array+0x12/0x15
[<c028ccf4>] export_array+0x26/0x95
[<c028e96c>] do_md_stop+0x1e3/0x2f8
[<c0292c60>] md_ioctl+0x6cb/0x17a0
[<c02016a6>] blkdev_driver_ioctl+0x55/0x5e
[<c020196d>] blkdev_ioctl+0x2be/0x7c1
[<c015ea84>] block_ioctl+0x1b/0x21
[<c0168652>] do_ioctl+0x22/0x71
[<c01686f6>] vfs_ioctl+0x55/0x28e
[<c0168962>] sys_ioctl+0x33/0x51
[<c02f8b6f>] syscall_call+0x7/0xb
[<b7e7a904>] 0xb7e7a904
BUG: warning at fs/block_dev.c:1128/__blkdev_put()
[<c0103316>] show_trace_log_lvl+0x11d/0x137
[<c01039f7>] show_trace+0x12/0x14
[<c0103b17>] dump_stack+0x19/0x1b
[<c015f174>] __blkdev_put+0x1b2/0x1b7
[<c015f186>] blkdev_put_partition+0xd/0xf
[<c028cb80>] unlock_rdev+0x23/0x4c
[<c028cc1c>] export_rdev+0x73/0x81
[<c028cccb>] kick_rdev_from_array+0x12/0x15
[<c028ccf4>] export_array+0x26/0x95
[<c028e96c>] do_md_stop+0x1e3/0x2f8
[<c0292c60>] md_ioctl+0x6cb/0x17a0
[<c02016a6>] blkdev_driver_ioctl+0x55/0x5e
[<c020196d>] blkdev_ioctl+0x2be/0x7c1
[<c015ea84>] block_ioctl+0x1b/0x21
[<c0168652>] do_ioctl+0x22/0x71
[<c01686f6>] vfs_ioctl+0x55/0x28e
[<c0168962>] sys_ioctl+0x33/0x51
[<c02f8b6f>] syscall_call+0x7/0xb
[<b7e7a904>] 0xb7e7a904
Kind regards,
Tom Wirschell
prev parent reply other threads:[~2006-06-21 15:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-17 17:17 BUG() with MV88SX6081 and other problems Tom Wirschell
2006-06-20 17:53 ` Greg Freemyer
2006-06-21 4:04 ` Mark Lord
2006-06-21 7:07 ` Tom Wirschell
2006-06-21 15:32 ` Tom Wirschell [this message]
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=20060621173210.6a7b3a83@localhost \
--to=tom@wirschell.nl \
--cc=greg.freemyer@gmail.com \
--cc=liml@rtr.ca \
--cc=linux-ide@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.