From: "Richard B. Johnson" <root@chaos.analogic.com>
To: John Bradford <john@grabjohn.com>
Cc: "Måns Rullgård" <mru@kth.se>, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: floppy motor spins when floppy module not installed
Date: Fri, 12 Dec 2003 14:47:34 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.53.0312121435570.1356@chaos> (raw)
In-Reply-To: <200312121928.hBCJSLBs000384@81-2-122-30.bradfords.org.uk>
On Fri, 12 Dec 2003, John Bradford wrote:
> Quote from "Richard B. Johnson" <root@chaos.analogic.com>:
> > On Fri, 12 Dec 2003, [iso-8859-1] M=E5ns Rullg=E5rd wrote:
> >
> > > Dale Mellor <dale@dmellor.dabsol.co.uk> writes:
> > >
> > > > 1. Floppy motor spins when floppy module not installed.
> > >
> > > It's a known problem. Some broken BIOSes don't turn off the motor
> > > after probing for a disk. One solution is to change the boot priorit=
> > y
> > > in the BIOS settings so the hard disk is tried before floppy. If you
> > > ever need to boot from a floppy, you can change it back.
> > >
> > > --
> > > M=E5ns Rullg=E5rd
> > > mru@kth.se
> >
> > It is not a broken BIOS! The BIOS timer that ticks 18.206 times
> > per second has an ISR that, in addition to keeping time, turns
> > OFF the FDC motor after two seconds of inactivity. This ISR is taken
> > away by Linux. Therefore Linux must turn off that motor! It is a
> > Linux bug, not a BIOS bug. Linux took control away from the BIOS
> > during boot.
>
> We discussed almost exactly the same problem at length on LKML just
> two months ago:
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=106545766213063&w=2
>
> John.
Yes, and I recall we agreed to disagree where the FDC stop must
be put, but we both agreed that it must be stopped. I still contend
that since the Linux startup code takes control away from the BIOS,
it's that codes responsibility to turn OFF things that the BIOS
might have left ON.
Funny thing. It's so trivial, anybody/everybody could turn the
floppy motor off, but all the fingers point to somebody else's
code.
It's a bug in Linux, not in a boot-loader. That bug was covered up
until the FDC code got modularized. Once we were able to compile
a kernel without the FDC, the bug was exposed. So, I suggest that
we just fix the bug and be done with it. It's not a performance
problem, the write to the port occurs exactly once during the nest
999 days of up-time. It's just an attempt to make a mountain out
of a mole-hill.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2003-12-12 19:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-12 13:57 Dale Mellor
2003-12-12 14:18 ` Måns Rullgård
2003-12-12 15:04 ` Richard B. Johnson
2003-12-12 15:11 ` Måns Rullgård
2003-12-12 15:20 ` Richard B. Johnson
2003-12-12 15:33 ` Måns Rullgård
2003-12-12 16:05 ` Petr Vandrovec
2003-12-12 16:27 ` Måns Rullgård
2003-12-12 16:41 ` Petr Vandrovec
2003-12-12 16:00 ` Matthew Kirkwood
2003-12-12 19:28 ` John Bradford
2003-12-12 19:47 ` Richard B. Johnson [this message]
2003-12-13 6:18 ` Joshua Schmidlkofer
2003-12-15 14:37 ` Richard B. Johnson
2003-12-13 10:40 ` John Bradford
2003-12-15 14:50 ` Richard B. Johnson
2003-12-15 20:24 ` John Bradford
2003-12-13 13:18 ` Helge Hafting
2003-12-13 16:42 ` Joshua Schmidlkofer
2003-12-12 14:59 ` Richard B. Johnson
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.53.0312121435570.1356@chaos \
--to=root@chaos.analogic.com \
--cc=john@grabjohn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mru@kth.se \
/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®