All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: Rodolfo Boer <movez@gawab.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Badness in as_remove_dispatched_request
Date: Fri, 03 Oct 2003 18:33:01 +1000	[thread overview]
Message-ID: <3F7D343D.7000806@cyberone.com.au> (raw)
In-Reply-To: <200310031013.37366.movez@gawab.com>



Rodolfo Boer wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Hello! This is my first try with the 2.6.0-test kernels and I get AMOUNTS of 
>these warnings during boot-up on both test5 and test6 (this expecially is 
>from test6):
>
>Badness in as_remove_dispatched_request at drivers/block/as-iosched.c:1023
>Call Trace:
> [<c01e0ef1>] as_remove_dispatched_request+0x71/0x100
> [<c01d9b17>] elv_remove_request+0x27/0x40
> [<c01e5974>] ide_end_request+0xf4/0x150
> [<c01f4ae7>] ide_dma_intr+0x97/0xc0
> [<c01e70ca>] ide_intr+0xea/0x190
> [<c01f4a50>] ide_dma_intr+0x0/0xc0
> [<c010b3aa>] handle_IRQ_event+0x3a/0x70
> [<c010b731>] do_IRQ+0x91/0x130
> [<c0105000>] rest_init+0x0/0x60
> [<c0109b48>] common_interrupt+0x18/0x20
> [<c0105000>] rest_init+0x0/0x60
> [<c0106e93>] default_idle+0x23/0x30
> [<c0106efc>] cpu_idle+0x2c/0x40
> [<c02d670c>] start_kernel+0x14c/0x160
> [<c02d6480>] unknown_bootoption+0x0/0x100
>
>They are all the same. Otherwise the system *seems* to work fine, but I 
>haven't tried much since I want to solve this. Maybe the problem is with my 
>on-board hpt-372 disk controller (not in RAID configuration). If you need 
>more info or my .config just ask.
>

Hi Rodolfo,
Linus just merged some AS fixes. Could you test the latest cset please?
http://www.kernel.org/pub/linux/kernel/v2.6/testing/cset/ (topmost link)

Thanks.



  reply	other threads:[~2003-10-03  8:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-03  8:13 Badness in as_remove_dispatched_request Rodolfo Boer
2003-10-03  8:33 ` Nick Piggin [this message]
2003-10-03  8:54 ` Rodolfo Boer
2003-10-03  8:57   ` Nick Piggin

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=3F7D343D.7000806@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=movez@gawab.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 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.