dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5341
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Next firmware tree is now 3.10

Sun Sep 15, 2013 6:09 pm

The 3.10 kernel is to have long term support:
http://www.kroah.com/log/blog/2013/08/0 ... -3-dot-10/

(The last long term kernel was 3.4, so they don't come along very often).

I'm aiming to move to 3.10 for the main firmware, but initially I've moved the "next" tree to 3.10 first.
If no problems emerge in the next month, the default tree will move to 3.10.

To update:

Code: Select all

sudo BRANCH=next rpi-update
Note: this tree is aimed at testers. There could be missing kernel modules, or things that don't work.
If you find any problems, then report here, or create a github issue.

kalehrl
Posts: 350
Joined: Tue Jul 24, 2012 10:49 am

Re: Next firmware tree is now 3.10

Sun Sep 15, 2013 6:46 pm

As I understand it, running dist-upgrade will fetch the kernel 3.6.11 with SD Card timeout and other fixes which was previously only available with rpi-update?

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5341
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Next firmware tree is now 3.10

Sun Sep 15, 2013 6:57 pm

kalehrl wrote:As I understand it, running dist-upgrade will fetch the kernel 3.6.11 with SD Card timeout and other fixes which was previously only available with rpi-update?
The apt-get repo is unrelated to this thread. There is a (3.6.11) apt-get update expected, but I'm not sure if it is out yet.

JerryPi
Posts: 17
Joined: Tue Nov 20, 2012 8:25 am

Re: Next firmware tree is now 3.10

Mon Sep 16, 2013 2:58 pm

I am missing f2fs support. 3.9.11+ next branch had it.
Don't grow up, it's a trap!

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5341
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Next firmware tree is now 3.10

Mon Sep 16, 2013 3:13 pm

JerryPi wrote:I am missing f2fs support. 3.9.11+ next branch had it.
Good point. That should be enabled.

Dilligaf
Posts: 283
Joined: Wed May 23, 2012 6:48 pm

Re: Next firmware tree is now 3.10

Mon Sep 16, 2013 3:31 pm

Last time I tried the 3.10 kernel there were problems with the spi modules staying loaded, has this been addressed/fixed ?

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5341
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Next firmware tree is now 3.10

Mon Sep 16, 2013 3:38 pm

Dilligaf wrote:Last time I tried the 3.10 kernel there were problems with the spi modules staying loaded, has this been addressed/fixed ?
Is there an issue reported for this?

I don't personally use SPI, and the driver came from the community.
I'm sure it can be fixed, but will need some help from someone who uses SPI and can explain exactly what goes wrong.

Dilligaf
Posts: 283
Joined: Wed May 23, 2012 6:48 pm

Re: Next firmware tree is now 3.10

Mon Sep 16, 2013 5:11 pm

Boblight uses the spi modules. What I was seeing was when modprobing the spidev module it would create /dev/spi* and then unload rather then staying loaded.
You could then see /dev/spi* but if you ran lsmod the modules weren't loaded.

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5341
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Next firmware tree is now 3.10

Tue Sep 24, 2013 1:01 pm

next tree is updated. Added various requested options: F2FS, BATMAN_ADV, OPENVSWITCH, NF_NAT, DUMMY, QFMT_V1, QFMT_V2, DLM, joystick
See:
https://github.com/Hexxeh/rpi-firmware/ ... 61ec3d0703

B.Jay
Posts: 28
Joined: Thu Jul 18, 2013 10:57 pm

Re: Next firmware tree is now 3.10

Tue Oct 01, 2013 2:21 pm

Hi dom

So I jumped the gun and installed 3.10.13+

One thing I see where something's off: the calibration of the delay loop during the kernel init gives a very weird figure:

Code: Select all

[    0.000000] Switching to timer-based delay loop
[    0.001159] Calibrating delay loop (skipped), value calculated using timer frequency.. 2.00 BogoMIPS (lpj=10000)
Taken from /var/log/dmesg - also visible in /proc/cpuinfo. I know the "BogoMIPS" value is pointless, but it should actually calibrate to a figure close to the actual clock frequency of the CPU core.

The good news is that the weird dwc_otg USB resets are gone when there's a external USB hard drive attached, in my case auto-mounted through usb-mount, during system boot. In the latest 3.6.11+ (from a few days ago) it started acting up that way - it would stall for a moment, throw 1-2 dwc_otg resets, and then mount the drive - but 3.10.13+ is fine in this regard.

EDIT1: Another thing to note is that overall network throughput seems to have improved:

Code: Select all

scp testfile_250MB.img pi@raspberrypi:/dev/null
testfile_250MB.img   100%  237MB   4.2MB/s   00:57
Started off at 5.9MB/s and then stabilized at 4.2MB/s during the course of the file transfer.

Doing the same thing on the 3.6 series kernel, as shipped with the default Raspbian image, resulted in 2.5/2.7MB/s max. Still not at the ~10.2MB/s my BBB manages to achieve, but at least it's some improvement. /EDIT

EDIT 2: After copying another test file via Samba to the USB hard drive: same result ... flows at ~4.2MB/s - AND - the "sms95xx 1-1,1:1.0: eth0: kevent 2 may have been dropped" errors in the logs are also gone; 3.6 was happily throwing them out in quanities./EDIT

If I happen to find something else I'll drop you a note.

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5341
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Next firmware tree is now 3.10

Tue Oct 01, 2013 2:54 pm

B.Jay wrote: One thing I see where something's off: the calibration of the delay loop during the kernel init gives a very weird figure:

Code: Select all

[    0.000000] Switching to timer-based delay loop
[    0.001159] Calibrating delay loop (skipped), value calculated using timer frequency.. 2.00 BogoMIPS (lpj=10000)
Taken from /var/log/dmesg - also visible in /proc/cpuinfo. I know the "BogoMIPS" value is pointless, but it should actually calibrate to a figure close to the actual clock frequency of the CPU core.
https://github.com/raspberrypi/linux/is ... t-16332052

B.Jay
Posts: 28
Joined: Thu Jul 18, 2013 10:57 pm

Re: Next firmware tree is now 3.10

Tue Oct 01, 2013 2:59 pm

DOH! Should've checked the GitHub issue tracker first.
Thanks, my bad for not checking first.

User avatar
DavidS
Posts: 4334
Joined: Thu Dec 15, 2011 6:39 am
Location: USA
Contact: Website

Re: Next firmware tree is now 3.10

Sun Oct 06, 2013 11:42 am

Just because someone decides to redifine something in a way that breaks some things does that mean that we should follow suite? There are many applications that rely on the empty loop bogomips figure to calibrate there delay loops where an active delay is required, or some that were written before there was reliable high resolution timing in the Linux Kernel (that did not come until Kernel version 2.4).

So I would vote for using the old form of bogomips.
RPi = The best ARM based RISC OS computer around
More than 95% of posts made from RISC OS on RPi 1B/1B+ computers. Most of the rest from RISC OS on RPi 2B/3B/3B+ computers

CommanderROR
Posts: 47
Joined: Wed Oct 31, 2012 10:32 am

Re: Next firmware tree is now 3.10

Sun Oct 06, 2013 11:00 pm

This might be an incredibly stupid question, but is the HDMI audio support for up to 192k included in this branch? Would be nice if the Pi stopped downsampling everything to 48KHz.
Picoreplayer and Raspify have this integrated and it seems to work fine...apparently all it takes is a small change to the bcm module.

B.Jay
Posts: 28
Joined: Thu Jul 18, 2013 10:57 pm

Re: Next firmware tree is now 3.10

Sun Oct 13, 2013 4:50 pm

@dom: Long-uptime issue detected ...

Kernel is 3.10.15+, uptime is ~3d 20m

I'm seeing random network drop-outs. Problem is not related to the power supply (already checked voltages, testpoints show me 4.98V (which isn't that far off the ~5.08V un-loaded output of the USB "charger")) and the network switch to which the Pi is connected is as good as new (Netgear GS108E, only a few days old) and works perfectly as I have no link issues on any other device that's connected to the switch.

Checking back through the logs, the drop-outs weren't there with 3.10.13+

Log entries from boot --> current time:

Code: Select all

[12783.324591] smsc95xx 1-1.1:1.0 eth0: link down
[12784.871179] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[13371.728422] smsc95xx 1-1.1:1.0 eth0: link down
[13373.331130] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[14107.196582] smsc95xx 1-1.1:1.0 eth0: link down
[14108.783051] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[14795.418238] smsc95xx 1-1.1:1.0 eth0: link down
[14796.964126] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[20848.528469] smsc95xx 1-1.1:1.0 eth0: link down
[20850.114883] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[23011.502333] smsc95xx 1-1.1:1.0 eth0: link down
[23013.136773] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[24407.780001] smsc95xx 1-1.1:1.0 eth0: link down
[24409.334330] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[29822.475504] smsc95xx 1-1.1:1.0 eth0: link down
[29824.110068] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[31086.920040] smsc95xx 1-1.1:1.0 eth0: link down
[31088.505868] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[32064.027282] smsc95xx 1-1.1:1.0 eth0: link down
[32065.614498] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[35130.196719] smsc95xx 1-1.1:1.0 eth0: link down
[35131.759190] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[103615.625679] smsc95xx 1-1.1:1.0 eth0: link down
[103617.180508] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[123735.797920] smsc95xx 1-1.1:1.0 eth0: link down
[123737.385017] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[275268.923208] smsc95xx 1-1.1:1.0 eth0: link down
[275270.502036] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[275426.056916] smsc95xx 1-1.1:1.0 eth0: link down
[275427.603384] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[275603.449055] smsc95xx 1-1.1:1.0 eth0: link down
[275605.043489] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[276007.495926] smsc95xx 1-1.1:1.0 eth0: link down
[276009.122441] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[276242.800127] smsc95xx 1-1.1:1.0 eth0: link down
[276244.402355] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[297838.540228] smsc95xx 1-1.1:1.0 eth0: link down
[297840.079278] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[298083.774178] smsc95xx 1-1.1:1.0 eth0: link down
[298085.368635] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[298213.327754] smsc95xx 1-1.1:1.0 eth0: link down
[298214.906232] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[298523.025867] smsc95xx 1-1.1:1.0 eth0: link down
[298524.612307] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[299474.651138] smsc95xx 1-1.1:1.0 eth0: link down
[299476.221588] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[299612.525889] smsc95xx 1-1.1:1.0 eth0: link down
[299614.112456] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[299804.519945] smsc95xx 1-1.1:1.0 eth0: link down
[299806.146420] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[299824.098613] smsc95xx 1-1.1:1.0 eth0: link down
[299825.693069] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[299851.502342] smsc95xx 1-1.1:1.0 eth0: link down
[299853.104795] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[299866.896413] smsc95xx 1-1.1:1.0 eth0: link down
[299868.474883] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[299984.840443] smsc95xx 1-1.1:1.0 eth0: link down
[299986.418883] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[299987.192814] smsc95xx 1-1.1:1.0 eth0: link down
[299988.763614] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[301263.790196] smsc95xx 1-1.1:1.0 eth0: link down
[301265.344659] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[301271.559248] smsc95xx 1-1.1:1.0 eth0: link down
[301273.145693] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[301402.849460] smsc95xx 1-1.1:1.0 eth0: link down
[301404.411552] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[303332.903288] smsc95xx 1-1.1:1.0 eth0: link down
[303334.465773] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[303517.912434] smsc95xx 1-1.1:1.0 eth0: link down
[303519.515040] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[303661.499953] smsc95xx 1-1.1:1.0 eth0: link down
[303663.070412] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[303748.647796] smsc95xx 1-1.1:1.0 eth0: link down
[303750.202243] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[303770.626767] smsc95xx 1-1.1:1.0 eth0: link down
[303772.205360] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[303867.936120] smsc95xx 1-1.1:1.0 eth0: link down
[303869.514455] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[303890.987130] smsc95xx 1-1.1:1.0 eth0: link down
[303892.576833] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[303893.359573] smsc95xx 1-1.1:1.0 eth0: link down
[303894.929884] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[303932.532770] smsc95xx 1-1.1:1.0 eth0: link down
[303934.103199] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[303934.877079] smsc95xx 1-1.1:1.0 eth0: link down
[303936.455401] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[303937.229394] smsc95xx 1-1.1:1.0 eth0: link down
[303938.799866] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[303946.934715] smsc95xx 1-1.1:1.0 eth0: link down
[303948.529189] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[303949.311055] smsc95xx 1-1.1:1.0 eth0: link down
[303950.881510] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[304169.108922] smsc95xx 1-1.1:1.0 eth0: link down
[304170.663345] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[304171.437255] smsc95xx 1-1.1:1.0 eth0: link down
[304173.015678] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[304176.109890] smsc95xx 1-1.1:1.0 eth0: link down
[304177.688576] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[306077.432419] smsc95xx 1-1.1:1.0 eth0: link down
[306078.970629] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[306079.744497] smsc95xx 1-1.1:1.0 eth0: link down
[306081.338948] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[306082.112835] smsc95xx 1-1.1:1.0 eth0: link down
[306083.691270] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[306084.465129] smsc95xx 1-1.1:1.0 eth0: link down
[306086.035593] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[306086.817476] smsc95xx 1-1.1:1.0 eth0: link down
[306088.387909] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[306089.161795] smsc95xx 1-1.1:1.0 eth0: link down
[306090.764241] smsc95xx 1-1.1:1.0 eth0: link up, 10Mbps, full-duplex, lpa 0xCC61
[324187.700640] smsc95xx 1-1.1:1.0 eth0: link down
[324191.135302] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[328566.247494] smsc95xx 1-1.1:1.0 eth0: link down
[328567.793924] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[329708.586665] smsc95xx 1-1.1:1.0 eth0: link down
[329710.149123] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[330183.171143] smsc95xx 1-1.1:1.0 eth0: link down
[330184.797606] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[330686.823812] smsc95xx 1-1.1:1.0 eth0: link down
[330688.450007] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[331016.868407] smsc95xx 1-1.1:1.0 eth0: link down
[331018.462874] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[332043.219093] smsc95xx 1-1.1:1.0 eth0: link down
[332044.790302] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[332471.174102] smsc95xx 1-1.1:1.0 eth0: link down
[332472.776445] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[332490.640618] smsc95xx 1-1.1:1.0 eth0: link down
[332492.235059] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[332639.588863] smsc95xx 1-1.1:1.0 eth0: link down
[332641.135295] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
EDIT: Running Raspbian Wheezy (latest version and up-to-date as it show no updates to install), booting to comand line, only services up and running are SSH, BTSync, Samba. No X11 loaded, no overclock, no fancy alterations to the system.

jdb
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 2123
Joined: Thu Jul 11, 2013 2:37 pm

Re: Next firmware tree is now 3.10

Sun Oct 13, 2013 9:05 pm

So, you got a new network switch a few days ago and the link starts to drop?

You should do an rpi-update to an older version and check that the issue still exists.
Try a sudo rpi-update 7d605b7bf162fd4a9151804b2dcbd4d6e4b671d4.
Rockets are loud.
https://astro-pi.org

B.Jay
Posts: 28
Joined: Thu Jul 18, 2013 10:57 pm

Re: Next firmware tree is now 3.10

Mon Oct 14, 2013 2:43 am

jdb wrote:So, you got a new network switch a few days ago and the link starts to drop?
Yes, I replaced a old 24-Port Netgear Gigabit switch with 2 Netgear GS108E (8-Port, Managed) switches because the 24-port switch was acting up. After closer inspection I found out the issue was caused by a couple of 1000µF 10V caps spread across the motherboard manufactured by CapXion (*RIPS HAIRS OUT*) - though all the other caps are from Taicon (belongs to Nichicon). I'm still waiting for the spares to arrive (ordered Nichicon caps and kicked the CapXion crap out and beyond this Universe).
jdb wrote:You should do an rpi-update to an older version and check that the issue still exists.
Try a sudo rpi-update 7d605b7bf162fd4a9151804b2dcbd4d6e4b671d4.
Okay, so I carefully investigated the systems connected to the switch (like I wrote above I actually got two, I'm focusing on the ones connected to the "GS108E-1"):
  • AMD Phenom II X6 1100T rig (Gigabyte GA-870A-UD3, Onboard Realtek 8168 PCIe GbE NIC)
    Stable 1000Mbps link, no dropouts
  • AMD FX8150 rig (Gigabyte GA-870A-UD3, Onboard Realtek 8168 PCIe GbE NIC)
    Same. Perfectly stable 1000Mbps link without dropouts
  • <some TI Sitara based ARMv7 board from some competitor which is not allowed to be mentioned here>
    Perfectly stable 100Mbps link, no dropouts.
  • TP-Link WR841N Router (Uplinked to the switch)
    No dropouts at LAN Port 1 recorded in the logs of the router (DD-WRT)
Since none of these four systems show ANY network issues I believe it is safe to assume the switch is working as intended without issues.

Now on to the Raspberry Pi (512MB rev. B)

I prepared three SD cards and I also exchanged the network cable past a "tried and tested" one:
1 with the "daily driver" setup (Raspbian 7, Kernel 3.10.15+, BTSync, Samba, SSH enabled, boot to command line)
1 copy of the "daily driver" image (same SD, directly dd sd -> img && img -> sd) with Kernel 3.10.13+
1 with the standard Raspbian 2013-09-25 image, only updated to 3.6.11+ from October 2nd

Results:
SD with the genuine, updated, Raspbian image shows network dropouts (only few minutes after booting)
SD with 3.10.15+ kernel shows network dropouts (first drop happened after ~42 minutes uptime).
SD with 3.10.13+ is stable so far. No dropouts in 2 hours.

Also monitored the voltage at the testpoints - doesn't drop below 4.98V (using a Agilent digital multivolt meter). The Raspberry is powered off a "tabtools" Universal USB charger providing a grand total of 2 Amps, and the last time I checked with a resistive dummy load the charger didn't break a sweat at drawing 2 amps straight.

EDIT: Mon Oct 14, 2013 ~7:05 pm
3.10.13+ also drops the link, but a lot more less than any other of the two setups... during the day it happened two times, and at the 2nd time (about an hour ago) it dropped down to negotiating only a 10Mbps link-speed. Funnily enough it's only the Pi acting up (and yes, I also already plugged it into another Port on the switch), all other systems on the switch are still perfectly fine.

ollo_rpi
Posts: 1
Joined: Thu Oct 17, 2013 5:15 pm

Re: Next firmware tree is now 3.10

Thu Oct 17, 2013 5:27 pm

Hi dom,

any chance to add the lirc_rpi module to next firmware tree? Its included in master, but not in next :?

Thanks & regards, ollo_rpi

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5341
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Next firmware tree is now 3.10

Sat Oct 19, 2013 11:18 am

ollo_rpi wrote: any chance to add the lirc_rpi module to next firmware tree? Its included in master, but not in next :?
Should be there in latest update.

druckmusik
Posts: 2
Joined: Thu Oct 24, 2013 8:54 am

Re: Next firmware tree is now 3.10

Thu Oct 24, 2013 8:57 am

ollo_rpi wrote:Hi dom,

any chance to add the lirc_rpi module to next firmware tree? Its included in master, but not in next :?

Thanks & regards, ollo_rpi
I also miss w1-gpio and w1-therm
which are in master but not in next.
Needed for 1-wire temperature-sensor

Stefan

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5341
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Next firmware tree is now 3.10

Wed Oct 30, 2013 11:06 pm

druckmusik wrote: I also miss w1-gpio and w1-therm
which are in master but not in next.
Needed for 1-wire temperature-sensor
Should be added to next firmware tree. Please update and test.

druckmusik
Posts: 2
Joined: Thu Oct 24, 2013 8:54 am

Re: Next firmware tree is now 3.10

Thu Oct 31, 2013 8:34 am

dom wrote:
druckmusik wrote: I also miss w1-gpio and w1-therm
which are in master but not in next.
Needed for 1-wire temperature-sensor
Should be added to next firmware tree. Please update and test.
Hello dom,

works so far (at least for me).

Thanks a lot
Stefan

dom
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 5341
Joined: Wed Aug 17, 2011 7:41 pm
Location: Cambridge

Re: Next firmware tree is now 3.10

Thu Oct 31, 2013 1:40 pm

druckmusik wrote:
dom wrote:
druckmusik wrote: works so far (at least for me).
Cool. I'm expecting to bump normal rpi-update tree to 3.10 this weekend.

vadim
Posts: 129
Joined: Wed Sep 18, 2013 1:47 pm
Location: Nottingham

Re: Next firmware tree is now 3.10

Thu Oct 31, 2013 3:32 pm

YAY! :D

mcgyver83
Posts: 358
Joined: Fri Oct 05, 2012 11:49 am

Re: Next firmware tree is now 3.10

Mon Nov 04, 2013 10:42 pm

So new rpi fw is coming?
I remember something related to dynamic memory split, is it stable now?can I activate it ?How?

Return to “Advanced users”