I am having terrible problems with the 3.0 series of drivers on an Alpha
UDB. They work perfectly under Intel Linux (I have C810a-based adapters
in two different boxes - one an SMP), so I'm wondering if this is a fluke
in the UDB hardware.
It boots in 2.1.117, but blows up fairly quickly with an endless cascade
of time-outs on /dev/sdb. Eventually, it tries a reset, pauses, and just
continues spitting out the same messages. This continues until
power-down.
There is nothing whatever wrong with the drive. It is a Maxtor MXT540S
which works perfectly under version 2.5f (and earlier) of your driver.
With the older driver, I configured it for:
Max Tags = 8
Tagged Queueing = Enabled
Sync = 10 (Mhz.)
(all else default)
I tried this on the new driver, adding:
Default Queue = 8
but it made no difference. I also tried booting with:
ncr53c8xx="tags:8/q8 sync:10"
but no luck with that either.
Finally, I rebuilt 2.1.117 with the 2.5f driver and it again works fine.
I'd like to help you chase this down, but there are a dizzying number of
options with the new driver and I don't know where to even start.
Any suggestions?
Steve
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html