mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: linux-kernel@vger.kernel.org
Cc: torvalds@transmeta.com
Subject: 2.4.0-test13-pre1 lockup: run_task_queue or tty_io are wrong
Date: Sun, 17 Dec 2000 03:49:28 +0100	[thread overview]
Message-ID: <20001217034928.A410@ppc.vc.cvut.cz> (raw)

Hi,
  my 2.4.0-test13-pre1 just stopped answering to my keystrokes.
I've found that it is looping in tqueue_bh and flush_to_ldisc
still again and again.

  To my surprise I found that flush_to_ldisc() does

if (test_bit(TTY_DONT_FLIP, &tty_flags)) {
   queue_task(&tty->filp.tqueue, &tq_timer);
   return;
}

Looks ok. But only until you'll look at run_task_queue().
It now contains

  while (!list_empty(list)) {
      ...
  }

So postponing event to next timer tick does not work anymore.
It will stop cycling in run_task_queue and machine is dead
(unless you have some spare CPU).

Is current run_task_queue() behavior intentional, or is it
only bug introduced by changing task queue to list based
implementation?
					Thanks,
						Petr Vandrovec
						vandrove@vc.cvut.cz

P.S.: Yes, I know that I should bought faster computer so that
ldisc buffer does not overflow, but...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2000-12-17  3:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-17  2:49 Petr Vandrovec [this message]
2000-12-17  3:09 ` Linus Torvalds
2000-12-17  3:49   ` Petr Vandrovec
2000-12-17  7:25   ` Andrew Morton
2000-12-17 18:23   ` Jamie Lokier
2000-12-17 20:02     ` Linus Torvalds
2000-12-17 21:05       ` Jeff V. Merkey
2000-12-17 20:23         ` Linus Torvalds
2000-12-18 20:51       ` Jamie Lokier
2000-12-18 23:58         ` Linus Torvalds
2000-12-19  1:32           ` Jamie Lokier

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=20001217034928.A410@ppc.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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

all inboxes | Powered by JetHome®