public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "John Bäckstrand" <sandos@home.se>
To: <linux-kernel@vger.kernel.org>
Subject: RE: [BUG] R8169 on 2.6.0-test9
Date: Mon, 27 Oct 2003 00:43:13 +0100	[thread overview]
Message-ID: <066301c39c1a$ed75d0f0$034d210a@sandos> (raw)
In-Reply-To: 

>The r8169 gigabit ethernet card causes lockups on both 2.4.22 and
2.6.0-test9.

It does it even on 2.4.20 and using the 8139cp. Heres lspci -vvv, starting
to wonder if this card is special/odd/unsupported or if its just this
hardware not being happy.

00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 (rev
10)
        Subsystem: CNet Technology Inc ProG-2000L
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (8000ns min, 16000ns max), cache line size 08
        Interrupt: pin A routed to IRQ 11
        Region 0: I/O ports at e000 [size=256]
        Region 1: Memory at e8000000 (32-bit, non-prefetchable) [size=256]
        Expansion ROM at <unassigned> [disabled] [size=128K]
        Capabilities: [dc] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
PME(D0-,D1+,D2+,D3hot+,D3cold+)
                Status: D0 PME-Enable+ DSel=0 DScale=0 PME-

---
John Bäckstrand


             reply	other threads:[~2003-10-26 23:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-26 23:43 John Bäckstrand [this message]
2003-10-27  0:55 ` [BUG] R8169 on 2.6.0-test9 Zwane Mwaikambo
2003-10-27 10:37   ` John Bäckstrand
2003-10-27 20:39     ` Zwane Mwaikambo
2003-10-27 22:03       ` SV: " John Bäckstrand
  -- strict thread matches above, loose matches on Subject: below --
2003-10-26 20:40 John Bäckstrand

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='066301c39c1a$ed75d0f0$034d210a@sandos' \
    --to=sandos@home.se \
    --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