Messages in this thread |  | | Date | Wed, 12 Feb 1997 23:48:56 +0000 (GMT) | From | Philip Blundell <> | Subject | Re: 2.0.27 major problems #1 -- 3c59x driver. |
| |
On Wed, 12 Feb 1997, Chris Evans wrote:
> > On Wed, 12 Feb 1997, Philip Blundell wrote: > > > > Just cut and paste into the same area when the "access conflict" occurs. > > > The idea is that when the controller refuses to work, reinitialize it. > > > > A transmitter access conflict is not disaster. There is no need to > > reinitialise the controller - all it means is that the driver's > > transmit routine was reentered, and the second transmit was deferred to > > avoid contention. > > I am forced to disagree -- when your card hangs it certainly _is_ a > disaster. Additionally, the code implies that that if execution reaches > this stage it is a disaster anyway; quote "if this ever happens then the > queue layer is doing something evil"
A transmitter access conflict will _not_ cause your card to hang. If you see that message then it means a problem has just been avoided.
I suspect there is some other cause. I also think the comment about the queue layer is incorrect - that mutex does come under contention under high load.
phil
|  |