mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Subbulu Koya <proteuskor@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: linux 2.4.20:Intel e1000 4.4.19 and 5.0.43 (Intel Pro1000/MT) hard lock in e1000_reset_hw
Date: Wed, 2 Apr 2003 13:23:11 -0800 (PST)	[thread overview]
Message-ID: <20030402212311.69823.qmail@web11307.mail.yahoo.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 2367 bytes --]

During MAC reset(e1000_hw.c:e1000_reset_hw) my system
hard locks. I have tried the following configurations:

Software:

            Linux 2.4.20 SMP

            Intel e1000 versions 4.4.19 and 5.0.43
with SMP and with and without ANS/diagnostics

Hardware:

            Tyan S2723 Motherboatd w/ dual XEONs

            *(onboard) Intel 82545EM rev1 (Pro1000/MT)
on IRQ 48 (unshared)

            (also on board) Intel 82557/8/9 (EEPro100)
on IRQ 17 (unshared, unplugged)

 

I have traced it to the following point in the 4.4.19
code:

 

    e1000_hw.c : e1000_reset_hw(struct e1000_hw *hw)

    ...

      /* Issue a global reset to the MAC.  This will
reset the chip's

         * transmit, receive, DMA, and link units.  It
will not effect

         * the current PCI configuration.  The global
reset bit is self-

         * clearing, and should clear within a
microsecond.

         */

        DEBUGOUT("Issuing a global reset to MAC\n");

        ctrl = E1000_READ_REG(hw, CTRL);

 

        if(hw->mac_type > e1000_82543)

            E1000_WRITE_REG_IO(hw, CTRL, (ctrl |
E1000_CTRL_RST));

        else

            E1000_WRITE_REG(hw, CTRL, (ctrl |
E1000_CTRL_RST));

 

    ...

    In this case 'E1000_WRITE_REG_IO(hw, CTRL, (ctrl |
E1000_CTRL_RST));' is

    called. Then the systems continues to
msec_delay(4), at which point the

    system locks up entirely.

 

and in the 5.0.43 code:

    e1000_main.c: e1000_reset(struct e1000_adapter
*adapter)

    …

    E1000_WRITE_REG(&adapter->hw, PBA, pba);

 

    adapter->hw.fc = adapter->hw.original_fc;

    e1000_reset_hw(&adapter->hw);

   …

   In this case ‘E1000_WRITE_REG(&adapter->hw, PBA,
pba);’ is called. Then

   the system calls e1000_reset_hw, my first trace
message isn’t hit and so with

   this driver version I seem to lockup just a bit
earlier then with 4.4.19

 

In both cases e1000_reset() is being called by
e1000_down(). In order to create this problem I bring
the interface up and down once every 10seconds or so
using ifconfig.

 

Is it possible this driver isn't working properly with
the 82545EM rev 1?

Is their any additional information I can provide?

 

Thank you in advance,

/)dam.. .  . D o n ' t   S t o p

 



__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - File online, calculators, forms, and more
http://tax.yahoo.com

                 reply	other threads:[~2003-04-02 21:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030402212311.69823.qmail@web11307.mail.yahoo.com \
    --to=proteuskor@yahoo.com \
    --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

all inboxes | Powered by JetHome®