From: Martin Dalecki <dalecki@evision-ventures.com>
To: Sebastian Droege <sebastian.droege@gmx.de>
Cc: Jens Axboe <axboe@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IDE TCQ #4
Date: Wed, 17 Apr 2002 09:48:33 +0200 [thread overview]
Message-ID: <3CBD28D1.6070702@evision-ventures.com> (raw)
In-Reply-To: <20020415125606.GR12608@suse.de> <02db01c1e498$7180c170$58dc703f@bnscorp.com> <20020416102510.GI17043@suse.de> <20020416200051.7ae38411.sebastian.droege@gmx.de> <20020416180914.GR1097@suse.de> <20020416204329.4c71102f.sebastian.droege@gmx.de>
Sebastian Droege wrote:
> On Tue, 16 Apr 2002 20:09:14 +0200
> Jens Axboe <axboe@suse.de> wrote:
>
>
>>On Tue, Apr 16 2002, Sebastian Droege wrote:
>>
>>>Hi,
>>>just one short question:
>>>My hda supports TCQ but my hdb doesn't
>>>Is it safe to enable TCQ in kernel config?
>>
>>yes, should be safe.
>>
>>--
>>Jens Axboe
>>
>
> Ok it really works ;)
> But there's another problem in 2.5.8 with ide patches until 37 applied (they don't appear with 2.5.8 and ide patches until 35), the unexpected interrupts (look at the relevant dmesg output at the bottom). They appear with and without TCQ enabled.
> If you need more informations, just ask :)
They are not a problem. They are just diagnostics for us and will
go away at some point in time.
next prev parent reply other threads:[~2002-04-17 8:50 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-15 12:56 [PATCH] IDE TCQ #4 Jens Axboe
2002-04-15 12:24 ` Martin Dalecki
2002-04-15 13:33 ` Jens Axboe
2002-04-15 12:39 ` Martin Dalecki
2002-04-15 16:13 ` Aaron Tiensivu
2002-04-15 16:18 ` Jens Axboe
2002-04-15 16:44 ` Jens Axboe
2002-04-16 10:25 ` Jens Axboe
[not found] ` <20020416200051.7ae38411.sebastian.droege@gmx.de>
[not found] ` <20020416180914.GR1097@suse.de>
2002-04-16 18:43 ` Sebastian Droege
2002-04-17 7:48 ` Martin Dalecki [this message]
2002-04-17 11:28 ` Sebastian Droege
2002-04-17 10:32 ` Martin Dalecki
2002-04-17 11:40 ` Sebastian Droege
2002-04-17 10:42 ` Martin Dalecki
2002-04-18 12:17 ` Sebastian Droege
2002-04-18 11:20 ` Martin Dalecki
2002-04-18 12:26 ` Sebastian Droege
2002-04-18 12:57 ` Jens Axboe
2002-04-18 12:57 ` Jens Axboe
2002-04-18 11:59 ` Martin Dalecki
2002-04-18 13:07 ` Jens Axboe
2002-04-18 12:08 ` Martin Dalecki
2002-04-18 13:12 ` Jens Axboe
2002-04-18 12:16 ` Martin Dalecki
2002-04-18 13:26 ` Jens Axboe
2002-04-18 12:40 ` Martin Dalecki
2002-04-18 12:45 ` Martin Dalecki
2002-04-18 14:17 ` Alan Cox
2002-04-18 13:01 ` Jens Axboe
2002-04-17 7:32 ` Helge Hafting
2002-04-17 13:01 ` Dave Jones
2002-04-17 13:05 ` Jens Axboe
2002-04-30 19:58 ` Martin Schewe
-- strict thread matches above, loose matches on Subject: below --
2002-04-15 18:41 Petr Vandrovec
2002-04-15 18:26 ` Jens Axboe
2002-04-16 5:11 ` Martin Dalecki
2002-04-15 19:11 Petr Vandrovec
2002-04-15 19:28 Petr Vandrovec
2002-04-16 10:25 ` Jens Axboe
2002-04-16 11:01 ` Martin Dalecki
2002-04-16 12:28 ` Jens Axboe
2002-04-16 11:44 ` Martin Dalecki
2002-04-15 19:29 Petr Vandrovec
2002-04-15 19:00 ` Jens Axboe
2002-04-18 22:05 Andries.Brouwer
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=3CBD28D1.6070702@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=axboe@suse.de \
--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