- 論壇徽章:
- 0
|
小弟有一款cavium板子,5020, 上面的網(wǎng)卡其中千兆的線由于主板設(shè)計(jì)問題不能連接。板子應(yīng)可用100M或者10M連接。
但是當(dāng)兩臺(tái)這樣的機(jī)器對(duì)接的時(shí)候,發(fā)現(xiàn)連接不上,網(wǎng)口燈不亮。但是將一臺(tái)板子里面的自協(xié)商關(guān)閉之后網(wǎng)口燈點(diǎn)亮,網(wǎng)絡(luò)連接。
連接速率顯示100M全雙工。
但當(dāng)這樣對(duì)接之后,使用bw進(jìn)行性能測(cè)試時(shí), 關(guān)閉自協(xié)商的那臺(tái)機(jī)器會(huì)panic,信息如下:
/ # Port 1 receive error code 6, packet dropped
Port 1 receive error code 6, packet dropped
Port 1 receive error code 6, packet dropped
CPU 0 Unable to handle kernel paging request at virtual address 0000000000000000, epc == ffffffff8138e0c4, ra == ffffffff8138e988
Oops[#1]:
Cpu 0
$ 0 : 0000000000000000 0000000000000008 0000000000000000 0000000000000000
$ 4 : a80000000db62a80 0000000000000040 0000000000000040 ffffffff8189f168
$ 8 : 0000000000000000 0000000000000000 ffffffff81482ac8 0000000000000000
$12 : 0000000000000010 ffffffff81105a74 a80000000f850000 0000000000000000
$16 : 0000000000000000 a800000002688ed8 a800000002688ee0 00000000ffffd08a
$20 : 0000000000000040 ffffffff818a0000 a800000002688f10 ffffffff818a0000
$24 : 0000000000000006 0000000000000000
$28 : ffffffff81898000 ffffffff8189bb70 ffffffff821ee6a0 ffffffff8138e988
Hi : 00000000000000cc
Lo : fffffffff070e000
epc : ffffffff8138e0c4 process_backlog+0x94/0x108
Not tainted
ra : ffffffff8138e988 net_rx_action+0x118/0x220
Status: 1000cce2 KX SX UX KERNEL EXL
Cause : 0080000c
BadVA : 0000000000000000
PrId : 000d0601 (Cavium Octeon+)
Modules linked in: crypto_null authenc ebt_redirect ebtable_broute ebtables xt_comment xt_state iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 alg_init pcie_ssx06 octeon_gpio xfrm_user esp4
Process swapper (pid: 0, threadinfo=ffffffff81898000, task=ffffffff818a6880, tls=0000000000000000)
Stack : 0000000000000040 a800000002688f10 0000000000000006 0000000000000126
a800000002688ed8 a800000002688ef8 00000000ffffd08b ffffffff8138e988
0000000000000001 ffffffff8189c798 0000000000000018 0000000000000100
0000000000000003 000000000000000a ffffffff821af1d0 ffffffff821ee6a0
0000000000000000 ffffffff81158d1c 0000000000000000 8001070000000218
8001070000000200 8001070000000000 8001070000000108 ffffffff821d0000
0000000000000005 ffffffffc0103ca0 0000000000000000 ffffffff81158dd8
0000000000000027 ffffffff8110c460 ffffffff821d0000 0000000000000000
0000000000000001 ffffffff821d0000 ffffffff821d0000 ffffffff81105bd0
0000000000000005 ffffffff81100888 0000000000000000 ffffffff821d0000
...
Call Trace:
[<ffffffff8138e0c4>] process_backlog+0x94/0x108
[<ffffffff8138e988>] net_rx_action+0x118/0x220
[<ffffffff81158d1c>] __do_softirq+0x154/0x1a0
[<ffffffff81158dd8>] do_softirq+0x70/0x78
[<ffffffff8110c460>] plat_irq_dispatch+0xd8/0x158
[<ffffffff81100888>] ret_from_irq+0x0/0x4
[<ffffffff81100a80>] r4k_wait+0x20/0x40
[<ffffffff81129d2c>] cpu_idle+0x74/0x90
[<ffffffff818d7aa4>] start_kernel+0x3bc/0x41c
Code: dc820008 fc800000 fc800008 <fc430000> fc620008 41606020 0c4e36ca 26100001 0214182a
Disabling lock debugging due to kernel taint
Kernel panic - not syncing: Fatal exception in interrupt
求達(dá)人解答。 |
|