From: Linus Torvalds <torvalds@osdl.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: "Antonino A. Daplas" <adaplas@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Jens Axboe <axboe@suse.de>
Subject: Re: 2.6.15-$SHA1: VT <-> X sometimes odd
Date: Thu, 12 Jan 2006 11:23:54 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0601121119100.3535@g5.osdl.org> (raw)
In-Reply-To: <20060112192856.GA7938@mipter.zuzino.mipt.ru>
On Thu, 12 Jan 2006, Alexey Dobriyan wrote:
>
> Now it's vim saving 5k proggie while X tarball was unpacking on reiserfs.
> :wq and vim freezes. Switching to another virtual "desktops" works and
> everything in general works except vim. But switching to VT and back
> sends system to hell.
This may be fixed by the current -git tree:
commit 1bc691d3, Tejun Heo <htejun@gmail.com>:
[PATCH] fix queue stalling while barrier sequencing
or if that isn't it, and you have an IDE drive, can you try if the
appended trivial patch makes a difference?
Linus
---
diff --git a/drivers/ide/ide-io.c b/drivers/ide/ide-io.c
index bcbaeb5..d726167 100644
--- a/drivers/ide/ide-io.c
+++ b/drivers/ide/ide-io.c
@@ -101,7 +101,7 @@ int __ide_end_request(ide_drive_t *drive
* for those
*/
nbytes = nr_sectors << 9;
- if (!rq->errors && rq_all_done(rq, nbytes)) {
+ if (0 && !rq->errors && rq_all_done(rq, nbytes)) {
rq->data_len = nbytes;
blkdev_dequeue_request(rq);
HWGROUP(drive)->rq = NULL;
next prev parent reply other threads:[~2006-01-12 19:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 16:23 2.6.15-$SHA1: VT <-> X sometimes odd Alexey Dobriyan
2006-01-11 11:50 ` Antonino A. Daplas
2006-01-11 15:38 ` Alexey Dobriyan
2006-01-12 19:28 ` Alexey Dobriyan
2006-01-12 19:23 ` Linus Torvalds [this message]
2006-01-12 20:04 ` Linus Torvalds
2006-01-12 20:08 ` Jens Axboe
2006-01-12 20:23 ` Lockups while unpacking huge tarballs (was Re: 2.6.15-$SHA1: VT <-> X sometimes odd) Alexey Dobriyan
2006-01-12 20:14 ` Jens Axboe
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=Pine.LNX.4.64.0601121119100.3535@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=adaplas@gmail.com \
--cc=adobriyan@gmail.com \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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).