Project

General

Profile

Actions

Bug #2529

open

Sundance network adapter is not detected and attached

Added by kworr almost 11 years ago. Updated almost 11 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
-
Target version:
Start date:
03/21/2013
Due date:
% Done:

0%

Estimated time:

Description

I have one of those ASUS NX1001 cards with Sundance controller. Current version doesn't correctly detects it.

pciconf -lv (snip):
none6@pci0:2:6:0: class=0x020000 card=0x82131043 chip=0x020013f0 rev=0x31 hdr=0x00
vendor = 'Sundance Technology Inc / IC Plus Corp'
device = 'IC Plus IP100A Integrated 10/100 Ethernet MAC + PHY'
class = network
subclass = ethernet

In current FreeBSD (RELENG_9) it is detected as:

ste0: <Sundance ST201 10/100BaseTX> port 0xd100-0xd17f mem 0xfe920000-0xfe9201ff irq 20 at device 6.0 on pci2
ste0: Ethernet address: 00:26:18:eb:37:85
miibus1: <MII bus> on ste0
ukphy0: <Generic IEEE 802.3u media interface> PHY 0 on miibus1
ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto


Files

coredump.jpg (65.2 KB) coredump.jpg kworr, 03/24/2013 11:48 PM
coretrace.jpg (66.6 KB) coretrace.jpg kworr, 03/24/2013 11:48 PM
Actions #1

Updated by sepherosa almost 11 years ago

On Thu, Mar 21, 2013 at 10:13 PM, Volodymyr Kostyrko via Redmine
<> wrote:

Issue #2529 has been reported by kworr.

----------------------------------------
Bug #2529: Sundance network adapter is not detected and attached
http://bugs.dragonflybsd.org/issues/2529

Author: kworr
Status: New
Priority: Low
Assignee:
Category:
Target version:

I have one of those ASUS NX1001 cards with Sundance controller. Current version doesn't correctly detects it.

Please test the latest master:
af3cc6ae269ab98cdf5a8347aaf5d857bc10a1a7

Should work now.

pciconf -lv (snip):
none6@pci0:2:6:0: class=0x020000 card=0x82131043 chip=0x020013f0 rev=0x31 hdr=0x00
vendor = 'Sundance Technology Inc / IC Plus Corp'
device = 'IC Plus IP100A Integrated 10/100 Ethernet MAC + PHY'
class = network
subclass = ethernet

In current FreeBSD (RELENG_9) it is detected as:

ste0: <Sundance ST201 10/100BaseTX> port 0xd100-0xd17f mem 0xfe920000-0xfe9201ff irq 20 at device 6.0 on pci2
ste0: Ethernet address: 00:26:18:eb:37:85
miibus1: <MII bus> on ste0
ukphy0: <Generic IEEE 802.3u media interface> PHY 0 on miibus1
ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

--
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account

--
Tomorrow Will Never Die

Updated by kworr almost 11 years ago

It's getting worse. The card is detected correctly:

Mar 23 01:12:11 kernel: ste0: <Sundance ST201 10/100BaseTX> port 0xd100-0xd17f mem 0xfe920000-0xfe9201ff irq 20 at device 6.0 on pci2
Mar 23 01:12:11 kernel: miibus1: <MII bus> on ste0
Mar 23 01:12:11 kernel: ukphy0: <Generic IEEE 802.3u media interface> on miibus1
Mar 23 01:12:11 kernel: ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
Mar 23 01:12:11 kernel: ste0: MAC address: 00:26:18:eb:37:85

The only difference from FreeBSD is that ukphy0 doesn't report 'none' as mediaopt whereas on FreeBSD it does.

After this no packets are flowing through kernel. Something like one minute later kernel crashes with some gibberish words. I tried several times but result is different and unclear, screenshots attached.

Actions #3

Updated by sepherosa almost 11 years ago

On Mon, Mar 25, 2013 at 2:48 PM, Volodymyr Kostyrko via Redmine
<> wrote:

Issue #2529 has been updated by kworr.

File coredump.jpg added
File coretrace.jpg added

It's getting worse. The card is detected correctly:

Mar 23 01:12:11 kernel: ste0: <Sundance ST201 10/100BaseTX> port 0xd100-0xd17f mem 0xfe920000-0xfe9201ff irq 20 at device 6.0 on pci2
Mar 23 01:12:11 kernel: miibus1: <MII bus> on ste0
Mar 23 01:12:11 kernel: ukphy0: <Generic IEEE 802.3u media interface> on miibus1
Mar 23 01:12:11 kernel: ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
Mar 23 01:12:11 kernel: ste0: MAC address: 00:26:18:eb:37:85

The only difference from FreeBSD is that ukphy0 doesn't report 'none' as mediaopt whereas on FreeBSD it does.

After this no packets are flowing through kernel. Something like one minute later kernel crashes with some gibberish words. I tried several times but result is different and unclear, screenshots attached.

I have taken a look at ste(4). This driver is not busdma(9) clean, so
it probably will not function correctly, e.g. the random crash you
have seen, on x86_64 system w/ more than 4GB memory.

If you or other folks are interested, other drivers, e.g. bfe(4),
could be used as an example to make ste(4) busdma(9) clean. Patches
are welcome! I personally don't have enough time to make various old
drivers busdma(9) currently.

Best Regards,
sephe

----------------------------------------
Bug #2529: Sundance network adapter is not detected and attached
http://bugs.dragonflybsd.org/issues/2529

Author: kworr
Status: New
Priority: Low
Assignee:
Category:
Target version:

I have one of those ASUS NX1001 cards with Sundance controller. Current version doesn't correctly detects it.

pciconf -lv (snip):
none6@pci0:2:6:0: class=0x020000 card=0x82131043 chip=0x020013f0 rev=0x31 hdr=0x00
vendor = 'Sundance Technology Inc / IC Plus Corp'
device = 'IC Plus IP100A Integrated 10/100 Ethernet MAC + PHY'
class = network
subclass = ethernet

In current FreeBSD (RELENG_9) it is detected as:

ste0: <Sundance ST201 10/100BaseTX> port 0xd100-0xd17f mem 0xfe920000-0xfe9201ff irq 20 at device 6.0 on pci2
ste0: Ethernet address: 00:26:18:eb:37:85
miibus1: <MII bus> on ste0
ukphy0: <Generic IEEE 802.3u media interface> PHY 0 on miibus1
ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

--
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account

--
Tomorrow Will Never Die

Actions

Also available in: Atom PDF