From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.0-test2-mm5
Date: Wed, 06 Aug 2003 23:31:47 -0700 [thread overview]
Message-ID: <28050000.1060237907@[10.10.2.4]> (raw)
In-Reply-To: <20030806223716.26af3255.akpm@osdl.org>
--Andrew Morton <akpm@osdl.org> wrote (on Wednesday, August 06, 2003 22:37:16 -0700):
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test2/2.6.0-test2-mm5/
>
>
> Lots of different things. Mainly trying to get this tree stabilised again;
> there has been some breakage lately.
I get lots of these .... (without 4/4 turned on)
Badness in as_dispatch_request at drivers/block/as-iosched.c:1241
Call Trace:
[<c01ca8d2>] as_dispatch_request+0x216/0x264
[<c01ca938>] as_next_request+0x18/0x2c
[<c01c343b>] elv_next_request+0x9f/0xd4
[<c01d4cd6>] scsi_request_fn+0x2e/0x280
[<c01c4e2f>] blk_run_queue+0x27/0x38
[<c01d43af>] scsi_run_queue+0xb3/0xbc
[<c01d43ff>] scsi_next_command+0x17/0x1c
[<c01d44bc>] scsi_end_request+0x88/0x94
[<c01d483b>] scsi_io_completion+0x1ef/0x408
[<c01dfa4e>] sd_rw_intr+0x1ce/0x1d8
[<c01d120d>] scsi_finish_command+0x89/0x90
[<c01d113d>] scsi_softirq+0xc5/0xe0
[<c012236c>] do_softirq+0x6c/0xcc
[<c010c1d3>] do_IRQ+0x113/0x124
[<c023c0d8>] common_interrupt+0x18/0x20
Badness in as_completed_request at drivers/block/as-iosched.c:930
Call Trace:
[<c01ca29c>] as_completed_request+0xe4/0x170
[<c01c357b>] elv_completed_request+0x13/0x18
[<c01c575e>] __blk_put_request+0x2a/0x84
[<c01c661d>] end_that_request_last+0xc5/0xd8
[<c01d44a8>] scsi_end_request+0x74/0x94
[<c01d483b>] scsi_io_completion+0x1ef/0x408
[<c01dfa4e>] sd_rw_intr+0x1ce/0x1d8
[<c01d120d>] scsi_finish_command+0x89/0x90
[<c01d113d>] scsi_softirq+0xc5/0xe0
[<c012236c>] do_softirq+0x6c/0xcc
[<c010c1d3>] do_IRQ+0x113/0x124
[<c023c0d8>] common_interrupt+0x18/0x20
seems to work, but whines a lot ;-)
M.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-08-07 6:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 5:37 2.6.0-test2-mm5 Andrew Morton
2003-08-07 6:31 ` Martin J. Bligh [this message]
2003-08-07 7:05 ` 2.6.0-test2-mm5 Andrew Morton
2003-08-07 8:29 ` 2.6.0-test2-mm5 Nick Piggin
2003-08-07 8:40 ` 2.6.0-test2-mm5 Nick Piggin
2003-08-07 8:43 ` 2.6.0-test2-mm5 Nick Piggin
2003-08-07 18:30 ` 2.6.0-test2-mm5 Martin J. Bligh
2003-08-07 8:44 ` 2.6.0-test2-mm5 Jens Axboe
2003-08-07 6:33 ` 2.6.0-test2-mm5 William Lee Irwin III
2003-08-07 6:44 ` 2.6.0-test2-mm5 Andrew Morton
2003-08-07 8:00 ` 2.6.0-test2-mm5 Christoph Hellwig
2003-08-07 21:21 ` 2.6.0-test2-mm5 Marcelo Tosatti
2003-08-07 21:24 ` 2.6.0-test2-mm5 William Lee Irwin III
2003-08-07 21:28 ` 2.6.0-test2-mm5 Andrew Morton
2003-08-07 22:07 ` 2.6.0-test2-mm5 Marcelo Tosatti
2003-08-08 20:51 ` 2.6.0-test2-mm5 Marcelo Tosatti
2003-08-08 21:36 ` 2.6.0-test2-mm5 William Lee Irwin III
2003-08-07 23:47 ` 2.6.0-test2-mm5 Martin J. Bligh
2003-08-08 0:16 ` 2.6.0-test2-mm5 William Lee Irwin III
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='28050000.1060237907@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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