From: "Marius Bjørnstad" <pmb@fa2k.net>
To: <linux-kernel@vger.kernel.org>
Subject: RE: Crash in et131x
Date: Mon, 19 Sep 2011 21:02:31 +0200 [thread overview]
Message-ID: <000801cc76fe$b01775c0$10466140$@net> (raw)
In-Reply-To:
I'm very sorry, the card was defective, just tried it with Windows.
Marius
-----Original Message-----
From: Marius Bjørnstad [mailto:pmb@fa2k.net]
Sent: 18 September 2011 13:37
To: 'linux-kernel@vger.kernel.org'
Subject: Crash in et131x
Hi,
I'm using an ExpressCard ethernet adapter, using the et131x (staging)
driver. The system stops responding about 15 min after I connect the NIC. It
crashes even when I don't transfer any data, but it doesn't crash when it's
not connected to a switch. There is no debug information on the screen.
I'm using 2.6.40.4-5.fc15.x86_64, which is a re-named 3.0 kernel (x86_64 bit
system). I also tried to build the et131x module from source using 3.1-rc6,
with the same result. The NIC is a no-name ExpressCard, here is the output
of lspci -v:
02:00.0 Ethernet controller: Agere Systems ET-131x PCI-E Ethernet Controller
(rev 02)
Subsystem: Agere Systems ET-131x PCI-E Ethernet Controller
Physical Slot: 1
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at 80200000 (64-bit, non-prefetchable) [size=2M]
[virtual] Expansion ROM at 80400000 [disabled] [size=128K]
Capabilities: [40] Power Management version 2
Capabilities: [48] Express Endpoint, MSI 00
Capabilities: [5c] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [100] Advanced Error Reporting
Capabilities: [130] Virtual Channel
Capabilities: [14c] Device Serial Number 9a-78-56-34-12-2d-02-00
Kernel driver in use: et131x
Kernel modules: et131x
Cheers,
Marius
PS: If you know a gigabit ethernet expresscard that definitely works with
Linux and is available in Europe, I'd be happy to know.
next reply other threads:[~2011-09-19 19:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 19:02 Marius Bjørnstad [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-09-18 11:37 Crash in et131x Marius Bjornstad
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='000801cc76fe$b01775c0$10466140$@net' \
--to=pmb@fa2k.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.