public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <andrewm@uow.edu.au>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Steve Kieu <haiquy@yahoo.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.4.5-ac2 OOPs when run pppd ?
Date: Tue, 29 May 2001 11:12:01 +1000	[thread overview]
Message-ID: <3B12F761.FE676BEF@uow.edu.au> (raw)
In-Reply-To: <3B125E62.1DD4712E@uow.edu.au>, <20010528084855.10604.qmail@web10402.mail.yahoo.com> <E154NQp-000386-00@the-village.bc.nu> <3B125E62.1DD4712E@uow.edu.au> <200105281821.f4SIL5000350@mobilix.atnf.CSIRO.AU>

Richard Gooch wrote:
> 
> How about having a helper function for interrupt handlers which queues
> characters to be sent to the console? kconsoled anyone? Blocking
> interrupts is quite distressing, so we need to be consoled ;-)

I don't think we need it, Richard.  These writes to tty
devices from interrupt context are coming from line
disciplines - n_hdlc, ppp, r3964, etc.

Now, while it may be amusing to see if you can successfully
negotiate a PPP session by typing raw LCP, there really isn't,
I believe, a useful reason for attaching one of these ldiscs
to the console tty.

Interrupt-context writes to the *console*, as opposed to
the console *tty* work just fine, of course.  printk.

      reply	other threads:[~2001-05-29  1:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-28  8:48 Kernel 2.4.5-ac2 OOPs when run pppd ? Steve Kieu
2001-05-28 13:51 ` Alan Cox
2001-05-28 14:19   ` Andrew Morton
2001-05-28 18:21     ` Richard Gooch
2001-05-29  1:12       ` Andrew Morton [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=3B12F761.FE676BEF@uow.edu.au \
    --to=andrewm@uow.edu.au \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=haiquy@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgooch@ras.ucalgary.ca \
    /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