Processor Upgrades And SCSI Woes 11
"I'm generally willing to tolerate the occasional crash, as they are rare. But CPU-intensive applications (Cyberlink PowerDVD and Quake 3 under Windows, recompiling apps and encoding MP3s under Linux) cause no trouble whatsoever.
Unfortunately, there are two cases where my system will hang with 100% certainty - fsck dies before completing 10% of my drive, and cdparanoia will always hang the system. If I drop the clock rate down to 400 MHz, everything works fine.
Any idea what's up with this? The correlation between SCSI use and crashes makes no sense to me, but it's most definitely there.
My setup includes: Epox MVP3E-M mobo with latest BIOS (VIA MVP3 chipset), Mylex/BusLogic FlashPoint LW SCSI controller also with latest BIOS, and the aforementioned AMD processor. (BTW, bus speed isn't an issue since both the old and new processors were running at 100MHz FSB.)"
Problem fixed. (No thanks to A.S.) (Score:2)
Fixed the problem about 3 days after I submitted my question. I found out that some people on linux-kernel had similar problems, the FlashPoint driver has some timing problems. I got a patch from one of the l-k guys, works like a charm.
It hasn't been integrated to the kernel tree, as they're still figuring out how to implement it without reducing performance for those who dont' have the problem.
disconnect set? (Score:1)
I had a similar problem when I put a new SCSI disk on my system - CPU intensive:fine, Disk intensive: hang. It turned out that disconnect was disabled by default for some devices (maybe DOS liked it that way??)
I think Linux expects to be able to do disconnect.
Power supply (Score:2)
Coincidence (Score:2)
Now I'm wondering if it's worth the trouble - if it crashes Linux then Win98 doesn't stand a chance.
I'd surely appreciate it if you could post more details about your hardware configuration. You should include everything - the tech specs from the RAM's datasheet, your PSU's power rating, the precise markings on your CPU, the make model and revision of your motherboard etc. etc.
Consciousness is not what it thinks it is
Thought exists only as an abstraction
CPU voltage? (Score:1)
I highly doubt your scsi chain has anything to do with the problem, since it works at 300 and 400 MHz. (I'm assuming you're keeping the PCI bus pegged at 33 MHz, if not, that may very well be your problem)
Check Low Level Settings (Score:1)
Ram (Score:1)
Motherboard problem? (Score:1)
Anyway, after replacing both CPUs, the SCSI card, and the motherboard twice he finally got a completely new motherboard. It worked(and still does) beautifully.
Moral of the story: when you get wacky errors, check the motherboard.
Active termination (Score:2)
If your drive doesn't support it, you can buy a physical terminator for the chain for maybe $50 at any good computer store.
Install the VIA PCI Bridge Patch (Score:1)
Stupid Stuf?? (Score:1)