On 23.04.2013 19:18, Jan Kiszka wrote:
Yeah, its hairy:
[ 94.352526] | #*func 0 ipipe_trace_panic_freeze+0x9
(ipipe_root_only+0x62)
[ 94.360774] | #*func 0 ipipe_prepare_panic+0x7
(ipipe_root_only+0x5d)
[ 94.368618] | #*func 0 ipipe_root_only+0x9
(add_preempt_count+0x15)
[ 94.376263] | #*func 0 add_preempt_count+0x9
(_raw_spin_lock_irqsave+0x56)
[ 94.384515] | # func 0 _raw_spin_lock_irqsave+0x7
(swiotlb_tbl_map_single+0x96)
[ 94.392925] | # func -1 __phys_addr+0x4 ( | # func
-1 __phys_addr+0x4 (pci_map_single+0x53 [rt_eepro100])
[ 94.392945] | # func -1 ___xnpod_lock_sched+0x4
(__xnpod_lock_sched+0x21 [rt_eepro100])
[ 94.392954] | + begin 0x80000000 -2 speedo_start_xmit+0x3a
[rt_eepro100] (rtdev_locked_xmit+0x33 [rtnet])
[ 94.392964] + func -2 speedo_start_xmit+0x11 [rt_eepro100]
(rtdev_locked_xmit+0x33 [rtnet])
Now the swiotlb is active, a software IOMMU that helps on systems >4G
RAM with devices that can only DMA to 32-bit addresses (it provides
bounce buffers). You can work around that issue by limiting the memory
used by your system (mem=) or by using an RTnet NIC that does not have
this limitation (rt_e1000e and rt_igb compatible ones).
Yep, that's it, thank you very much.
Does the rt_8139too driver support pre-mapping? Last year, we built a
system with two RTL 8139 and 8 GB of RAM - and did not experience any
such problems since...
Or add pre-mapping support to the rt_e100pro. Check e.g. the conversion of the
e1000e for the pattern. Patches welcome.
I will see what I can do. For now, the system runs on an e1000e.
Regards,
Kai
_______________________________________________
Xenomai mailing list
[email protected]
http://www.xenomai.org/mailman/listinfo/xenomai
