RE: [SQU] Select Loop Failed

I had a similar problem, using RealTek RTL8139 Based cards... we had the
card dropping very regually, but have found the latest linux drivers have
fixed most of the problems.. i think it was mainly an issue with POP3
crashing the card...

Andrew Lowe
andrew@pccentre.com.au
        The South Coast Professional Computing Centre
                + Hislora Website Hosting & Design
                + Daly & Daly Computer Training
                + Flatearth Internet Cafe
        Ph: 02 4423 7771
        Fax: 02 4423 7772
        email: sales@pccentre.com.au

On Wed, 13 Sep 2000, Nightingale, Don wrote:

> I had this problem with one machine. I ran a script to bandaid it until a
> new card arrived:
>
> #!/bin/sh
> ifconfig eth1 down
> ping -c 1 some.address
> ifconfig eth1 up
> sleep 60
>
> It was definitely a card/driver issue, though. I've been using Iexas
> Instruments TLAN-based cards successfully since.
>
> -----Original Message-----
> From: Henrik Nordstrom [mailto:hno@hem.passagen.se]
> Sent: Tuesday, September 12, 2000 3:37 PM
> To: Michael Baird
> Cc: squid-users@ircache.net
> Subject: Re: [SQU] Select Loop Failed
>
>
> What you describe is more likely a network driver issue. If there are
> network driver problems then Squid will get into trouble as well, in
> some cases with the mentioned error message.
>
> Try switching to another network card model or brand.
>
> Problems similar to this have been experienced on Linux with
> * 3com vortex cards
> * Intel EtherExpress 100
> * Tulip based cards (built in Compaq server card)
>
> Of the three the tulip cards have been the most stable, but then I
> haven't used the other two models in quite some time now (a year or so).
>
> In some cases messages are logged in /var/log/messages, sometimes not.
> In most cases it helps to stop the network, unload the driver module and
> start the network again.
>
> --
> Henrik Nordstrom
>
>
> Michael Baird wrote:
> >
> > I'm currently testing 2.4.4Dev, w/no special compile options, no DISKD,
> > I've had it running for a couple of weeks, and in the last 3 days, it
> > seems to have killed my ethernet interface, with the error message of
> > Select Loop Failed, this is written in the user.log, can someone tell me
> > what generally causes select loop failed, I'm using linux kernel2.2.16,
> > 512MBRam,4x20GB IDE, dual PII-500, 30GB cache, memory utilization looks
> > fine, not going into swap, it reaches about 70request/sec. It usually
> > dies at peak request time also.
> >
> > Regards
> > MIKE
> >
> > --
> > To unsubscribe, see http://www.squid-cache.org/mailing-lists.html
>
> --
> To unsubscribe, see http://www.squid-cache.org/mailing-lists.html
>
> --
> To unsubscribe, see http://www.squid-cache.org/mailing-lists.html
>

--
To unsubscribe, see http://www.squid-cache.org/mailing-lists.html