From: Nick Piggin <piggin@cyberone.com.au>
To: Thomas Schlichter <schlicht@uni-mannheim.de>
Cc: Ivan Gyurdiev <ivg2@cornell.edu>, Andrew Morton <akpm@osdl.org>,
B.Zolnierkiewicz@elka.pw.edu.pl, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: Processes receive SIGSEGV if TCQ is enabled
Date: Fri, 31 Oct 2003 18:37:31 +1100 [thread overview]
Message-ID: <3FA2113B.1020102@cyberone.com.au> (raw)
In-Reply-To: <200310310828.41598.schlicht@uni-mannheim.de>
Thomas Schlichter wrote:
>Hi,
>
>On Friday 31 October 2003 00:40, Nick Piggin wrote:
>
>>Hi,
>>If you're testing IDE TCQ, please try the following patch and use the
>>default io scheduler. It won't fix anything, but it poisons requests
>>so we can sometimes tell if they are being used in the wrong places.
>>I have seen warnings that lead me to believe this might be happening.
>>Its against 2.6.0-test9-mm1. Report any stack traces you see. Thanks.
>>
>
>OK, I tested 2.6.0-test9-mm1 + your patch, but it seems not to print any
>messages or stack traces, even if many processes are killed after setting TCQ
>depth to 1.
>
OK well thats good, its not my problem then ;) Thanks.
prev parent reply other threads:[~2003-10-31 7:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 15:01 Processes receive SIGSEGV if TCQ is enabled Thomas Schlichter
2003-10-30 17:48 ` Bartlomiej Zolnierkiewicz
2003-10-31 13:00 ` Jens Axboe
2003-10-31 13:11 ` Thomas Schlichter
2003-10-31 14:44 ` Ivan Gyurdiev
2003-10-30 21:33 ` Andrew Morton
2003-10-30 22:10 ` Thomas Schlichter
2003-10-30 22:44 ` Ivan Gyurdiev
2003-10-30 23:40 ` Nick Piggin
2003-10-31 7:28 ` Thomas Schlichter
2003-10-31 7:37 ` Nick Piggin [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=3FA2113B.1020102@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=akpm@osdl.org \
--cc=ivg2@cornell.edu \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schlicht@uni-mannheim.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 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.