All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann Dupont <Yann.Dupont@IPv6.univ-nantes.fr>
To: linux-kernel@vger.kernel.org
Subject: Deadlock/crash with Quad tulip card in 2.4
Date: 10 May 2001 17:13:15 +0200	[thread overview]
Message-ID: <989507596.18286.0.camel@olive> (raw)

Hello. I'm having problem with Quad eth100 tulip (digital 21140) cards.

The machine was acting as a bridge with kernel 2.2 very reliably.

Now, when I boot 2.4.4-ac6, the machine hangs - no oops, nothing. Just
hang.

even CTRL-Scroll lock does nothing.

I supected a bridge problem (I know 2.2  & 2.4 bridge are different) But
it's not the case as I reproduce the bug on another machine (with
another motherboard. kernel 2.4.4-ac6 where the bridge is not
configured.)

single boot is OK,

ifconfig eth0 up is ok (MII negotiation is OK)
ifconfig eth1 up crash the machine -

on another boot i tried this :

ifconfig eth0 up
ifconfig eth0 down

ifconfig eth1 up is OK
ifconfig eth1 down ... etc etc

This works as long as only one interface is up. 

If only 1 interface is up, the machine works reliably.

just putting 2 interfaces up hang the machine.

Can this be an  IRQ sharing / bridge  problem  ??? (all interface shares
the same IRQ and are after a bridge)

I don't know if this is ac-series specific. I'll try tomorrow.

Any Idea how I can test further ? Without oops it's not easy...

Yann Dupont.

-- 
\|/ ____ \|/ Fac. des sciences de Nantes-Linux-Python-IPv6-ATM-BONOM....
"@'/ ,. \@"  Tel :(+33) [0]251125865(AM)[0]251125857(PM)[0]251125868(Fax)
/_| \__/ |_\ Yann.Dupont@sciences.univ-nantes.fr
   \__U_/    http://www.unantes.univ-nantes.fr/~dupont


             reply	other threads:[~2001-05-10 15:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-10 15:13 Yann Dupont [this message]
2001-05-10 16:08 ` Deadlock/crash with Quad tulip card in 2.4 Jeff Garzik
2001-05-11  8:30   ` Yann Dupont

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=989507596.18286.0.camel@olive \
    --to=yann.dupont@ipv6.univ-nantes.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.