ide-io.c, ide_do_request -- race condition?
Quoted 7 lines · Bartlomiej Zolnierkiewicz
Quoted 4 lines · Max T. Woodbury
PIIXa: IDE controller at PCI slot 00:01.0
PIIXa: chipset revision 2
PIIXa: not 100% native mode: will probe irqs later
PIIXa: neither IDE port enabled (BIOS)
Quoted 6 lines
Do you have IDE ports disabled in BIOS?
This prevents piix IDE driver from working and instead you are using generic IDE driver which is much slower (no DMA!) and may be unsafe.
Bartlomiej
The Thinkpad 760 BIOS setup does not make this easy. It's this pretty GUI thingy with a humming bird for a cursor and practically no text anywhere. Very international. There's a more comprehensive control program under 'doz. I'll try to find something on the thinkpad lists... I don't remember seeing anything in the user docs on this.
Still, why would PIO mode be unsafe? (I can see slower, but I don't expect speed from this beast. Oh well. Thanks for the pointer.)
Hmm. Going to DMA would almost certainly make the symptoms disappear because the I/O timing would change and whatever was screwing up the I/O would happen at a non-critical point. Much like the fact that I could get the symptoms to disappear by by putting a computational load on the machine. It would NOT actually solve the underlying problem, whatever that problem really is.
Max
Quoted 2 lines · Max T. Woodbury
Still, why would PIO mode be unsafe? (I can see slower, but I don't expect speed from this beast. Oh well. Thanks for the pointer.)
PIO has no data integrity check, so bogus cables that glitch the data will not be detected. Not sure if that is what he was talking about, but is definitely a problem for PIO.
--eric
Signature · 2 lines
Eric D. Mudama [email protected]
Quoted 8 lines · Eric D. Mudama
Quoted 2 lines · Max T. Woodbury
Still, why would PIO mode be unsafe? (I can see slower, but I don't expect speed from this beast. Oh well. Thanks for the pointer.)
PIO has no data integrity check, so bogus cables that glitch the data will not be detected. Not sure if that is what he was talking about, but is definitely a problem for PIO.
Huh? Unless something major has changed since the last time I looked at DMA hardware (and it has been a few years), DMA uses the same transfer sequence from the devices point of view as PIO. The fact that the transfer is under the control of another device rather than a program should be transparent to the target device. Impedance mismatches, reflections and constructive and destructive interference caused by cable problems don't care about who's in control of the busses.
I can see a possible problem with cache consistency causing problems with PIO, but there are similar (abet in some sense inverted or reversed) problems with DMA.
max
Quoted 18 lines · Max T. Woodbury
Quoted 8 lines · Eric D. Mudama
Quoted 2 lines · Max T. Woodbury
Still, why would PIO mode be unsafe? (I can see slower, but I don't expect speed from this beast. Oh well. Thanks for the pointer.)
PIO has no data integrity check, so bogus cables that glitch the data will not be detected. Not sure if that is what he was talking about, but is definitely a problem for PIO.
Huh? Unless something major has changed since the last time I looked at DMA hardware (and it has been a few years), DMA uses the same transfer sequence from the devices point of view as PIO. The fact that the transfer is under the control of another device rather than a program should be transparent to the target device. Impedance mismatches, reflections and constructive and destructive interference caused by cable problems don't care about who's in control of the busses.
Quoted 3 lines
I can see a possible problem with cache consistency causing problems with PIO, but there are similar (abet in some sense inverted or reversed) problems with DMA.
Yes that's very clever of you. But read what Eric writes - PIO has no data integrity check. DMA transfers are crc'ed so you know if something goes bad between device and host in the data phase, with PIO you do not.
Signature · 1 line
Jens Axboe
Quoted 20 lines · Jens Axboe
Quoted 18 lines · Max T. Woodbury
Quoted 8 lines · Eric D. Mudama
Quoted 2 lines · Max T. Woodbury
Still, why would PIO mode be unsafe? (I can see slower, but I don't expect speed from this beast. Oh well. Thanks for the pointer.)
PIO has no data integrity check, so bogus cables that glitch the data will not be detected. Not sure if that is what he was talking about, but is definitely a problem for PIO.
Huh? Unless something major has changed since the last time I looked at DMA hardware (and it has been a few years), DMA uses the same transfer sequence from the devices point of view as PIO. The fact that the transfer is under the control of another device rather than a program should be transparent to the target device. Impedance mismatches, reflections and constructive and destructive interference caused by cable problems don't care about who's in control of the busses.
Quoted 7 lines
Quoted 3 lines
I can see a possible problem with cache consistency causing problems with PIO, but there are similar (abet in some sense inverted or reversed) problems with DMA.
Yes that's very clever of you. But read what Eric writes - PIO has no data integrity check. DMA transfers are crc'ed so you know if something goes bad between device and host in the data phase, with PIO you do not.
Sorry, NO. From the device point of view, DMA and PIO are indistinguishable. Both have CRCs on some busses and neither have CRCs on others. There are ALWAYS CRCs on transfers across the drive interface cables. This is controlled by the IDE/CPU interface chip and not by the DMA hardware. The transfer of the CRC is triggered by the termination of data transfer which happens with both DMA and PIO. These are design issues that go back at least thirty years and are generally well understood.
Bartlomiej was talking about timing register setup problems. They can be messed up for either mode. They are separate for DMA and PIO. His point was that the default driver left PIO timing setup to the hardware and BIOS while the special drivers sometimes included more specific initialization. These are fairly new problems arising from multi-tiered bus technologies like PCI.
max
Quoted 25 lines · Max T. Woodbury
Quoted 24 lines · Jens Axboe
Quoted 21 lines · Max T. Woodbury
Quoted 8 lines · Eric D. Mudama
Quoted 2 lines · Max T. Woodbury
Still, why would PIO mode be unsafe? (I can see slower, but I don't expect speed from this beast. Oh well. Thanks for the pointer.)
PIO has no data integrity check, so bogus cables that glitch the data will not be detected. Not sure if that is what he was talking about, but is definitely a problem for PIO.
Huh? Unless something major has changed since the last time I looked at DMA hardware (and it has been a few years), DMA uses the same transfer sequence from the devices point of view as PIO. The fact that the transfer is under the control of another device rather than a program should be transparent to the target device. Impedance mismatches, reflections and constructive and destructive interference caused by cable problems don't care about who's in control of the busses.
I can see a possible problem with cache consistency causing problems with PIO, but there are similar (abet in some sense inverted or reversed) problems with DMA.
Quoted 6 lines
Quoted 3 lines
Yes that's very clever of you. But read what Eric writes - PIO has no data integrity check. DMA transfers are crc'ed so you know if something goes bad between device and host in the data phase, with PIO you do not.
Sorry, NO. From the device point of view, DMA and PIO are indistinguishable.
That's nonsense. Even the commands are different.
Quoted 7 lines
Both have CRCs on some busses and neither have CRCs on others. There are ALWAYS CRCs on transfers across the drive interface cables. This is controlled by the IDE/CPU interface chip and not by the DMA hardware. The transfer of the CRC is triggered by the termination of data transfer which happens with both DMA and PIO. These are design issues that go back at least thirty years and are generally well understood.
So the icrc bit is where on the non-dma read commands? I repeat, if you are in pio mode, you will not notice crc differences in data transferred between host and device.
Signature · 1 line
Jens Axboe
Quoted 7 lines · Max T. Woodbury
Quoted 5 lines · Eric D. Mudama
Quoted 2 lines · Max T. Woodbury
Still, why would PIO mode be unsafe? (I can see slower, but I don't expect speed from this beast. Oh well. Thanks for the pointer.)
Quoted 8 lines
Quoted 3 lines
PIO has no data integrity check, so bogus cables that glitch the data will not be detected. Not sure if that is what he was talking about, but is definitely a problem for PIO.
Huh? Unless something major has changed since the last time I looked at DMA hardware (and it has been a few years), DMA uses the same transfer sequence from the devices point of view as PIO. The fact that the
Ultra DMA does CRC, PIO does not. Thus will cable glitches be detected.
Jeff
Quoted 9 lines
Huh? Unless something major has changed since the last time I looked at DMA hardware (and it has been a few years), DMA uses the same transfer sequence from the devices point of view as PIO. The fact that the transfer is under the control of another device rather than a program should be transparent to the target device. Impedance mismatches, reflections and constructive and destructive interference caused by cable problems don't care about who's in control of the busses.
Quoted 3 lines
I can see a possible problem with cache consistency causing problems with PIO, but there are similar (abet in some sense inverted or reversed) problems with DMA.
Actually, it's not the same transfer sequence (and it's not the same ATA commands neither). Look for an ATA spec and check out the signals on the wire, DMA is different at the device level as well.
In addition, U/DMA does CRC
Ben.