Messages in this thread | | | Date | Sat, 7 Nov 1998 13:29:24 +1100 | From | Richard Gooch <> | Subject | Re: timeouts with ncr53c8xx |
| |
Gerard Roudier writes: > > On Thu, 5 Nov 1998, Richard Gooch wrote: > > > Hans-Frieder Vogt writes: > > > from kernel 2.1.127-pre3 (the first I tried) on I get loads of "aborting command > > > due to timeout" messages short after switching to synchronous mode FAST-10. > > > Were the timings changed in new version 3.1a? Last tried was 2.1.127-pre7. > > > Problem still there. > > > hw is P100 single processor, NCR53C810 on noname card. > > > compiler was gcc 2.8.1 (also tested with egcs-1.1b). > > > > Yeah, I'm getting much the same behaviour. > > It should be interesting to have results using driver 3.0i and 3.1a on the > same kernel version and configuration, for example: > > - linux-2.1.126 that has driver 3.0i > - linux-2.1.126 patched for driver 3.1a > > Patch location: > ftp://ftp.tux.org/pub/roudier/ncr53c8xx-3.0i-to-3.1a-for-linux-2.1.125.patch.gz > > And you may want to also compile the kernel using gcc-2.7.x if driver 3.1a > has the timeout problem. If booting with tags disabled, asynchronous > transfers, etc..., makes difference, this may also help find the cause > of the problem.
I've tried plain 2.1.127-pre7 (which has NCR 3.1a) and that fails. I then tried 2.1.127-pre7 with the 3.0i driver (from 2.1.127-pre1) and that works fine. So the problem looks like being with v3.1a of the NCR driver.
I use gcc 2.7.2.1, always.
BTW: this isn't meant as a flame, but was NCR 3.1a tested before going into the kernel?
Regards,
Richard....
- 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.tux.org/lkml/
| |