From: Bill Davidsen <davidsen@tmr.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Rene Herman <rene.herman@gmail.com>,
Oleg Nesterov <oleg@tv-sign.ru>,
Stephane Eranian <eranian@hpl.hp.com>,
linux-kernel@vger.kernel.org
Subject: Re: bug in kernel 2.6.21-rc1-git1: conventional floppy drive cannot be mounted without hanging up the whole system
Date: Tue, 27 Feb 2007 21:42:16 -0500 [thread overview]
Message-ID: <45E4EC08.50409@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0702261308490.12485@woody.linux-foundation.org>
Linus Torvalds wrote:
>
> On Mon, 26 Feb 2007, Rene Herman wrote:
>> Other than these two, ECP parallel ports are the other remaining users.
>> Now, even though on a machine that still has a parallel port it might usually
>> indeed be set to ECP in its BIOS; having anything attached to the port also
>> use it as such seems quite seldom.
>
> Well, if it's some kind of cache coherency problem (the same way much more
> modern CPU's have cache coherency issues with DMA during C3 sleep), then
> it's entirely possible that the normal ECP parallel port behaviour would
> never show it, since most people tend to use it for output only (yeah, I
> realize you can use it bidirectionally, but at least on old hardware it
> tends to be "talk AT printer" rather than "talk WITH printer".
The bidirectional use is/was PL/IP, aka "laplink" connections. Yes, I
still have a machine I installed that way, and it will run 2.2.19
forever before I try it again. ;-)
>
> I frankly forget what hardware platforms had problems with the DMA thing,
> and what the exact behaviour even was (I think there was some possibility
> of corrupt data on the floppy). We also used to have the "nohlt" flag to
> turn off hlt entirely, and that was due to some other legacy issues, iirc.
>
> I seriously doubt we will ever see anybody who has this problem ever
> again, but on the other hand, I also seriously doubt that most modern
> machines even *have* a floppy drive any more, so I'd rather not even
> change it. It's just not worth even a miniscule risk..
Thank you.
>
> Linus
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2007-02-28 2:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 18:06 bug in kernel 2.6.21-rc1-git1: conventional floppy drive cannot be mounted without hanging up the whole system Oleg Nesterov
2007-02-26 18:13 ` Linus Torvalds
2007-02-26 20:55 ` Rene Herman
2007-02-26 21:14 ` Linus Torvalds
2007-02-28 2:42 ` Bill Davidsen [this message]
2007-02-28 13:04 ` Alan
2007-02-28 12:20 ` Rene Herman
-- strict thread matches above, loose matches on Subject: below --
2007-02-25 18:29 Uwe Bugla
2007-02-25 21:04 ` Alexey Dobriyan
2007-02-26 3:55 ` Mike Galbraith
2007-02-24 17:54 Uwe Bugla
2007-02-24 18:07 ` Andrew Morton
2007-02-24 18:29 ` Uwe Bugla
2007-02-24 19:23 ` Uwe Bugla
2007-02-24 19:49 ` Ray Lee
2007-02-26 10:38 ` Jiri Slaby
2007-02-26 15:12 ` Jiri Slaby
2007-02-26 15:51 ` Linus Torvalds
2007-02-26 16:28 ` Jiri Slaby
2007-02-26 16:34 ` Benjamin LaHaise
2007-02-26 17:10 ` Linus Torvalds
2007-02-26 17:45 ` Stephane Eranian
2007-02-26 17:28 ` Stephane Eranian
2007-02-26 17:37 ` Linus Torvalds
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=45E4EC08.50409@tmr.com \
--to=davidsen@tmr.com \
--cc=eranian@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=rene.herman@gmail.com \
--cc=torvalds@linux-foundation.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