From: Andrew Morton <akpm@osdl.org>
To: Miquel van Smoorenburg <miquels@cistron.nl>
Cc: linux-lvm@sistina.com, linux-kernel@vger.kernel.org,
Nick Piggin <piggin@cyberone.com.au>, Jens Axboe <axboe@suse.de>
Subject: Re: System hangs after echo value > /sys/block/dm-0/queue/nr_requests
Date: Tue, 30 Dec 2003 03:42:39 -0800 [thread overview]
Message-ID: <20031230034239.27950054.akpm@osdl.org> (raw)
In-Reply-To: <20031229130055.GA30647@cistron.nl>
Miquel van Smoorenburg <miquels@cistron.nl> wrote:
>
> If you echo a value (any value; for example the default 128) to
> /sys/block/dm-0/queue/nr_requests the shell you are in hangs.
> After about 5 seconds, the whole system hangs 100%.
hm, nice. It does the same thing for /sys/block/md0/queue/nr-requests.
With CONFIG_DEBUG_SPINLOCK enabled we go BUG in __wake_up():
Program received signal SIGTRAP, Trace/breakpoint trap.
__wake_up (q=0xcf299e90, mode=3, nr_exclusive=1) at include/asm/spinlock.h:137
137 BUG();
(gdb) bt
#0 __wake_up (q=0xcf299e90, mode=3, nr_exclusive=1) at include/asm/spinlock.h:137
#1 0xc02cc847 in queue_requests_store (q=0xcf299df8, page=0xe <Address 0xe out of bounds>, count=14)
at drivers/block/ll_rw_blk.c:2843
#2 0xc02cc907 in queue_attr_store (kobj=0xcf299f68, attr=0xe, page=0xe <Address 0xe out of bounds>,
length=14) at drivers/block/ll_rw_blk.c:2892
#3 0xc01aa84f in flush_write_buffer (file=0xe, buffer=0xc0456100, count=14) at fs/sysfs/file.c:205
#4 0xc01aa8ac in sysfs_write_file (file=0xc0493550, buf=0xe <Address 0xe out of bounds>, count=2,
ppos=0xc851cf84) at fs/sysfs/file.c:233
#5 0xc016f458 in vfs_write (file=0xc0493550, buf=0x80b2d00 "128\n", count=4, pos=0xc851cf84)
at fs/read_write.c:257
#6 0xc016f55e in sys_write (fd=14, buf=0xe <Address 0xe out of bounds>, count=14) at fs/read_write.c:293
Where queue_requests_store() does wake_up(&rl->wait[READ]);
It looks like nobody has called blk_init_queue() for this queue and the
waitqueue head is uninitialised.
No md was in use on this machine: it was simply enabled in kernel config.
next prev parent reply other threads:[~2003-12-30 11:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-29 13:00 Miquel van Smoorenburg
2003-12-30 11:42 ` Andrew Morton [this message]
2003-12-31 0:44 ` Mike Christie
2003-12-31 10:32 ` Jens Axboe
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=20031230034239.27950054.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lvm@sistina.com \
--cc=miquels@cistron.nl \
--cc=piggin@cyberone.com.au \
/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
all inboxes | Powered by JetHome®