Overo P-COMs slow to boot with 4.8 or 4.9 kernels

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Overo P-COMs slow to boot with 4.8 or 4.9 kernels

Gumstix mailing list
The system takes 2 minutes to get to a login prompt on the console.

A Y-COM takes ~12 seconds using the same SD card on the same Tobi board.

I get these mmc messages while booting

[   67.969146] udevd[880]: worker [891]
/devices/platform/68000000.ocp/480b4000.mmc/mmc_host/mmc1/mmc1:0001/mmc1:0001:1
is taking a long time
[   67.982299] udevd[880]: worker [885]
/devices/platform/68000000.ocp/480b4000.mmc/mmc_host/mmc1/mmc1:0001/mmc1:0001:2
is taking a long time
[   67.995422] udevd[880]: worker [890]
/devices/platform/68000000.ocp/480b4000.mmc/mmc_host/mmc1/mmc1:0001/mmc1:0001:3
is taking a long time

480b4000.mmc is the mmc the radio is attached to.

The 4.8 kernel is from github.com/gumstix/linux.

The 4.9.32 kernel is from linux-stable with some omap3-overo dts updates for
the wifi chips taken from the Gumstix 4.8 repo.

If I blacklist the Marvell Bluetooth drivers, the P-COM comes up as quickly
as the Y-COM.

root@overo:~# cat /etc/modprobe.d/blacklist.conf
install btmrvl_sdio /bin/false
install btmrvl /bin/false

root@overo:~# lsmod
Module                  Size  Used by
ipv6                  422272  16
bnep                   11394  2
mwifiex_sdio           25788  0
mwifiex               265678  1 mwifiex_sdio
cfg80211              531422  1 mwifiex
bluetooth             392305  7 bnep
rfkill                 20367  4 bluetooth,cfg80211
twl4030_madc            9759  0
industrialio           35244  1 twl4030_madc


I haven't worked with the Overo radios in awhile.

Is this a known issue?

I know with the 3.18 kernels, the P-COM bluetooth drivers took about
20 seconds to load firmware.

Wifi performance with the Y-COM using the 4.9 kernel is terrible
compared to the P-COM.

I didn't check performance with the 4.8 kernel.

Y-COM

Receiving
[ ID] Interval           Transfer     Bandwidth
[  5]   0.00-60.26  sec  0.00 Bytes  0.00 bits/sec            sender
[  5]   0.00-60.26  sec  4.71 MBytes   655 Kbits/sec          receiver

Sending
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-60.00  sec  5.51 MBytes   770 Kbits/sec    0     sender
[  4]   0.00-60.00  sec  5.48 MBytes   766 Kbits/sec          receiver


P-COM

Receiving
[ ID] Interval           Transfer     Bandwidth
[  5]   0.00-60.36  sec  0.00 Bytes  0.00 bits/sec            sender
[  5]   0.00-60.36  sec  43.3 MBytes  6.01 Mbits/sec          receiver

Sending
[ ID] Interval           Transfer     Bandwidth       Retr
[  4]   0.00-60.00  sec  71.0 MBytes  9.93 Mbits/sec    0     sender
[  4]   0.00-60.00  sec  70.9 MBytes  9.91 Mbits/sec          receiver

Any ideas?



--
View this message in context: http://gumstix.8.x6.nabble.com/Overo-P-COMs-slow-to-boot-with-4-8-or-4-9-kernels-tp4971361.html
Sent from the Gumstix mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Reply | Threaded
Open this post in threaded view
|

Re: Overo P-COMs slow to boot with 4.8 or 4.9 kernels

Gumstix mailing list
Answering my own question, reverting this commit to btmrvl_sdio.c gets the
system back to the ~20 second delay for the bluetooth drivers instead of 2
minutes.

commit 9a01242dc7fc4d5fe3f722afbf35b33aa414cd2f
Author: Wei-Ning Huang <[hidden email]>
Date:   Tue Mar 8 11:40:06 2016 +0800

    Bluetooth: btmrvl_sdio: fix firmware activation failure

    In some case, the btmrvl_sdio firmware would fail to active within the
    polling time. Increase the polling interval to 100 msec to fix the
    issue.

    Signed-off-by: Wei-Ning Huang <[hidden email]>
    Signed-off-by: Wei-Ning Huang <[hidden email]>
    Signed-off-by: Marcel Holtmann <[hidden email]>

diff --git a/drivers/bluetooth/btmrvl_sdio.c
b/drivers/bluetooth/btmrvl_sdio.c
index 6ed8acf..c6ef248 100644
--- a/drivers/bluetooth/btmrvl_sdio.c
+++ b/drivers/bluetooth/btmrvl_sdio.c
@@ -371,7 +371,7 @@ static int btmrvl_sdio_verify_fw_download(struct
btmrvl_sdio_card *card,
                if (firmwarestat == FIRMWARE_READY)
                        return 0;

-               msleep(10);
+               msleep(100);
        }

        return -ETIMEDOUT;




--
View this message in context: http://gumstix.8.x6.nabble.com/Overo-P-COMs-slow-to-boot-with-4-8-or-4-9-kernels-tp4971362p4971368.html
Sent from the Gumstix mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Reply | Threaded
Open this post in threaded view
|

Re: Overo P-COMs slow to boot with 4.8 or 4.9 kernels

Scott Ellis
This post has NOT been accepted by the mailing list yet.
In reply to this post by Gumstix mailing list
Answering my own question, reverting this commit to btmrvl_sdio.c gets the system back to the ~20 second delay for the bluetooth drivers instead of 2 minutes.

commit 9a01242dc7fc4d5fe3f722afbf35b33aa414cd2f
Author: Wei-Ning Huang <wnhuang@chromium.org>
Date:   Tue Mar 8 11:40:06 2016 +0800

    Bluetooth: btmrvl_sdio: fix firmware activation failure

    In some case, the btmrvl_sdio firmware would fail to active within the
    polling time. Increase the polling interval to 100 msec to fix the
    issue.

    Signed-off-by: Wei-Ning Huang <wnhuang@chromium.org>
    Signed-off-by: Wei-Ning Huang <wnhuang@google.com>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

diff --git a/drivers/bluetooth/btmrvl_sdio.c b/drivers/bluetooth/btmrvl_sdio.c
index 6ed8acf..c6ef248 100644
--- a/drivers/bluetooth/btmrvl_sdio.c
+++ b/drivers/bluetooth/btmrvl_sdio.c
@@ -371,7 +371,7 @@ static int btmrvl_sdio_verify_fw_download(struct btmrvl_sdio_card *card,
                if (firmwarestat == FIRMWARE_READY)
                        return 0;

-               msleep(10);
+               msleep(100);
        }

        return -ETIMEDOUT;
Reply | Threaded
Open this post in threaded view
|

Re: Overo P-COMs slow to boot with 4.8 or 4.9 kernels

Scott Ellis
This post has NOT been accepted by the mailing list yet.
And this patch removes the 20 second delay for the btmrvl driver.

Its for initialization that always fails on the Overos anyway.

https://github.com/jumpnow/meta-overo/blob/pyro/recipes-kernel/linux/linux-stable-4.9/0005-btmrvl-Avoid-unnecessary-initialization.patch

The systems now boot under 15 seconds with a dhcp address on wifi and bluetooth up and running.

These are for a 4.9.34 LTS kernel.

I've been testing only with Overo Storm P-COMs since that's what this particular customer project is using.

There are some additional patches for wifiex in that repo to eliminate some unsupported commands to the wifi chip that just cause noise in the syslog.

None of this should affect the Y-COMs since they are only btmrvl or mwifiex driver changes.

Reply | Threaded
Open this post in threaded view
|

Re: Overo P-COMs slow to boot with 4.8 or 4.9 kernels

Gumstix mailing list
In reply to this post by Scott Ellis
And this patch removes the 20 second delay for the btmrvl driver.

Its for initialization that always fails on the Overos anyway.

https://github.com/jumpnow/meta-overo/blob/pyro/recipes-kernel/linux/linux-stable-4.9/0005-btmrvl-Avoid-unnecessary-initialization.patch

The systems now boot under 15 seconds with a dhcp address on wifi and
bluetooth up and running.

These are for a 4.9.34 LTS kernel.

I've been testing only with Overo Storm P-COMs since that's what this
particular customer project is using.

There are some additional patches for wifiex in that repo to eliminate some
unsupported commands to the wifi chip that just cause noise in the syslog.

None of this should affect the Y-COMs since they are only btmrvl or mwifiex
driver changes.





--
View this message in context: http://gumstix.8.x6.nabble.com/Overo-P-COMs-slow-to-boot-with-4-8-or-4-9-kernels-tp4971362p4971386.html
Sent from the Gumstix mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users