From: Jens Axboe <axboe@suse.de>
To: Sebastian Droege <sebastian.droege@gmx.de>
Cc: dalecki@evision-ventures.com, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] IDE TCQ #2
Date: Fri, 3 May 2002 22:56:35 +0200 [thread overview]
Message-ID: <aautqf$kvd$2@main.gmane.org> (raw)
In-Reply-To: <20020503193006.6b4b9094.sebastian.droege@gmx.de>
On Fri, May 03 2002, Sebastian Droege wrote:
> On Fri, 3 May 2002 19:01:18 +0200
> Jens Axboe <axboe@suse.de> wrote:
>
> > > > > ide_tcq_intr_timeout: timeout waiting for interrupt...
> > > > > ide_tcq_intr_timeout: hwgroup not busy
> > > >
> > > > We timed out waiting for an interrupt for service or dma completion.
> > > > Damn, I forgot to print which one. Please change that printk in
> > > > drivers/ide/ide-tcq.c:ide_tcq_intr_timeout() to:
> > > >
> > > > printk("ide_tcq_intr_timeout: timeout waiting for %s interrupt...\n",
> > > > hwgroup->rq ? "completion" : "service");
> > > >
> > > > and reproduce!
> > > Is this printk enough or should I handcopy the oops again? ;)
> >
> > The oops is pretty irrelevant here, the fact that it triggers is enough
> > to know. I already know the backtrace :-)
>
> It's a service interrupt....
Ok thanks, what were the other messages this time? Just the ones before
the oops.
Jens
prev parent reply other threads:[~2002-05-03 20:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-03 11:06 [PATCH] IDE TCQ #2 Jens Axboe
2002-05-03 14:32 ` Sebastian Droege
[not found] ` <20020503163248.633c8358.sebastian.droege@gmx.de>
2002-05-03 16:45 ` Jens Axboe
2002-05-03 16:57 ` Sebastian Droege
[not found] ` <20020503185744.7f4e192f.sebastian.droege@gmx.de>
2002-05-03 17:01 ` Jens Axboe
[not found] ` <20020503170118.GV839@suse.de>
2002-05-03 17:30 ` Sebastian Droege
2002-05-03 18:36 ` Sebastian Droege
2002-05-03 20:56 ` Jens Axboe [this message]
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='aautqf$kvd$2@main.gmane.org' \
--to=axboe@suse.de \
--cc=dalecki@evision-ventures.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian.droege@gmx.de \
/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;
as well as URLs for NNTP newsgroup(s).