From: Andrew Morton <akpm@zip.com.au>
To: Richard Gooch <rgooch@ras.ucalgary.ca>
Cc: Jeff Dike <jdike@karaya.com>, bulb@ucw.cz, linux-kernel@vger.kernel.org
Subject: Re: 2.4.17 OOPS in tty code.
Date: Mon, 21 Jan 2002 15:08:03 -0800 [thread overview]
Message-ID: <3C4C9F53.D6949776@zip.com.au> (raw)
In-Reply-To: <200201212204.RAA03719@ccure.karaya.com>, <20020121151037.A21622@ucw.cz> <200201212204.RAA03719@ccure.karaya.com> <200201212247.g0LMlBU01766@vindaloo.ras.ucalgary.ca>
Richard Gooch wrote:
>
> Jeff Dike writes:
> > bulb@ucw.cz said:
> > > Tty device code causes oopses when closing /dev/console and devfs is
> > > used. The bug is reproducible on 2.4.17 UML port.
> >
> > How do you reproduce it?
> >
> > UML config, command line, a backtrace, etc would be nice.
>
> Furthermore, this was done without applying the latest devfs patch
> (v199.8 as I write this). Bug reports with old versions of devfs are
> (and should be) dropped in the bit-bucket, especially considering
> recent devfs patches have ChangeLog entries which talk about fixing
> Oopses!
>
Jan's report seems to have nothing to do with devfs. It
sounds like it's purely a tty-layer thing.
I'd like to see the full backtrace before we bitbucket
this one, please.
-
next prev parent reply other threads:[~2002-01-21 23:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 14:10 2.4.17 OOPS in tty code bulb
2002-01-21 22:04 ` Jeff Dike
2002-01-21 22:47 ` Richard Gooch
2002-01-21 23:08 ` Andrew Morton [this message]
2002-01-31 0:21 ` Jan Hudec
[not found] <009101c1a2cf$704da030$0801a8c0@Stev.org>
2002-01-24 13:18 ` Jan Hudec
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=3C4C9F53.D6949776@zip.com.au \
--to=akpm@zip.com.au \
--cc=bulb@ucw.cz \
--cc=jdike@karaya.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 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.