public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: Robbert Kouprie <robbert@jvb.tudelft.nl>, linux-kernel@vger.kernel.org
Subject: Re: NIC lockup in 2.4.17 (SMP/APIC/Intel 82557)
Date: Thu, 31 Jan 2002 09:32:25 -0700	[thread overview]
Message-ID: <3C597199.6050301@candelatech.com> (raw)
In-Reply-To: <20020130220659.29bd66f5.skraw@ithnet.com>	<002a01c1a9ee$1b6ddd20$020da8c0@nitemare> <20020131133516.68c78352.skraw@ithnet.com>

What does the rest of the hardware-config look like?  Is
the NIC attached to a 10bt hub?  Are you using PCI-Riser
cards?

Stephan von Krawczynski wrote:

> On Thu, 31 Jan 2002 01:27:47 +0100
> "Robbert Kouprie" <robbert@jvb.tudelft.nl> wrote:
> 
> 
>>Thanks for your reaction Stephan, but I seriously doubt the change below
>>would fix the problem... Also, as the problem appears randomly, and
>>usually after some uptime, I obviously can not know about it being fixed
>>if I constantly upgrade the kernel. I'd rather wait and see if it
>>appears again in time after I did a kernel upgrade, and not trying every
>>-pre while there's no mention on the mailing list of such bug being
>>fixed.
>>
>>Anyway, I just rebooted with 2.4.18-pre7-ac1, we'll see if it helps.
>>
> 
> Hello Robert,
> 
> Well, I know the changes to the driver are rather ... small :-)
> But on the other hand, I would not be all that sure that the bug is a
> hundred percent related to the driver itself.
> I run a working config with eepro100-driver, btw.
> 
> Regards,
> Stephan
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
> 


-- 
Ben Greear <greearb@candelatech.com>       <Ben_Greear AT excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear



  reply	other threads:[~2002-01-31 16:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-22  8:51 NIC lockup in 2.4.17 (SMP/APIC/Intel 82557) Robbert Kouprie
2002-01-22 14:53 ` James Bourne
2002-01-30 19:29   ` Robbert Kouprie
2002-01-30 21:06     ` Stephan von Krawczynski
2002-01-31  0:27       ` Robbert Kouprie
2002-01-31 12:35         ` Stephan von Krawczynski
2002-01-31 16:32           ` Ben Greear [this message]
2002-01-31 16:52             ` Robbert Kouprie
2002-01-31 17:54               ` Ben Greear
2002-01-31 19:17                 ` Robbert Kouprie
2002-02-01 17:52                 ` PCI Problems [was Re: NIC lockup in 2.4.17 (SMP/APIC/Intel 82557)] Edward S. Marshall
2002-02-01 18:16                   ` nick
2002-02-01 19:44                     ` Ken Brownfield
2002-02-01 23:54                   ` Alan Cox
     [not found] <Pine.LNX.4.33.0201201531570.6499-100000@coffee.psychology.mcmaster.ca>
2002-01-21 10:06 ` NIC lockup in 2.4.17 (SMP/APIC/Intel 82557) Robbert Kouprie
     [not found] <yqo1ygkd8np.fsf@penguin.ucs.ed.ac.uk>
2002-01-20 21:53 ` Robbert Kouprie
2002-01-21 18:48   ` Jussi Laako
  -- strict thread matches above, loose matches on Subject: below --
2002-01-20 19:16 Robbert Kouprie

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=3C597199.6050301@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robbert@jvb.tudelft.nl \
    --cc=skraw@ithnet.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