From: Jens Axboe <axboe@suse.de>
To: Mark v Wolher <trilight@ns666.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Badness in as_insert_request at drivers/block/as-iosched.c:1519
Date: Sat, 7 Jan 2006 15:34:48 +0100 [thread overview]
Message-ID: <20060107143447.GF3389@suse.de> (raw)
In-Reply-To: <43BFC3FF.5080908@ns666.com>
On Sat, Jan 07 2006, Mark v Wolher wrote:
> Hiya all,
>
> I was just playing a cd as usual and i noticed suddenly the errors
> below, they repeated like 8 times.
>
> kernel: 2.6.14.5
Should be fixed in newer 2.6.14.x, and in 2.6.15.
--
Jens Axboe
next prev parent reply other threads:[~2006-01-07 14:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 13:37 Badness in as_insert_request at drivers/block/as-iosched.c:1519 Mark v Wolher
2006-01-07 13:49 ` Mark v Wolher
2006-01-07 14:33 ` Mark v Wolher
2006-01-07 14:34 ` Jens Axboe [this message]
2006-01-07 14:50 ` Mark v Wolher
2006-01-07 14:55 ` Jens Axboe
2006-01-07 15:03 ` Mark v Wolher
-- strict thread matches above, loose matches on Subject: below --
2005-10-31 20:40 Bongani Hlope
2005-11-01 6:59 ` Jens Axboe
2005-11-01 20:47 ` Bongani Hlope
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=20060107143447.GF3389@suse.de \
--to=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=trilight@ns666.com \
/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