Return-Path: <linux-kernel-owner+willy=40w.ods.org-S932324AbVKUPgP@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932324AbVKUPgP (ORCPT <rfc822;willy@w.ods.org>);
	Mon, 21 Nov 2005 10:36:15 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932330AbVKUPgP
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Mon, 21 Nov 2005 10:36:15 -0500
Received: from rwcrmhc13.comcast.net ([216.148.227.118]:17036 "EHLO
	rwcrmhc12.comcast.net") by vger.kernel.org with ESMTP
	id S932324AbVKUPgP (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Mon, 21 Nov 2005 10:36:15 -0500
Message-ID: <4381E960.8070108@ens-lyon.org>
Date: Mon, 21 Nov 2005 10:36:00 -0500
From: Brice Goglin <Brice.Goglin@ens-lyon.org>
User-Agent: Debian Thunderbird 1.0.7 (X11/20051017)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jens Axboe <axboe@suse.de>
CC: Linus Torvalds <torvalds@osdl.org>, LKML <linux-kernel@vger.kernel.org>,
       Andrew Morton <akpm@osdl.org>
Subject: Re: Linux 2.6.14: Badness in as-iosched
References: <Pine.LNX.4.64.0510271717190.4664@g5.osdl.org> <4373C042.3060901@ens-lyon.org> <20051121145446.GA15804@suse.de>
In-Reply-To: <20051121145446.GA15804@suse.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1509
Lines: 50

Jens Axboe wrote:

>On Thu, Nov 10 2005, Brice Goglin wrote:
>  
>
>>Hi Jens,
>>
>>I just hit a badness (actually, tons of badness like this) in as-iosched
>>while ripping
>>an audio CD with ripperX (with cdparanoia as a backend).
>>I was using 2.6.14 on an IBM Thinkpad R52. The kernel has been compiled with
>>gcc-4.0.2-2 (Debian testing).
>>
>>The first badness in dmesg is:
>>
>>cdrom: dropping to single frame dma
>>arq->state: 4
>>Badness in as_insert_request at drivers/block/as-iosched.c:1519
>> [<c0237410>] as_insert_request+0x70/0x1d0
>> [<c022dc25>] __elv_add_request+0xa5/0xe0
>> [<c022dc8b>] elv_add_request+0x2b/0x40
>> [<c0230fe6>] blk_execute_rq_nowait+0x46/0x60
>> [<c023107a>] blk_execute_rq+0x7a/0xe0
>> [<c0231310>] blk_end_sync_rq+0x0/0x30
>> [<c0160b77>] bio_phys_segments+0x27/0x30
>> [<c0232610>] blk_rq_bio_prep+0x40/0xb0
>> [<c0230dc7>] blk_rq_map_user+0xb7/0xf0
>> [<c026bc32>] cdrom_read_cdda_bpc+0x182/0x210
>> [<c026bd1b>] cdrom_read_cdda+0x5b/0xc0
>>    
>>
>
>Similar case was posted yesterday (I realize yours is older, just missed
>it the first time around), see my explanation here:
>
>http://lkml.org/lkml/2005/11/20/119
>
>And work-around below.
>  
>
Thank you very much, Jens.
Is this patch going to -stable ?

Brice Goglin

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/