LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM
User Name
Password
Slackware - ARM This forum is for the discussion of Slackware ARM.

Notices


Reply
  Search this Thread
Old 07-08-2017, 10:46 AM   #1
abga
LQ Newbie
 
Registered: Jul 2017
Location: EU
Distribution: Slackware x86 & ARM
Posts: 4

Rep: Reputation: 1
USB issues under the new 2017-07-05 Raspbian official kernel 4.9.28-v7+ on Slackware ARM


Greetings Earthlings,

I'd like to start by thanking all of the Slackers for helping me out with their work in my last 17 years of continuous "slacking", the last 2 also on ARM.

I'm using Slack ARM current HF on a bunch of Raspberry Pi2 & Zero devices and have been updating my kernel & firmware always directly from the Raspbian official images (once they were released) for the last 2 years.

By my last update with the 2017-07-05 Raspbian image, I've stumbled upon some peculiar issues with the USB bus and failed to identify the cause. I've asked for help on the Raspberry Forums and made a big mistake by telling them that I'm not using Raspbian but Slack and that I don't really trust Debian derivatives for my needs. I got a bored moderator on a brink of resigning together with his trolls and came here to ask if someone has had the same experience like me with the new kernel 4.9.28v7+.
I've documented my problem both on the Kodi Forum - under ABGA:
https://forum.kodi.tv/showthread.php?tid=267284
And on the Raspberry Forum under justme123 (actually banned for the impertinence to ask for help and being a hardcore Slacker, not to mention - asking Santa Claus to put his glasses on):
https://www.raspberrypi.org/forums/v...?f=63&t=187697

Just for the sake of consistency and completion I'm also inserting (copy/paste) here the original problem description from the Raspberry Forum:

I'm not using Raspbian myself and just took the firmware&kernel from the latest image dated 2017-07-05, which comes with kernel 4.9.28-v7+ and Firmware: May 15 2017 16:57:15, version 9469ea3706e34c4de62f38a5008f69a429b4b43e (clean) (release)
Just for information, I make whole SDCard backups between the kernel updates and just updating the firmware and kernel (/opt/vc included) once they are released. The configuration files and packages are being kept in the same state/version (preserved), I only start to modify/upgrade them after making sure that the new kernel is OK.The last kernel I was using without any issues was the previously released 4.4.50-v7+.

Among other interesting things, I use one of my Pi 2 B boards for streaming video through tvheadend from an usb DVB-S2 adapter. The only part I'm compiling myself (updating the kernel modules) is the media_tree (linuxtv.org) because I need to patch a tuner file.
With the latest kernel & firmware from 2017-07-05 I experience issues with tvheadend (launched with non-root privileges), which is bragging every minute in syslog that it's getting DVB stream continuity errors from the usb DVB adapter:
tvheadend[19131]: TS: Astra/11347V/ZDFinfo HD: H264 @ #6710 Continuity counter error (total 14)
tvheadend[19131]: TS: Astra/11347V/ZDFinfo HD: AC3 @ #6722 Continuity counter error (total 11)
tvheadend[19131]: TS: Astra/11347V/ZDFinfo HD: MPEG2AUDIO @ #6720 Continuity counter error (total 10)
and eventually stops streaming as the errors frequency is getting worse. It works again for a while after I restart the tvheadend process.

My CPU frequency governor is set on ondemand (only under very intensive usage is jumping from 600-900Mhz) and if I tune it on performance (CPU frequency will stay at 900Mhz) the tvheadend errors are almost disappearing - I get one every 10-20 minutes.
The CPU temperature is usually at 45C in idle mode, 50-60C when streaming and only while compiling I get between 65-70C.
By trying to identify the cause of this real-time streaming issue with the new kernel& firmware, I stumbled upon an old tvheadend thread, not ARM related, which suggest that CPU throttling might be a valid cause:
https://tvheadend.org/boards/5/topics/8502?r=8790

Just by trying to exclude the media_tree (media_build) from the equation, I have recompiled it (the latest git release) under the older backup image (older firmware & 4.4.50-v7+ kernel) and I was not experiencing any issues.

The kernel being the only component that I have changed and not fully investigated yet, I believe that the issue is somewhere in the new usb subsystem / modules.

I'm also considering to start my own kernel compilation with this latest experience and looking for an ARM toolchain under x86.

Thank you in advance!

Off-Topic, there are some General Raspberry kernel related threads at the Raspberry Forums that you might find informative (that's from when I was still able to find help):
https://www.raspberrypi.org/forums/v...?f=63&t=182116
https://www.raspberrypi.org/forums/v...f=107&t=187222
And on the Kodi Forums, if you look for compiling Kodi, FFmpeg, etc on Slackware, search for my nickname ABGA - or simply ask me, now that I'm registered - Always happy to help Slackers!
 
Old 07-10-2017, 01:36 PM   #2
abga
LQ Newbie
 
Registered: Jul 2017
Location: EU
Distribution: Slackware x86 & ARM
Posts: 4

Original Poster
Rep: Reputation: 1
Hi,

I've got some time today and searched in the official 2017-07-05 Raspbian Image after new /boot/config.txt&cmdline.txt / modules parameters / udev rules that might have been the cause for my reported issue. I couldn't find anything new or special in comparison to the previously released Raspbian Image with kernel 4.4.50

However, I've identified several outstanding USB related issues with the 4.9 kernel branch on Raspberry's git and if you look for stability, I'd advise to stick with the 4.4.50 kernel for the moment, as it is confirmed as stable even by the ones that reported the issues with the new 4.9 branch:

https://github.com/raspberrypi/linux/issues/1943
https://github.com/raspberrypi/linux/issues/2097
https://github.com/raspberrypi/linux/issues/2026

As a side note, kernels previous to 4.4.50 are affected by this issue (I can confirm it for 4.4.34 & 4.4.48):
https://github.com/raspberrypi/linux/issues/1753

I'll stick with 4.4.50 for the moment and will stall the investigation on 4.9 - as there are several confirmed USB issues with this branch.

Regarding a Slackware x86-64 Raspberry Pi kernel cross-compilation environment, I'm still studying/learning from the google results I've found.
I'd be thankful if anyone could help me be more efficient by pointing me at a tested Slackware "recipe", if such a recipe exists.

Thanks!

Last edited by abga; 07-10-2017 at 01:38 PM.
 
1 members found this post helpful.
Old 07-12-2017, 07:12 AM   #3
Exaga
Member
 
Registered: Nov 2012
Distribution: Slackware Linux
Posts: 77

Rep: Reputation: 50
Quote:
Originally Posted by abga View Post
Hi,

https://github.com/raspberrypi/linux/issues/1753

I'll stick with 4.4.50 for the moment and will stall the investigation on 4.9 - as there are several confirmed USB issues with this branch.
I haven't noticed any USB issues under the 4.9 kernel running Slackware ARM. That's not to say there aren't any, just that I haven't experienced any issues in the months I've been using the 4.9 kernel.

Quote:
Originally Posted by abga View Post
Regarding a Slackware x86-64 Raspberry Pi kernel cross-compilation environment, I'm still studying/learning from the google results I've found.
I'd be thankful if anyone could help me be more efficient by pointing me at a tested Slackware "recipe", if such a recipe exists.
These days, when it comes to cross-compiling for ARM architecture I refer to this FAQ by Mozes.
 
Old 07-12-2017, 11:49 AM   #4
abga
LQ Newbie
 
Registered: Jul 2017
Location: EU
Distribution: Slackware x86 & ARM
Posts: 4

Original Poster
Rep: Reputation: 1
@Exaga

Thank you for your feedback, and cross-compiler hints.

Kernel related:
I'm using a Pi2B board as a testbed on my desk, running several services(Firewall,Snort,VPN,DNS Resolver,PostgreSQL,Kodi...etc), monitored by the help of Monitorix and having 3 USB ports always directly connected. A DVBS2 USB adapter (max 20Mbps), a 3G USB dongle for Internet fail-over (max 21Mbps) and an USB Card Reader(16GB Sandisk SDCard) for the PostgreSQL db storage (older type that is not supporting write speeds over 4-5MB/s and reads over 10MB/s). The Ethernet (which is also connected internally on the USB bus), the DVB-S2 and the Card Reader are active and servicing 24/7. It's in this environment that I observe USB issues and not on other boards that are more "relaxed". As stated, I'm happy with 4.4.50


Cross-Compiler related:

Thanks again for pointing me to that Q&A link, I don't know why I missed it, maybe because I was focusing solely on kernel compilation.

I was asking for help because I got confused by the multiple choices I have with respect to toolchains:
http://elinux.org/Toolchains#Getting_a_toolchain

And by the fact that most of the Raspberry kernel compilation recipes I've found on the Internet are advising to use the "official" and "optimized" linaro toolchain that Rapberry itself is using:
https://github.com/raspberrypi/tools

But all these should be part of a new thread, as they are off-topic here. I'll maybe start a thread and document a Raspberry kernel compilation recipe on Slackware, once I'll learn my lessons and become more confident.
 
Old 07-13-2017, 05:08 AM   #5
Exaga
Member
 
Registered: Nov 2012
Distribution: Slackware Linux
Posts: 77

Rep: Reputation: 50
Quote:
Originally Posted by abga View Post
@Exaga

Thank you for your feedback, and cross-compiler hints.

Thanks again for pointing me to that Q&A link, I don't know why I missed it, maybe because I was focusing solely on kernel compilation.
You're welcome to any help and advice.

At one time I had the idea that it may be beneficial to use a more powerful and much faster Intel x86_64 based Linux system to save a shed load of compiling time. However, after having spent approx. 1 month trying to get a cross-compile to work, and being quite unsuccessful throughout, producing more errors than one could shake a stick at, I gave up on the idea and stuck to compiling natively on the various RPi devices. Compiling natively produces zero errors for me and is 100% successful every time.
 
2 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Slackware ARM vs Raspbian inquiry Exaga Slackware - ARM 15 12-05-2016 02:55 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - ARM

All times are GMT -5. The time now is 07:29 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration