From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Thomas Schlichter <schlicht@uni-mannheim.de>
Cc: 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: Thu, 30 Oct 2003 17:44:10 -0500 [thread overview]
Message-ID: <3FA1943A.7010300@cornell.edu> (raw)
In-Reply-To: <200310302310.53798.schlicht@uni-mannheim.de>
Hi, perhaps this might also be relevant:
http://www.ussg.iu.edu/hypermail/linux/kernel/0307.2/1655.html
Have those issues here been finally addressed?
I haven't been following development much lately, but I wanted to ask,
since at the moment I have no confidence in TCQ. I know #1 has been
fixed. Have there been any major TCQ changes that I need to retest for?
The only thing I see is this:
ChangeSet@1.1153.141.3, 2003-09-05 07:15:37-07:00,
B.Zolnierkiewicz@elka.pw.edu.pl
[PATCH] ide: fix ide_cs oops with TCQ
Thomas Schlichter wrote:
> Hello again...
>
> On Thursday 30 October 2003 22:33, Andrew Morton wrote:
>
>>Thomas Schlichter <schlicht@uni-mannheim.de> wrote:
>>
>>> today I tried to test TCQ with the linux-2.6.0-test9-mm1 kernel. The
>>>config.gz is attached. But after enabling TCQ with 'hdparm -Q1 /dev/hda'
>>>newly started processes die due to a received SIGSEGV. No bad kernel
>>>messages appear...
next prev parent reply other threads:[~2003-10-30 22:38 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 [this message]
2003-10-30 23:40 ` Nick Piggin
2003-10-31 7:28 ` Thomas Schlichter
2003-10-31 7:37 ` 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=3FA1943A.7010300@cornell.edu \
--to=ivg2@cornell.edu \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=akpm@osdl.org \
--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.