It's better than it was, I can now ping various machines on my local network, and I did get a couple of web pages to load at one point.Skateman wrote:Kernel 5.0 RC6 dpaa patched is running fine on the AmigaOne X5000 but the network issues remain... (thanks anyway guys!! )
I had to unplug and reinsert the ethernet cable to get the network interface going... and did get an ip address by DHCP.
But soon after that, the network traffic died...like it almost always does.
Where did you find your backdrop?
That sounds good!kilaueabart wrote: Not sure that anything I do is "careful testing" but I booted with 5.0-rc5-2-... yesterday and rc6 now. No new problems in either fienix or MATE..
I mean with "careful testing", that you test it longer and that with more devices and programs. The DMA updates affects many devices (drivers) and therefore also programs. I tested the kernel with Bluetooth, TV cards, USB sound cards etc.Great!Skateman wrote:Kernel 5.0 RC6 non dpaa patched is running fine on the AmigaOne X5000
OK. Maybe Darren can solve the issue.Skateman wrote:Kernel 5.0 RC6 dpaa patched is running fine on the AmigaOne X5000 but the network issues remain... (thanks anyway guys!! )
I had to unplug and reinsert the ethernet cable to get the network interface going... and did get an ip address by DHCP.
But soon after that, the network traffic died...like it almost always does.
xeno74 wrote:Hi All,
I tested Christoph's latest Git kernel in a virtual e5500 QEMU machine [1] today. Unfortunately the kernel crashes.
I tested with the following QEMU commands:Code: Select all
[ 54.624330] BUG: Unable to handle kernel data access at 0xc06c008a0013014a [ 54.625640] Faulting instruction address: 0xc000000000027e7c [ 54.626140] Oops: Kernel access of bad area, sig: 11 [#1] [ 54.626456] BE SMP NR_CPUS=4 QEMU e500 [ 54.626876] Modules linked in: [ 54.627284] CPU: 1 PID: 1876 Comm: systemd-journal Not tainted 5.0.0-rc5-DMA_A1-X5000-54581-gda1d065-dirty #1 [ 54.627819] NIP: c000000000027e7c LR: c0000000000b5264 CTR: 0000000000000000 [ 54.628173] REGS: c00000007ffeb700 TRAP: 0300 Not tainted (5.0.0-rc5-DMA_A1-X5000-54581-gda1d065-dirty) [ 54.628607] MSR: 0000000080009000 <EE,ME> CR: 44008486 XER: 00000000 [ 54.629023] DEAR: c06c008a0013014a ESR: 0000000000800000 IRQMASK: 0 [ 54.629023] GPR00: 0000000000005254 c00000007ffeb990 c0000000016b2000 c06c008a0013014a [ 54.629023] GPR04: c00000007c54f8c0 0000000000000058 0000000000000006 0000000000000000 [ 54.629023] GPR08: 0000000000000000 000000007c54f8c0 006c008a0013014a c00000007c86c000 [ 54.629023] GPR12: 0000000028002482 c00000003ffff8c0 0000000000000000 c000000078dfaa70 [ 54.629023] GPR16: c000000078366c00 0000000000000000 000000000000005e 0000000000000000 [ 54.629023] GPR20: 0000000000000000 c00000007c54f8c0 0000000000000007 c000000078dfa000 [ 54.629023] GPR24: 0000000000000000 0000000000000047 0000000000000000 80000000003f6470 [ 54.629023] GPR28: c00000007928d470 c000000078801dc0 000000000000005e c000000078dfa7c0 [ 54.632572] NIP [c000000000027e7c] .memcpy+0x1fc/0x288 [ 54.632886] LR [c0000000000b5264] .swiotlb_tbl_sync_single+0xb0/0xe4 [ 54.633221] Call Trace: [ 54.633513] [c00000007ffeb990] [c00000007ffeba70] 0xc00000007ffeba70 (unreliable) [ 54.633988] [c00000007ffeba00] [c0000000000b41e4] .dma_direct_sync_single_for_cpu+0x58/0x6c [ 54.634436] [c00000007ffeba70] [c000000000788da4] .e1000_clean_rx_irq+0x1bc/0x4c8 [ 54.634857] [c00000007ffebb90] [c00000000078667c] .e1000_clean+0x714/0x8d4 [ 54.635263] [c00000007ffebcc0] [c000000000a3f15c] .net_rx_action+0x11c/0x2a4 [ 54.635712] [c00000007ffebdb0] [c000000000c48c20] .__do_softirq+0x150/0x2a8 [ 54.636211] [c00000007ffebeb0] [c000000000064184] .irq_exit+0x6c/0xc4 [ 54.636533] [c00000007ffebf20] [c000000000004124] .__do_irq+0x80/0x94 [ 54.636985] [c00000007ffebf90] [c00000000000eca0] .call_do_irq+0x14/0x24 [ 54.637371] [c00000007c86fd80] [c0000000000041c0] .do_IRQ+0x88/0xc4 [ 54.637737] [c00000007c86fe20] [c000000000012920] exc_0x500_common+0xd8/0xdc [ 54.638104] Instruction dump: [ 54.638451] e861fff8 4e800020 7cd01120 7ca62850 38e00000 28a50010 409f0010 88040000 [ 54.638887] 98030000 38e70001 409e0010 7c07222e <7c071b2e> 38e70002 409d000c 7c07202e [ 54.639594] ---[ end trace a4861de7e4c199f7 ]--- [ 54.639873] [ 55.640484] Kernel panic - not syncing: Aiee, killing interrupt handler! [ 55.641556] Rebooting in 180 seconds..
Code: Select all
./qemu-system-ppc64 -M ppce500 -cpu e5500 -m 2048 -nographic -kernel /home/christian/Downloads/vmlinux-5.0-rc5-2-AmigaOne_X1000_X5000/X5000_and_QEMU_e5500/uImage-5.0 -nic user,model=e1000 -drive format=raw,file=/home/christian/Downloads/MATE_PowerPC_Remix_2017_0.9.img,index=0,if=virtio -append "rw root=/dev/vda" -smp 4[1] Gitweb: powerpc-dma.6Code: Select all
./qemu-system-ppc64 -M ppce500 -cpu e5500 -m 2048 -kernel /home/christian/Downloads/vmlinux-5.0-rc5-2-AmigaOne_X1000_X5000/X5000_and_QEMU_e5500/uImage-5.0 -drive format=raw,file=/home/christian/Downloads/MATE_PowerPC_Remix_2017_0.9.img,index=0,if=virtio -nic user,model=e1000 -append "rw root=/dev/vda" -device virtio-vga -device virtio-mouse-pci -device virtio-keyboard-pci -usb -soundhw es1370 -smp 4
Cheers,
Christian
Christoph Hellwig wrote: This looks like a patch I fixed in mainline a while ago, but which
the powerpc tree didn't have yet.
I've cherry picked this commit
("swiotlb: clear io_tlb_start and io_tlb_end in swiotlb_exit")
and added it to the powerpc-dma.6 tree, please retry with that one.
daz wrote:It's better than it was, I can now ping various machines on my local network, and I did get a couple of web pages to load at one point.Skateman wrote:Kernel 5.0 RC6 dpaa patched is running fine on the AmigaOne X5000 but the network issues remain... (thanks anyway guys!! )
I had to unplug and reinsert the ethernet cable to get the network interface going... and did get an ip address by DHCP.
But soon after that, the network traffic died...like it almost always does.
I am fairly sure that this is a memory issue, as you've seen, it works for a short time then dies. I will have to take a look and see if there is anymore initialisation code in the pamu driver I need to port across.
This code I'm adding is from the SDK Linux version of the driver, I suspect it wasn't ported to mainline due to updates made to U-Boot, and I think we'll get told to update U-Boot if we try to get this code added. Feel free to hassle Matthew (AmigaKit) about this
Where did you find your backdrop?
Regards
Darren
Christian Zigotzky wrote: Hi Christoph
Many thanks! Your Git kernel works in a virtual e5500 machine now!
I think we have reached the end of testing! All things are working with your DMA updates.
I am looking forward to testing your DMA changes in the next merge window again.
Cheers
Christian
Unfortunately it isn't possible because there are some differences between X1000 and X5000 for example KVM and AltiVec.caseycullen wrote:Christian,
Is there a version of the kernel_modules that can be placed in lib/modules that will work on X1000 and X5000 or is it possible to make one?
-Casey
IIRC, if you give the kernels different local names, this changes where the kernel looks for modules, so you could have 2 sets of modules, one for the X1000 and one for the X5000 installed at the same time, and each kernel would only load it's own modules.xeno74 wrote:Unfortunately it isn't possible because there are some differences between X1000 and X5000 for example KVM and AltiVec.caseycullen wrote:Christian,
Is there a version of the kernel_modules that can be placed in lib/modules that will work on X1000 and X5000 or is it possible to make one?
-Casey
-- Christian
We have finished the testing of the DMA updates.
