public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Robbert Kouprie" <robbert@jvb.tudelft.nl>
To: "'Kenneth MacDonald'" <kenny@holyrood.ed.ac.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: NIC lockup in 2.4.17 (SMP/APIC/Intel 82557)
Date: Sun, 20 Jan 2002 22:53:03 +0100	[thread overview]
Message-ID: <005e01c1a1fc$d61eae50$020da8c0@nitemare> (raw)
In-Reply-To: <yqo1ygkd8np.fsf@penguin.ucs.ed.ac.uk>

Hi Kenny,

Thanks for the quick reply :) Just checked it, and it's in slot 2, so
that's not the problem. It doesn't share the HPT366 IRQ. This is my
/proc/interrupts:

radium:/$ cat /proc/interrupts 
           CPU0       CPU1       
  0:    1207342    1186359    IO-APIC-edge  timer
  1:          3          1    IO-APIC-edge  keyboard
  2:          0          0          XT-PIC  cascade
  4:         68         55    IO-APIC-edge  serial
  8:          2          0    IO-APIC-edge  rtc
 14:          6         12    IO-APIC-edge  ide0
 17:    1723020    1719230   IO-APIC-level  eth0
 18:      33419      33452   IO-APIC-level  ide2
 19:          0          0   IO-APIC-level  es1371
NMI:          0          0 
LOC:    2393677    2393676 
ERR:         14
MIS:          0

Regards,
- Robbert

> -----Original Message-----
> From: kenny@penguin.ucs.ed.ac.uk 
> [mailto:kenny@penguin.ucs.ed.ac.uk] On Behalf Of Kenneth MacDonald
> Sent: zondag 20 januari 2002 22:18
> To: Robbert Kouprie
> Subject: Re: NIC lockup in 2.4.17 (SMP/APIC/Intel 82557)
> 
> 
> Do you have the NIC in slot 3?  Read your motherboard manual, 
> page 1-4.
> 
> Hope that helps, just in case!
> -- 
> Kenny
> 
> ADML Support, EUCS, The University of Edinburgh, Scotland.
> 


       reply	other threads:[~2002-01-20 21:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <yqo1ygkd8np.fsf@penguin.ucs.ed.ac.uk>
2002-01-20 21:53 ` Robbert Kouprie [this message]
2002-01-21 18:48   ` NIC lockup in 2.4.17 (SMP/APIC/Intel 82557) Jussi Laako
2002-01-22  8:51 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
2002-01-31 16:52             ` Robbert Kouprie
2002-01-31 17:54               ` Ben Greear
2002-01-31 19:17                 ` Robbert Kouprie
     [not found] <Pine.LNX.4.33.0201201531570.6499-100000@coffee.psychology.mcmaster.ca>
2002-01-21 10:06 ` Robbert Kouprie
  -- 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='005e01c1a1fc$d61eae50$020da8c0@nitemare' \
    --to=robbert@jvb.tudelft.nl \
    --cc=kenny@holyrood.ed.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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