public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: "Hillier\, Gernot" <gernot.hillier@siemens.com>
Cc: jesse.brandeburg@intel.com, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, bruce.w.allan@intel.com
Subject: Re: e1000e: sporadic "hardware error"s with Intel 82563EB on Supermicro X7DB3
Date: Thu, 09 Oct 2008 00:03:00 +0200	[thread overview]
Message-ID: <m31vyq923v.fsf@maximus.localdomain> (raw)
In-Reply-To: <48ECB727.6050905@siemens.com> (Gernot Hillier's message of "Wed\, 08 Oct 2008 15\:35\:35 +0200")

"Hillier, Gernot" <gernot.hillier@siemens.com> writes:

>         Region 0: Memory at d0020000 (32-bit, non-prefetchable) [size=128K]
>         Region 1: Memory at d0000000 (32-bit, non-prefetchable) [size=128K]
>         Region 2: I/O ports at 4000 [size=32]
>         [virtual] Expansion ROM at d0080000 [disabled] [size=64K]

Doesn't look like a spurious reset, though.

> - Control "DisINTx-" changes to "DisINTx+" if the card is correctly
> initialized
> - Interrupt changes from IRQ 18 to IRQ 4345 if card is correctly initialized
> - Message Signalled Interrupts change from "Enable-" to "Enable+"

The "normal" effects of enabling MSI.
-- 
Krzysztof Halasa

  reply	other threads:[~2008-10-08 22:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-07 14:25 e1000e: sporadic "hardware error"s with Intel 82563EB on Supermicro X7DB3 Hillier, Gernot
2008-10-08 10:29 ` Krzysztof Halasa
2008-10-08 13:35   ` Hillier, Gernot
2008-10-08 22:03     ` Krzysztof Halasa [this message]
     [not found] <EA929A9653AAE14F841771FB1DE5A1365F498F4EDC@rrsmsx501.amr.corp.intel.com>
2008-10-08 15:25 ` Graham, David
2008-10-08 21:36   ` Stephen Hemminger
2008-10-09 13:18   ` Hillier, Gernot
2008-10-14  9:18     ` Gernot Hillier
2008-10-15 16:37       ` Graham, David
2008-10-16 12:32         ` Hillier, Gernot
2008-10-16 16:07         ` Hillier, Gernot
2008-11-11 10:05           ` Hillier, Gernot

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=m31vyq923v.fsf@maximus.localdomain \
    --to=khc@pm.waw.pl \
    --cc=bruce.w.allan@intel.com \
    --cc=gernot.hillier@siemens.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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