mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Samuel Maftoul <maftoul@esrf.fr>
To: Mickael Bailly <mickael.bailly@trader.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: eepro100: wait_for_cmd_done timeout (2.4.19-pre2/8)
Date: Tue, 7 May 2002 17:26:32 +0200	[thread overview]
Message-ID: <20020507172632.F3155@pcmaftoul.esrf.fr> (raw)
In-Reply-To: <Pine.LNX.4.44.0205071454270.16371-100000@dunlop.admin.ie.alphyra.com> <200205071712.21699.mickael.bailly@trader.com>

On Tue, May 07, 2002 at 05:12:21PM +0200, Mickael Bailly wrote:
> 	Hi,
> 
> We got the same problem with PCI eepro NICs (not onboard) on Dell Poweredge.
I'm on dell's also but not only poweredge
> We got the same error messages
> We tried the alternative 'e100' driver, but without success.
We also did but we get  approximatively with the same message ( no
really the same, but one talking about timeouts)
> We tried on 2.2 kernels (RedHat 6.2), then on 2.4 (RedHat 7.1/7.2): problem 
> still exist.
I didn't tried 2.2
> 
> At last we disabled APIC ( configuration line 'append=noapic' in your 
> lilo.conf configuration file )
I did also but my problem with firewire still exists 
That's the first thing I did, disableapic and noapic ( it's an smp
system so I have no idea what the consequences of this are )

> 
> Now it's working fine since 2 days... need a little more time to validate the 
> change...
> 
> See you
> Mickael
> 
Thanks for the tip.
        Sam

      reply	other threads:[~2002-05-07 15:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-07 14:23 Paul Jakma
2002-05-07 14:53 ` Richard B. Johnson
2002-05-07 15:06   ` Samuel Maftoul
2002-05-07 15:44     ` Richard B. Johnson
2002-05-07 20:20       ` Paul Jakma
2002-05-08  3:22   ` Paul Jakma
2002-05-07 15:12 ` Mickael Bailly
2002-05-07 15:26   ` Samuel Maftoul [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020507172632.F3155@pcmaftoul.esrf.fr \
    --to=maftoul@esrf.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mickael.bailly@trader.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®