Skip to contentSkip to conversation

bug in kernel 2.6.21-rc1-git1: conventional floppy drive cannot be mounted without hanging up the whole system

DISCUSSION Oleg Nesterov 5 participants 7 messages Feb 26, 2007 – Feb 28, 2007

lore
Share & tools
lore
#0 lore raw
Quoted 6 lines · Stephane Eranian
Quoted 4 lines · Linus Torvalds

It is in fact possible that the floppy failure might just be from some timing-dependent thing, and the slowdown itself is the problem.

Quoted 6 lines
Quoted 4 lines

Although I do find that a bit unlikely, since machines these days are about a million times faster than they used to be, so even if it's unnecessarily slow, it shouldn't be noticeable for a floppy drive.

I don't know enough about the floppy driver to comment on this but I would agree with you here.

I know nothing about floppy, but I guess the reason is floppy_disable_hlt().

Sorry for the offtopic question, is it really needed? According to grep, floppy is the only one user of disable_hlt().

Oleg.

#1 lore raw
Quoted 5 lines · Oleg Nesterov

I know nothing about floppy, but I guess the reason is floppy_disable_hlt().

Sorry for the offtopic question, is it really needed? According to grep, floppy is the only one user of disable_hlt().

I suspect you'd have a hard time finding a machine where it was broken any more.

But it used to be that the native (aka "braindamaged and idiotic") DMA by the motherboard southbridge chipset (and apparently _only_ that) had problems with the CPU being halted on some motherboards, and would corrupt data if the CPU was halted while the DMA took place.

We never bothered to even figure out why it happened, though. It was undeniable that there were people who had trouble with "hlt" and the floppy driver, but it is not clear what the cause was.

That's a _loong_ time ago, though, and it *probably* hasn't been an issue on any recent machine. People just don't care enough to test, especially since the upside is negligible, and the downside for when it would trigger is huge.

The floppy is still pretty much the only user of native motherboard (aka i8237) DMA'ing for most people. Some old ISA sound-cards may do it, of course. But any PCI device will do its own DMA rather than rely on the broken 8237 DMA engine, so for all I know, the bug - whatever it ever ended up being - could still be there.

Linus

#2 lore raw
Quoted 3 lines · Linus Torvalds

The floppy is still pretty much the only user of native motherboard (aka i8237) DMA'ing for most people. Some old ISA sound-cards may do it, of course.

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.

Rene.

#3 lore raw
Quoted 5 lines · Rene Herman

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".

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..

Linus

#4 lore raw
Quoted 8 lines · Linus Torvalds
Quoted 4 lines · Rene Herman

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. ;-)

Quoted 4 lines

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.

Quoted 2 lines

Linus

Signature · 3 lines
Bill Davidsen <[email protected]>
  "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot
#5 lore raw
Quoted 3 lines

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. ;-)

PLIP/Laplink runs bidirectional on ordinary parallel ports. The bidirectional part of parallel ports in "normal" modes is still used for things like PnP detection of printer and drivers.

#6 lore raw
Quoted 2 lines · Alan

PLIP/Laplink runs bidirectional on ordinary parallel ports. The bidirectional part of parallel ports in "normal" modes is still used for things like PnP detection of printer and drivers.

And my parallel port Iomega ZIP drive, it seems. I actually checked earlier and although it doesn't use DMA (it says it's using "EPP 32-bit") it does use bidrectional communication; it's an sd device.

I admit most of those will be confined to history as well with respect to actual use (they existed with 100MB, 250 and 750MB disks, although the 750 one probably not as parallel) but they looked cool, so people haven't just thrown them away yet :)

Rene