From: thockin@hockin.org
To: "Shawn M. Campbell" <scampbell@malone.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PCI Express or TG3 issue
Date: Wed, 21 Sep 2005 10:21:57 -0700 [thread overview]
Message-ID: <20050921172156.GA31339@hockin.org> (raw)
In-Reply-To: <433182C8.2060006@malone.edu>
On Wed, Sep 21, 2005 at 11:56:56AM -0400, Shawn M. Campbell wrote:
> 0000:02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751
> Gigabit Ethernet PCI Express (rev 11)
> Subsystem: IBM: Unknown device 02f7
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr+ Stepping- SERR+ FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
> Latency: 0, Cache Line Size: 0x08 (32 bytes)
> Interrupt: pin A routed to IRQ 5
> Region 0: Memory at <ignored> (64-bit, non-prefetchable)
^^^^^^^^^^^^^^^^^^
Problem.
hexdump /proc/bus/pci/02/00.0 and send it here.
next prev parent reply other threads:[~2005-09-21 17:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 15:56 PCI Express or TG3 issue Shawn M. Campbell
2005-09-21 17:21 ` thockin [this message]
2005-09-21 17:18 ` Martin Mares
-- strict thread matches above, loose matches on Subject: below --
2005-09-21 17:34 FW: " Campbell, Shawn
2005-09-21 18:11 ` thockin
2005-09-22 15:25 ` Atsushi Nemoto
2005-09-22 15:58 ` thockin
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=20050921172156.GA31339@hockin.org \
--to=thockin@hockin.org \
--cc=linux-kernel@vger.kernel.org \
--cc=scampbell@malone.edu \
/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