Does T2080QDS support Intel E1000e card in SDK 1.7?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Does T2080QDS support Intel E1000e card in SDK 1.7?

618 Views
jinyanjiang
Contributor I

When I ifup E1000e card in SDK 1.7 kernel, I got the below error. I have attached complete boot log for reference.

 

root@t2080qds:~# ifconfig eth6 up

IPv6: ADDRCONF(NETDEV_UP): eth6: link is not ready

8021q: adding VLAN 0 to HW filter on device eth6

root@t2080qds:~#

root@t2080qds:~# e1000e: eth6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

IPv6: ADDRCONF(NETDEV_CHANGE): eth6: link becomes ready

 

root@t2080qds:~# e1000e 0002:01:00.0 eth6: Detected Hardware Unit Hang:

  TDH                  <0>

  TDT                  <1>

  next_to_use          <1>

  next_to_clean        <0>

buffer_info[next_to_clean]:

  time_stamp           <ffff084f>

  next_to_watch        <0>

  jiffies              <ffff0ca3>

  next_to_watch.status <0>

MAC Status             <80383>

PHY Status             <792d>

PHY 1000BASE-T Status  <3d00>

PHY Extended Status    <3100>

PCI Status             <10>

 

NETDEV WATCHDOG: eth6 (e1000e): transmit queue 0 timed out

root@t2080qds:~#------------[ cut here ]------------

WARNING: at net/sched/sch_generic.c:279

Modules linked in: nfsd exportfs qoriq_dbg(O)

CPU: 2 PID: 2123 Comm: named Tainted: G           O 3.12.19-rt30-QorIQ-SDK-V1.7+g6619b8b #1

task: c0000000060c2280 ti: c00000007ffc4000 task.ti: c000000079d14000

NIP: c00000000062d320 LR: c00000000062d31c CTR: c0000000002fe3ec

REGS: c00000007ffc79f0 TRAP: 0700   Tainted: G           O  (3.12.19-rt30-QorIQ-SDK-V1.7+g6619b8b)

MSR: 0000000080029000 <CE,EE,ME>  CR: 48004244  XER: 20000000

SOFTE: 1

 

GPR00: c00000000062d31c c00000007ffc7c70 c000000000b3a4b0 000000000000003a

GPR04: 0000000048004244 0000000000000001 c000000000aec748 00000000000000ff

GPR08: 0000000000000000 0000000000000001 00000000b9947588 0000000000000020

GPR12: 0000000028004242 c00000000fff4f00 00000000f7a16418 000000000000fc00

GPR16: 0000000000000100 0000000000000100 0000000000404140 c000000079199c28

GPR20: c000000079199828 0000000000000000 c000000079199428 c000000079199028

GPR24: 0000000000000000 ffffffffffffffff 0000000000000000 0000000000000002

GPR28: 0000000000000004 c000000000b3d180 c000000079da4000 0000000000000000

NIP [c00000000062d320] .dev_watchdog+0x37c/0x390

LR [c00000000062d31c] .dev_watchdog+0x378/0x390

Call Trace:

[c00000007ffc7c70] [c00000000062d31c] .dev_watchdog+0x378/0x390 (unreliable)

[c00000007ffc7d20] [c000000000047704] .call_timer_fn.isra.30+0x44/0xb8

[c00000007ffc7db0] [c000000000047998] .run_timer_softirq+0x220/0x2c8

[c00000007ffc7ea0] [c00000000003f774] .__do_softirq+0x15c/0x288

[c00000007ffc7f90] [c000000000014c5c] .call_do_softirq+0x14/0x24

[c000000079d17c80] [c000000000005eac] .do_softirq+0xd0/0xfc

[c000000079d17d10] [c000000000040048] .irq_exit+0xb8/0xec

[c000000079d17d90] [c00000000001060c] .timer_interrupt+0x118/0x1a8

[c000000079d17e30] [c000000000019054] exc_0x900_common+0x104/0x108

Instruction dump:

994d06b4 4bfffe40 7fc3f378 4bfe3341 60000000 7fc4f378 7c651b78 3c62ffe4

3863deb0 7fe6fb78 4810aaed 60000000 <0fe00000> 39200001 3d02fff4 9928dc13

---[ end trace e3ff271575642d1e ]---

e1000e 0002:01:00.0 eth6: Reset adapter unexpectedly

 

root@t2080qds:~# e1000e: eth6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

e1000e 0002:01:00.0 eth6: Detected Hardware Unit Hang:

  TDH                  <0>

  TDT                  <1>

  next_to_use          <1>

  next_to_clean        <0>

buffer_info[next_to_clean]:

  time_stamp           <ffff113a>

  next_to_watch        <0>

  jiffies              <ffff156d>

  next_to_watch.status <0>

MAC Status             <80383>

PHY Status             <792d>

PHY 1000BASE-T Status  <3d00>

PHY Extended Status    <3100>

PCI Status             <10>

e1000e 0002:01:00.0 eth6: Reset adapter unexpectedly

e1000e: eth6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

Original Attachment has been moved to: t2080qds-fullbootlog.zip

Labels (1)
0 Kudos
1 Reply

375 Views
ufedor
NXP Employee
NXP Employee

Please check whether the issue is resolved in the SDK 1.9.

0 Kudos