Kernel 4.15

AmigaOne X5000 platform specific issues related to Linux only.

Re: Kernel 4.15

Postby xeno74 » Tue Jan 16, 2018 7:16 am

Result2

— Christian
http://www.amigalinux.org
http://www.supertuxkart-amiga.de

Running Linux on AmigaONEs can require some tinkering.
User avatar
xeno74
 
Posts: 3651
Joined: Fri Mar 23, 2012 8:58 am

Re: Kernel 4.15

Postby xeno74 » Tue Jan 16, 2018 10:49 pm

Madalin-cristian Bucur wrote:The PAMU related errors may be relevant to the issue, if you have incorrect
settings you may have no traffic passing through. The PAMU configuration
should be made by the bootloader. Can you try to disable CONFIG_FSL_PAMU?

Madalin


Hi All,

I compiled the RC8 of kernel 4.15 for the X5000 without PAMU support today.

Download: uImage_without_pamu.tar.gz

Please test it on your AmigaOne X5000.

Thanks,
Christian
http://www.amigalinux.org
http://www.supertuxkart-amiga.de

Running Linux on AmigaONEs can require some tinkering.
User avatar
xeno74
 
Posts: 3651
Joined: Fri Mar 23, 2012 8:58 am

Re: Kernel 4.15

Postby Skateman » Tue Jan 16, 2018 11:40 pm

Yess...... we have progress...

I had to give the Eth0 a manual IP due to not responding on DHCP requests.
Anyway..

I can ping my Gateway, and even DNS queries work..

But when i start Netsurf (or generate to much packets)... all traffic dies.... due to No buffer space available..

64 bytes from 192.168.22.66: icmp_seq=81 ttl=255 time=0.317 ms
64 bytes from 192.168.22.66: icmp_seq=82 ttl=255 time=0.317 ms
64 bytes from 192.168.22.66: icmp_seq=83 ttl=255 time=0.314 ms
64 bytes from 192.168.22.66: icmp_seq=84 ttl=255 time=0.321 ms
64 bytes from 192.168.22.66: icmp_seq=85 ttl=255 time=0.323 ms
64 bytes from 192.168.22.66: icmp_seq=86 ttl=255 time=0.312 ms
64 bytes from 192.168.22.66: icmp_seq=87 ttl=255 time=0.331 ms
64 bytes from 192.168.22.66: icmp_seq=88 ttl=255 time=0.338 ms
64 bytes from 192.168.22.66: icmp_seq=89 ttl=255 time=0.334 ms
64 bytes from 192.168.22.66: icmp_seq=90 ttl=255 time=0.349 ms
64 bytes from 192.168.22.66: icmp_seq=91 ttl=255 time=0.324 ms
64 bytes from 192.168.22.66: icmp_seq=92 ttl=255 time=0.320 ms
64 bytes from 192.168.22.66: icmp_seq=93 ttl=255 time=0.320 ms
64 bytes from 192.168.22.66: icmp_seq=94 ttl=255 time=0.338 ms
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available

i found this...
Chances are it's a problem with the driver. Basically the output queue is full and unless you are handling some major network traffic or have a ton of hosts on the network you shouldn't see that error, and if you were, you could probably tweak some kernel values to prevent the error.

We are getting closer :-)

A workaround to keep the nic alive a bit longer.... is the following command
ip link set eth0 qlen 10000
Last edited by Skateman on Wed Jan 17, 2018 12:38 pm, edited 1 time in total.
User avatar
Skateman
 
Posts: 140
Joined: Thu Aug 10, 2017 9:36 pm
Location: The Netherlands

Re: Kernel 4.15

Postby xeno74 » Wed Jan 17, 2018 7:59 am

Hi Skateman,

Fantastic! Many thanks for testing the RC8 of kernel 4.15 without PAMU support.

Cheers,
Christian
http://www.amigalinux.org
http://www.supertuxkart-amiga.de

Running Linux on AmigaONEs can require some tinkering.
User avatar
xeno74
 
Posts: 3651
Joined: Fri Mar 23, 2012 8:58 am

Re: Kernel 4.15

Postby JamieKrueger » Thu Jan 18, 2018 3:39 am

My tests on the X5000/20 with 4.15.0-rc8 (w/CONFIG_FSL_PAMU disabled) shows
the same kind of progress seen by Skateman's testing. My results vary somewhat, but
I believe there are other factors at play which account for the slightly different results
(I suspect mostly timing issues).

For example, in my tests I can now get the interface to obtain an IP Address via DHCP,
at least part of the time that is. Here is a screenshot of a Wireshark capture which
shows a successful DHCP request/response for the X5000/20, followed by some failed
ping attempts.

Image
(This traffic was captured on an external machine on the same subnet, and not from the X5000/20 itself)
Here is a link to the export of the packet data shown in the above image: Full packet breakdown.

As you can see by this example, even when the interface does obtain an IP address via
DHCP (about half the time), subsequent traffic still fails to receive responses.

In this example, I attempt to ping the gateway (192.168.1.1), and one or two other
local addresses, and nothing pings back (even when trying Skateman's suggestion
of expanding the buffers for the interface).
Skateman wrote: A workaround to keep the nic alive a bit longer.... is the following command
ip link set eth0 qlen 10000


As far as the dmesg output, it appears cleaner now;
here are all the Freescale(fsl) related messages I get now:
Code: Select all
[    0.000000] OF: reserved mem: initialized node qman-fqd, compatible id fsl,qman-fqd
[    0.000000] OF: reserved mem: initialized node qman-pfdr, compatible id fsl,qman-pfdr
[    0.000000] OF: reserved mem: initialized node bman-fbpr, compatible id fsl,bman-fbpr
[    0.053008] fsl-pci ffe200000.pcie: PCI host bridge to bus 0000:00
[    0.056385] fsl-pci ffe201000.pcie: PCI host bridge to bus 1000:00
[    0.080433] fsl-of-rio ffe0c0000.rapidio: Of-device full name /rapidio@ffe0c0000
[    0.080442] fsl-of-rio ffe0c0000.rapidio: Regs: [mem 0xffe0c0000-0xffe0d0fff]
[    0.080454] fsl-of-rio ffe0c0000.rapidio: No valid fsl,srio-rmu-handle property
[    0.080470] fsl-of-rio: probe of ffe0c0000.rapidio failed with error -2
[    0.230143] fsl-elo-dma ffe100300.dma: #0 (fsl,eloplus-dma-channel), irq 28
[    0.230184] fsl-elo-dma ffe100300.dma: #1 (fsl,eloplus-dma-channel), irq 29
[    0.230222] fsl-elo-dma ffe100300.dma: #2 (fsl,eloplus-dma-channel), irq 30
[    0.230260] fsl-elo-dma ffe100300.dma: #3 (fsl,eloplus-dma-channel), irq 31
[    0.230485] fsl-elo-dma ffe101300.dma: #0 (fsl,eloplus-dma-channel), irq 32
[    0.230523] fsl-elo-dma ffe101300.dma: #1 (fsl,eloplus-dma-channel), irq 33
[    0.230563] fsl-elo-dma ffe101300.dma: #2 (fsl,eloplus-dma-channel), irq 34
[    0.230601] fsl-elo-dma ffe101300.dma: #3 (fsl,eloplus-dma-channel), irq 35
[    4.709339] fsl-sata ffe220000.sata: Sata FSL Platform/CSB Driver init
[    4.709734] scsi host4: sata_fsl
[    4.709989] fsl-sata ffe221000.sata: Sata FSL Platform/CSB Driver init
[    4.710369] scsi host5: sata_fsl
[    4.711608] fsl_espi ffe110000.spi: at 0x        (ptrval) (irq = 53)
[    4.739590] fsl_dpaa_mac ffe4e6000.ethernet: FMan dTSEC version: 0x08240101
[    4.743879] fsl_dpaa_mac ffe4e6000.ethernet: FMan MAC address: 00:80:10:11:11:11
[    4.748136] fsl_dpaa_mac ffe4e8000.ethernet: FMan dTSEC version: 0x08240101
[    4.752461] fsl_dpaa_mac ffe4e8000.ethernet: FMan MAC address: 00:80:10:22:22:22
[    4.756674] fsl_dpaa_mac ffe4e0000.ethernet: of_get_mac_address(/soc@ffe000000/fman@400000/ethernet@e0000) failed
[    4.760954] fsl_dpaa_mac: probe of ffe4e0000.ethernet failed with error -22
[    4.765324] fsl_dpaa_mac ffe4e2000.ethernet: of_get_mac_address(/soc@ffe000000/fman@400000/ethernet@e2000) failed
[    4.769799] fsl_dpaa_mac: probe of ffe4e2000.ethernet failed with error -22
[    4.774277] fsl_dpaa_mac ffe4e4000.ethernet: of_get_mac_address(/soc@ffe000000/fman@400000/ethernet@e4000) failed
[    4.778897] fsl_dpaa_mac: probe of ffe4e4000.ethernet failed with error -22
[    4.783587] fsl_dpaa_mac ffe4f0000.ethernet: of_get_mac_address(/soc@ffe000000/fman@400000/ethernet@f0000) failed
[    4.788414] fsl_dpaa_mac: probe of ffe4f0000.ethernet failed with error -22
[    4.795390] fsl_dpaa_mac ffe4e6000.ethernet eth0: Probed interface eth0
[    4.802355] fsl_dpaa_mac ffe4e8000.ethernet eth1: Probed interface eth1
[    4.870506] ehci-fsl: Freescale EHCI Host controller driver
[    4.896374] fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
[    4.901654] fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
[    4.916527] fsl-ehci fsl-ehci.0: irq 44, io mem 0xffe210000
[    4.927829] fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00
[    4.954474] usb usb1: SerialNumber: fsl-ehci.0
[    4.970693] fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
[    4.976117] fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2
[    4.991216] fsl-ehci fsl-ehci.1: irq 45, io mem 0xffe211000
[    5.002827] fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
[    5.040763] usb usb2: SerialNumber: fsl-ehci.1
[    5.314826] usb 1-1: new high-speed USB device number 2 using fsl-ehci
[    5.347646] fsl-hv: no hypervisor found
[    5.385831] usb 2-1: new high-speed USB device number 2 using fsl-ehci
[    5.852850] usb 2-1.4: new high-speed USB device number 3 using fsl-ehci
[    5.978071] usb 1-1.1: new low-speed USB device number 3 using fsl-ehci
[    6.109571] input: CHICONY USB Keyboard as /devices/platform/ffe000000.soc/ffe210000.usb/fsl-ehci.0/usb1/1-1/1-1.1/1-1.1:1.0/0003:04F2:0116.0001/input/input1
[    6.167144] hid-generic 0003:04F2:0116.0001: input,hidraw0: USB HID v1.10 Keyboard [CHICONY USB Keyboard] on usb-fsl-ehci.0-1.1/input0
[    6.248828] usb 1-1.3: new low-speed USB device number 4 using fsl-ehci
[    6.355611] input: Logitech USB-PS/2 Optical Mouse as /devices/platform/ffe000000.soc/ffe210000.usb/fsl-ehci.0/usb1/1-1/1-1.3/1-1.3:1.0/0003:046D:C050.0002/input/input2
[    6.355781] hid-generic 0003:046D:C050.0002: input,hidraw1: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-fsl-ehci.0-1.3/input0
[   55.555491] [c0000001ffbcfbc0] [c00000000002c8b4] .fsl_error_int_handler+0xac/0xf4
Best Regards,

Jamie Krueger
BITbyBIT Software Group LLC
User avatar
JamieKrueger
Beta Tester
Beta Tester
 
Posts: 10
Joined: Mon Dec 20, 2010 8:15 pm

Re: Kernel 4.15

Postby xeno74 » Thu Jan 18, 2018 9:46 am

Hi Jamie,

Many thanks for your effort. If you need a new kernel for testing please let me know.

Cheers,
Christian
http://www.amigalinux.org
http://www.supertuxkart-amiga.de

Running Linux on AmigaONEs can require some tinkering.
User avatar
xeno74
 
Posts: 3651
Joined: Fri Mar 23, 2012 8:58 am

Re: Kernel 4.15

Postby xeno74 » Thu Jan 18, 2018 10:34 am

Hi All,

Could you please post the output of /sys/devices/system/cpu/vulnerabilities/?

Code: Select all
ls -l /sys/devices/system/cpu/vulnerabilities/


Image

Thanks,
Christian
http://www.amigalinux.org
http://www.supertuxkart-amiga.de

Running Linux on AmigaONEs can require some tinkering.
User avatar
xeno74
 
Posts: 3651
Joined: Fri Mar 23, 2012 8:58 am

Re: Kernel 4.15

Postby Skateman » Fri Jan 19, 2018 3:16 pm

root@X5000LNX:/home/skateman# ls -l /sys/devices/system/cpu/vulnerabilities/
ls: cannot access '/sys/devices/system/cpu/vulnerabilities/': No such file or directory

Checked for a Vulnerabilities folder... but does not exists
User avatar
Skateman
 
Posts: 140
Joined: Thu Aug 10, 2017 9:36 pm
Location: The Netherlands

Re: Kernel 4.15

Postby Skateman » Fri Jan 19, 2018 3:54 pm

@xeno74

xeno74 wrote:Hi Jamie,

Many thanks for your effort. If you need a new kernel for testing please let me know.

Cheers,
Christian


I think we need a kernel with a more stable driver... there is a lot of patching going on regarding this NIC driver.
http://patchwork.ozlabs.org/project/net ... 62&state=*
User avatar
Skateman
 
Posts: 140
Joined: Thu Aug 10, 2017 9:36 pm
Location: The Netherlands

Re: Kernel 4.15

Postby xeno74 » Fri Jan 19, 2018 4:49 pm

Skateman wrote:root@X5000LNX:/home/skateman# ls -l /sys/devices/system/cpu/vulnerabilities/
ls: cannot access '/sys/devices/system/cpu/vulnerabilities/': No such file or directory

Checked for a Vulnerabilities folder... but does not exists


Hi Skateman,

Many thanks for checking the path.

Cheers,
Christian
http://www.amigalinux.org
http://www.supertuxkart-amiga.de

Running Linux on AmigaONEs can require some tinkering.
User avatar
xeno74
 
Posts: 3651
Joined: Fri Mar 23, 2012 8:58 am

PreviousNext

Return to Platform: AmigaOne X5000 - Linux Only

Who is online

Users browsing this forum: No registered users and 1 guest