From: P Lavin <lavin.p@redpinesignals.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux kernel TI TLAN driver
Date: Fri, 22 Apr 2005 14:23:27 +0530 [thread overview]
Message-ID: <4268BB87.1030902@redpinesignals.com> (raw)
In-Reply-To: <200504220800.j3M80GSL006528@kruuna.helsinki.fi>
Can you send me the oops capture ??
Atro Tossavainen wrote:
> Hi,
>
> I got my hands on a Texas Instruments ThunderLAN PCI 100 Mbit card (PCI
> ID 104c:0500), which is what SGI are supplying if you want a second NIC
> in your O2. It appears that this card is not supported by the tlan
> driver in the Linux kernel (at least not in 2.4.29, which is what I am
> using on the machine I tried it on). Patching the driver with the
> relevant PCI IDs allowed the detection of the card, as shown in dmesg:
>
> ThunderLAN driver v1.15
> TLAN: eth0 irq=15, io=8400, Compaq NetFlex-3/E, Rev. 48
> TLAN: 1 device installed, PCI: 1 EISA: 0
>
> and in "ifconfig eth0":
>
> eth0 Link encap: Ethernet HWaddr 00:00:58:01:55:53
>
> (and the rest of the normal stuff)
>
> but trying to configure the interface with an address and bringing
> it up caused a kernel oops. (This is on Alpha.)
>
> # ifconfig eth0 inet blah... up
> Unable to handle kernel paging request at virtual address 00000000093fcb04
> Segmentation fault
>
> In dmesg, there is an
>
> ifconfig(4218): Oops 0
> followed by a register dump, a trace, and some code.
>
> Any ideas?
>
--
P.Lavin
Software Engineer,
Redpine Signals ,Inc.
Hyderabad.
http://www.redpinesignals.com
next prev parent reply other threads:[~2005-04-22 8:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-22 8:00 Linux kernel TI TLAN driver Atro Tossavainen
2005-04-22 8:53 ` P Lavin [this message]
2005-04-25 11:24 ` Alan Cox
2005-04-25 13:56 ` Torben Mathiasen
2005-04-25 16:30 ` Ganesh Venkatesan
2005-04-25 17:12 ` Torben Mathiasen
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=4268BB87.1030902@redpinesignals.com \
--to=lavin.p@redpinesignals.com \
--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