On Thu, 6 Feb 2003 [EMAIL PROTECTED] wrote:
> I looked at the code of if_ep.c and I see that the continue is indeed
> not there.
AFAIK it needs to be there; at least it solves the hangs I see here.
Dw
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the bo
Dear All,
>
> : --- if_ep.c Fri Feb 1 19:51:43 2002
> : +++ if_ep.c.fix Sat Feb 9 12:49:31 2002
> : @@ -571,7 +571,6 @@
> :
> : if (status & (S_RX_COMPLETE | S_RX_EARLY)) {
> : epread(sc);
> : - continue;
> : }
> : if (status & S_TX_AVAIL) {
>
In message: <[EMAIL PROTECTED]>
Jonathan Hanna <[EMAIL PROTECTED]> writes:
:
: This looks like the bug in the "ep" driver. When the interrupt routine
: gets both TX and RX interrupts it acknowledges both but only services
: the read. Karl Dietz, <[EMAIL PROTECTED]> is working on an ov
In message: <[EMAIL PROTECTED]>
Jonathan Hanna <[EMAIL PROTECTED]> writes:
: From my look at the driver the issues I know of are the interrupt
: problem as above and a lack of splx(x) if sc->gone in
: ep_intr(). From Karl: possible impending merge with the "vx" driver.
That's right.
User Seva wrote:
> I commented out "continue" in if_ep.c.
> There is no any "No buffer space available" any more.
If you are missing it, then you can set up a PPP connection,
and then unplug your modem and start a "ping".
(it's still a routing problem).
-- Terry
To Unsubscribe: send mail to [E
On 11-Feb-02 M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Mike Silbersack <[EMAIL PROTECTED]> writes:
>:
>: On Sat, 9 Feb 2002, Jonathan Hanna wrote:
>:
>: >
>: > This looks like the bug in the "ep" driver. When the interrupt routine
>: > gets both TX and RX interrupts
In message: <[EMAIL PROTECTED]>
Mike Silbersack <[EMAIL PROTECTED]> writes:
: Ah, good. I wasn't sure that any committers still used those cards.
You'd be surprised how many cards I have...
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in
On Sun, 10 Feb 2002, M. Warner Losh wrote:
> : If this fix is solid, should it be applied now to the ep driver? Should
> : we wait until the driver merge is complete? I don't own any cards that
> : use the ep chipset, but if that change fixes bugs for multiple ep users I
> : wouldn't be oppose
In message: <[EMAIL PROTECTED]>
Mike Silbersack <[EMAIL PROTECTED]> writes:
:
: On Sat, 9 Feb 2002, Jonathan Hanna wrote:
:
: >
: > This looks like the bug in the "ep" driver. When the interrupt routine
: > gets both TX and RX interrupts it acknowledges both but only services
: > the
On Sat, 9 Feb 2002, Jonathan Hanna wrote:
>
> This looks like the bug in the "ep" driver. When the interrupt routine
> gets both TX and RX interrupts it acknowledges both but only services
> the read. Karl Dietz, <[EMAIL PROTECTED]> is working on an overhaul
> but my quick fix is to take out the
Thanks!
I commented out "continue" in if_ep.c.
There is no any "No buffer space available" any more.
Seva.
Jonathan Hanna <[EMAIL PROTECTED]> writes:
> This looks like the bug in the "ep" driver. When the interrupt routine
> gets both TX and RX interrupts it acknowledges both but only servic
This looks like the bug in the "ep" driver. When the interrupt routine
gets both TX and RX interrupts it acknowledges both but only services
the read. Karl Dietz, <[EMAIL PROTECTED]> is working on an overhaul
but my quick fix is to take out the "continue" after the "epread()" in
ep_intr(). The bu
Try increasing your maxsockbuf:
kern.ipc.maxsockbuf: 262144
is the default setting, try:
sysctl -w kern.ipc.maxsockbuf=384000 [or higher, depending on your RAM and
your network usage]
There are a bunch of other network buffers you might want to tune as I am
sure others will mention.
Deepak J
13 matches
Mail list logo
