---------- 已转发邮件 ----------
发件人： yi zheng <yizhen...@gmail.com>
日期： 2011年8月12日 上午11:21
主题： kernel oops when using RTnet
收件人： rtnet-users-requ...@lists.sourceforge.net
Hi all
I meet with headache problem when using RTnet-0.9.12 in my embedded
platform with AT91SAM9263 arm and DM9161A network card.My software
environments is described as follows:
1)linux kernel vision is 2.6.20.13.I compiled Atmel MACB driver as
module.And its network function can run smoothly.
2）RTAI vision is 3.7.RTAI configuration options are:
ARCH=arm
CROSS_COMPILE=arm-linux-
./configure --host=arm-linux
--enable-lxrt-use-linux-syscall
--enable-testsuite
--enable-rtdm
--enable-rtdm-shirq
--enable-rtdm-select.
I compiled RTAI successfully and downloaded it to my target platform. all
the test programs in testsuit directory can run successfully.
3)RTnet vision is 0.9.12.RTnet configuration options are
ARCH=arm
CROSS_COMPILE=/opt/3.4.1/bin/arm-linux-
./configure --host=arm-linux
--with-rtext=/usr/realtime
--with-linux=/home/zhengyi/rtai-porting/linux-2.6.20.13
--with-rtext-config=/usr/realtime/bin/rtai-config
--enable-macb
I have changed a little when compiling rt_macb.c and rt_macb.h. I
loaded rtai_hal,rtai_lxrt,rtai_sem and rtai_rtdm modules in RTAI ,and also
rtnet and tipv4 modules in RTnet.and when I insert rt_macb I got information
as explained in the following sections:
[@NewMsg9263: modules]# insmod rt_macb.ko
RTnet: registered rteth0
MACB_mii_bus: probed
rteth0: Atmel MACB at 0xfffbc000 irq 21 (12:34:56:78:90:12)
rteth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:00,
irq=-1)
[@NewMsg9263: sbin]# ./rtifconfig rteth0 up
it seems the rtifconfig command proper implementation，but after a short
while serial console print following information：
[@NewMsg9263: sbin]# Unable to handle kernel paging request at virtual
address e50b005c
pgd = c3f84000
[e50b005c] *pgd=00000000
Internal error: Oops: 5 [#1]
Modules linked in: rt_macb rtmac rtipv4 rtnet rtai_rtdm rtai_sem rtai_lxrt
rtai_hal
CPU: 0
PC is at qdisc_reset+0x10/0x28
LR is at dev_deactivate+0x24/0xac
pc : [<c0189c08>] lr : [<c0189e60>] Not tainted
sp : c0345eec ip : c0345efc fp : c0345ef8
r10: fffffffc r9 : 00000000 r8 : c0345f14
r7 : c0345f14 r6 : c395982c r5 : c3959800 r4 : c3959800
r3 : e50b002c r2 : c0344000 r1 : 60000013 r0 : bf04a690
Flags: nzCv IRQs on FIQs on Mode SVC_32 Segment kernel
Control: 5317F
Table: 23F84000 DAC: 00000017
Process events/0 (pid: 4, stack limit = 0xc0344250)
Stack: (0xc0345eec to 0xc0346000)
5ee0: c0345f10 c0345efc c0189e60 c0189c08
00000003
5f00: c3959800 c0345f3c c0345f14 c01875fc c0189e4c c0287358 c0287358
c0267dd0
5f20: c0327da0 c0187650 c0254300 c0327da8 c0345f4c c0345f40 c0187698
c0187490
5f40: c0345f70 c0345f50 c0049d5c c0187660 c0327db0 c0327da8 c0327da0
c0345f90
5f60: 00000001 c0345fc0 c0345f74 c0049f40 c0049c7c ffffffff ffffffff
00000001
5f80: 00000000 c0035278 00010000 00000000 00000000 c03393a0 c0035278
00100100
5fa0: 00200200 c0327da0 c0344000 c033bef8 c0049e24 c0345ff4 c0345fc4
c004da90
5fc0: c0049e34 00000001 ffffffff ffffffff 00000000 00000000 00000000
00000000
5fe0: 00000000 00000000 00000000 c0345ff8 c003b484 c004d9b4 06797447
aee165f8
Backtrace:
[<c0189bf8>] (qdisc_reset+0x0/0x28) from [<c0189e60>]
(dev_deactivate+0x24/0xac)
[<c0189e3c>] (dev_deactivate+0x0/0xac) from [<c01875fc>]
(linkwatch_run_queue+0x17c/0x1d0)
r5 = C3959800 r4 = 00000003
[<c0187480>] (linkwatch_run_queue+0x0/0x1d0) from [<c0187698>]
(linkwatch_event+0x48/0x5c)
r8 = C0327DA8 r7 = C0254300 r6 = C0187650 r5 = C0327DA0
r4 = C0267DD0
[<c0187650>] (linkwatch_event+0x0/0x5c) from [<c0049d5c>]
(run_workqueue+0xf0/0x1b8)
[<c0049c6c>] (run_workqueue+0x0/0x1b8) from [<c0049f40>]
(worker_thread+0x11c/0x170)
r8 = 00000001 r7 = C0345F90 r6 = C0327DA0 r5 = C0327DA8
r4 = C0327DB0
[<c0049e24>] (worker_thread+0x0/0x170) from [<c004da90>]
(kthread+0xec/0x11c)
r7 = C0049E24 r6 = C033BEF8 r5 = C0344000 r4 = C0327DA0
[<c004d9a4>] (kthread+0x0/0x11c) from [<c003b484>] (do_exit+0x0/0x7bc)
Code: e1a0c00d e92dd800 e24cb004 e5903010 (e5933030)
<0>Kernel panic - not syncing: Aiee, killing interrupt handler!
It seems that the problem caused by linux kernel instead of RTnet. I
tried to describe my problem in detail.Now i can't find a way to solve my
problem.can you give me some suggestion？
------------------------------------------------------------------------------
Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
user administration capabilities and model configuration. Take
the hassle out of deploying and managing Subversion and the
tools developers use with it.
http://p.sf.net/sfu/wandisco-dev2dev
_______________________________________________
RTnet-users mailing list
RTnet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rtnet-users
