mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Egger <de@axiros.com>
To: Ross Biro <rossb@google.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC/Patch 2.6.11] Take control of PCI Master Abort Mode
Date: Wed, 6 Apr 2005 22:44:31 +0200	[thread overview]
Message-ID: <c818c171530aec46fe0c8895b6e59901@axiros.com> (raw)
In-Reply-To: <4252E827.4080807@google.com>

[-- Attachment #1: Type: text/plain, Size: 732 bytes --]

On 05.04.2005, at 21:33, Ross Biro wrote:

> The problem with always setting the bit is that some PCI hardware, 
> notably some Intel E-1000 chips (Ethernet controller: Intel 
> Corporation: Unknown device 1076) cannot properly handle the target 
> abort bit.  In the case of the E-1000 chip, the driver must reset the 
> chip to recover. This usually leads to the machine being off the 
> network for several seconds, or sometimes even minutes, which can be 
> bad for servers.

This sounds *exactly* like my problem since I swapped
motherboards. I'll see whether there's some option in
the BIOS that fixes it and if not bite the bullet and
compile a generic kernel....

Thanks a lot for investigating this.

Servus,
       Daniel

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 186 bytes --]

  parent reply	other threads:[~2005-04-06 20:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-05 19:33 Ross Biro
2005-04-05 20:53 ` Randy.Dunlap
2005-04-06 12:47   ` Ross Biro
2005-04-06 20:44 ` Daniel Egger [this message]
2005-04-10 13:29 ` Andi Kleen
     [not found]   ` <8783be66050412075218b2b0b0@mail.gmail.com>
2005-04-13 18:37     ` Andi Kleen
2005-04-13 23:00       ` Ross Biro
2005-04-13 23:28         ` Dave Jones
2005-04-14 17:25           ` Ross Biro
2005-04-14 17:34             ` Tim Hockin
2005-04-14 18:02               ` Andi Kleen
2005-04-14 18:33                 ` Dave Jones
2005-04-14 19:14             ` Daniel Egger

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=c818c171530aec46fe0c8895b6e59901@axiros.com \
    --to=de@axiros.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rossb@google.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
all inboxes | Powered by JetHome®