Kernel 4.0-rc6 – Maybe only -rc7 Needed?

Updated the test system to Kernel 4.0-rc6, and VMware 11.1.0 (patched) and the latest NVIDIA driver – 349.12 – compile and load OK..

$ uname -a
Linux rg6830l 4.0.0-rc6 #1 SMP Sun Mar 29 22:23:37 PDT 2015 x86_64 x86_64 x86_64 GNU/Linux

Brief details of changes since -rc5 are here: http://lkml.iu.edu/hypermail/linux/kernel/1503.3/04437.html

The VMware patch info is in a previous article, at http://rglinuxtech.com/?p=1281.

Apparently – if all goes according to plan with -rc6 – 4.0 Final may be out after -rc7…    But of course, this sort of prediction is never absolutely certain!

Robert Gadsdon.  March 30, 2015.

ARM – DreamPlug Kernel Compile – Correction..

Thanks are due to Marcus Roeder, who pointed out an error in my DreamPlug kernel compile workflow (http://rglinuxtech.com/?p=1354)..

The make LOADADDR.. command was incorrect, and would result in less system memory being available..

The correct command is:

make LOADADDR=000008000 uImage

– and this will result in all the memory being available:

# free
      total  used   free  shared buffers cached
Mem: 512648 143796 368852 0      18968    74800
.............

I have amended the original article..  Apologies for the confusion..

Robert Gadsdon.  March 29, 2015.

ARM – Raspberry Pi and Pi2 – OK with 3.19.3..

After trials with earlier versions, the Pi and Pi2 updated to Kernel 3.19.3 without too much effort..

Source from here:  https://github.com/raspberrypi/linux/tree/rpi-3.19.y

Pi:

Pidora release 2014 (Raspberry Pi Fedora Remix)
Kernel 3.19.3 on an armv6l (ttyAMA0)
........
]# uname -a
Linux rgpi 3.19.3 #1 PREEMPT Fri Mar 27 23:55:44 PDT 2015 armv6l armv6l armv6l GNU/Linux

Pi2:

Fedora release 21 (Twenty One)
Kernel 3.19.3-v7 on an armv7l (ttyAMA0)
.............
]# uname -a
Linux rgpi2 3.19.3-v7 #1 SMP PREEMPT Sat Mar 28 00:50:19 PDT 2015 armv7l armv7l armv7l GNU/Linux

I also discovered the source of the ‘sluggish’ performance of the Pi2 – I had accidentally put an older version of the boot binaries etc. in the /boot directory, which resulted in only 256MB of total memory!

Robert Gadsdon.   March 28, 2015.

ARM – DreamPlug to Kernel 4.0-rc5 – .config Example

Updated the DreamPlug to Kernel 4.0-rc5, using the standard source from kernel.org, without any problems..

Fedora release 18 (Spherical Cow)
Kernel 4.0.0-rc5 on an armv5tel (ttyS0)
......
]$ uname -a
Linux rgdreamplug 4.0.0-rc5 #1 Mon Mar 23 10:47:21 PDT 2015 armv5tel armv5tel armv5tel GNU/Linux

In case it might be useful, I have put a copy of the corresponding kernel .config here:  http://pastebin.com/4ywFSLNP

Robert Gadsdon.   March 25, 2015.

ARM – Odroid to 4.0-rc5 – Eventually..

I had tried to update the Odroid U3 to Kernel 4.0-rc5 – using the patched source from https://github.com/tobiasjakobi/linux-odroid/tree/odroid-4.0.y – a few days ago, but the boot failed:

hub 1-3:1.0: 3 ports detected
INFO: rcu_sched detected stalls on CPUs/tasks: { 0} (detected by 1, t=4202 jiffies, g=-255, c=-256, q=2)
Task dump for CPU 0:
swapper/0 R running 0 1 0 0x00000002
Backtrace:
[<ee079c8c>] (0xee079c8c) from [<ee079cbc>] (0xee079cbc)
Backtrace aborted due to bad frame pointer <ed870ac0>
INFO: rcu_sched detected stalls on CPUs/tasks: { 0} (detected by 1, t=16807 jiffies, g=-255, c=-256, q=2)
Task dump for CPU 0:
swapper/0 R running 0 1 0 0x00000002
Backtrace:
[<ee079c8c>] (0xee079c8c) from [<ee079cbc>] (0xee079cbc)
Backtrace aborted due to bad frame pointer <ed870ac0>

I noticed that there has been more changes to this source later, and (re) downloaded it, and it now boots successfully:

Fedora release 21 (Twenty One)
Kernel 4.0.0-rc5 on an armv7l (ttySAC1)
...................
]# uname -a
Linux rgodroid 4.0.0-rc5 #1 SMP Wed Mar 25 11:38:17 PDT 2015 armv7l armv7l armv7l GNU/Linux

So… although the version seems the same, be sure to look out for any later ‘commits’!

Robert Gadsdon.   March 25, 2015.

ARM – Raspberry Pi and Pi2 – Trials with Later Kernels..

I had Kernel 3.19.0 (originally from https://github.com/raspberrypi/linux/tree/rpi-3.19.y – now updated) running on my Pi (armv6) and Pi2 (armv7) with no problems (apart from the Pi2 seeming very sluggish..) but after that had a few ‘issues’..

Pi:  Kernel 3.19.1 OK, but 3.19.2 refused to boot (nothing on console)

Pi2:  Kernel 3.19.1 booted and then crashed:

BCM2708FB: allocated DMA memory 47c00000
BCM2708FB: allocated DMA channel 0 @ f3007000
------------[ cut here ]------------
Kernel BUG at 802a04ec [verbose debug info unavailable]
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.19.1-v7 #1
Hardware name: BCM2709
task: 87040000 ti: 87048000 task.ti: 87048000
PC is at bcm2708_fb_set_par+0x120/0x124
LR is at console_unlock+0x2e0/0x4f4
pc : [<802a04ec>] lr : [<8005d488>] psr: 60000113
sp : 87049d70 ip : 87049d10 fp : 87049d94
r10: 00000102 r9 : 00000010 r8 : 00000268
r7 : 8727003c r6 : 87049d74 r5 : 87c10000 r4 : 87270000
r3 : 00000000 r2 : 00000000 r1 : 60000113 r0 : 806410f0
Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel
......... etc  etc..........

Pi2 with Kernel 3.19.2 had the same result as the Pi – no boot, and blank console..

It seems that the git repository contents are often updated, but the version is still the same, which makes tracking updates tricky!     This means that the ‘3.19.2’ I download today may well be different from the ‘3.19.2’ I downloaded a few days ago..   I know that this can all be controlled by git, but it it might be better for the average user if the ‘extraversion’ was used to signify fix levels, without resorting to git command complexity to control all this..

Robert Gadsdon.    March 23, 2015

 

ARM – Odroid U3 to 4.0-rc4..

Updated the Odroid U3 to Kernel 4.0-rc4, from the patched source here: https://github.com/tobiasjakobi/linux-odroid/tree/odroid-4.0.y

This time, the system booted successfully..

Fedora release 21 (Twenty One)
Kernel 4.0.0-rc4 on an armv7l (ttySAC1)
................
]# uname -a
Linux rgodroid 4.0.0-rc4 #1 SMP Wed Mar 18 23:53:05 PDT 2015 armv7l armv7l armv7l GNU/Linux

Robert Gadsdon.    March 19, 2015.

ARM – CuBox to 4.0-rc4 – Networking Fixed..

Updated the CuBox-I4Pro to Kernel 4.0-rc4 – from kernel.org, and – at last – networking works without the need for the mach-imx6q.c patch.

Fedora release 22 (Twenty Two)
Kernel 4.0.0-rc4 on an armv7l (ttymxc0)
........................
# uname -a
Linux rgcubox 4.0.0-rc4 #1 SMP Sun Mar 15 21:55:09 EDT 2015 armv7l armv7l armv7l GNU/Linux

Details of changes from -rc3 are here:  http://lkml.iu.edu/hypermail/linux/kernel/1503.1/05704.html

Robert Gadsdon.  March 15, 2015.

ARM – Odroid U3 test with Kernel.org 4.0-rc3 – Panic..

As there is no later version of the Odroid-specific 4.0 kernel source available yet, I decided to test with the standard 4.0-rc3 from kernel.org, but the U3 booted – and then Panic‘d..

.............................
EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 179:3.
devtmpfs: mounted
Freeing unused kernel memory: 288K (c0628000 - c0670000)
usb 1-3: New USB device found, idVendor=0424, idProduct=3503
usb 1-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 1-3:1.0: USB hub found
hub 1-3:1.0: 3 ports detected
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
CPU0: stopping
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.0.0-rc3 #1
Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
Backtrace:
[<c000c5dc>] (dump_backtrace) from [<c000c800>] (show_stack+0x18/0x1c)
 r6:00000000 r5:c0680c40 r4:00000000 r3:00000000
[<c000c7e8>] (show_stack) from [<c049929c>] (dump_stack+0x90/0xa0)
[<c049920c>] (dump_stack) from [<c000e948>] (handle_IPI+0x154/0x174)
 r5:00000000 r4:c069f798
[<c000e7f4>] (handle_IPI) from [<c0008678>] (gic_handle_irq+0x6c/0x70)
 r6:c06727ac r5:fffffff5 r4:f002000c r3:c0671f08
[<c000860c>] (gic_handle_irq) from [<c000d3a0>] (__irq_svc+0x40/0x54)
Exception stack(0xc0671f08 to 0xc0671f50)
1f00: 00000001 00000000 00000000 c0016940 c0670000 c06724cc
1f20: 00000000 c0672518 00000000 c066da20 c04a1118 c0671f5c c0671f60 c0671f50
1f40: c000a2f0 c000a2f4 60000153 ffffffff
 r8:00000000 r7:c0671f3c r6:ffffffff r5:60000153 r4:c000a2f4 r3:c000a2f0
[<c000a2b4>] (arch_cpu_idle) from [<c0050d48>] (cpu_startup_entry+0x2a8/0x34c)
[<c0050aa0>] (cpu_startup_entry) from [<c0497790>] (rest_init+0x7c/0x80)
 r7:ffffffff
[<c0497714>] (rest_init) from [<c0628cf4>] (start_kernel+0x3a8/0x3b4)
[<c062894c>] (start_kernel) from [<40008074>] (0x40008074)
CPU3: stopping
CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.0.0-rc3 #1
Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
Backtrace:
[<c000c5dc>] (dump_backtrace) from [<c000c800>] (show_stack+0x18/0x1c)
 r6:00000000 r5:c0680c40 r4:00000000 r3:00000000
[<c000c7e8>] (show_stack) from [<c049929c>] (dump_stack+0x90/0xa0)
[<c049920c>] (dump_stack) from [<c000e948>] (handle_IPI+0x154/0x174)
 r5:00000003 r4:c069f798
[<c000e7f4>] (handle_IPI) from [<c0008678>] (gic_handle_irq+0x6c/0x70)
 r6:c06727ac r5:fffffff5 r4:f002c00c r3:ee0aff48
[<c000860c>] (gic_handle_irq) from [<c000d3a0>] (__irq_svc+0x40/0x54)
Exception stack(0xee0aff48 to 0xee0aff90)
ff40: 00000001 00000000 00000000 c0016940 ee0ae000 c06724cc
ff60: 00000000 c0672518 00000000 c066da20 c04a1118 ee0aff9c ee0affa0 ee0aff90
ff80: c000a2f0 c000a2f4 60000153 ffffffff
 r8:00000000 r7:ee0aff7c r6:ffffffff r5:60000153 r4:c000a2f4 r3:c000a2f0
[<c000a2b4>] (arch_cpu_idle) from [<c0050d48>] (cpu_startup_entry+0x2a8/0x34c)
[<c0050aa0>] (cpu_startup_entry) from [<c000e59c>] (secondary_start_kernel+0x118/0x124)
 r7:c069f7c0
[<c000e484>] (secondary_start_kernel) from [<40008704>] (0x40008704)
 r5:00000015 r4:6e09006a
CPU2: stopping
CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.0.0-rc3 #1
Hardware name: SAMSUNG EXYNOS (Flattened Device Tree)
Backtrace:
[<c000c5dc>] (dump_backtrace) from [<c000c800>] (show_stack+0x18/0x1c)
 r6:00000000 r5:c0680c40 r4:00000000 r3:00000000
[<c000c7e8>] (show_stack) from [<c049929c>] (dump_stack+0x90/0xa0)
[<c049920c>] (dump_stack) from [<c000e948>] (handle_IPI+0x154/0x174)
 r5:00000002 r4:c069f798
[<c000e7f4>] (handle_IPI) from [<c0008678>] (gic_handle_irq+0x6c/0x70)
 r6:c06727ac r5:fffffff5 r4:f002800c r3:ee0adf48
[<c000860c>] (gic_handle_irq) from [<c000d3a0>] (__irq_svc+0x40/0x54)
Exception stack(0xee0adf48 to 0xee0adf90)
df40: 00000001 00000000 00000000 c0016940 ee0ac000 c06724cc
df60: 00000000 c0672518 00000000 c066da20 c04a1118 ee0adf9c ee0adfa0 ee0adf90
df80: c000a2f0 c000a2f4 60000153 ffffffff
 r8:00000000 r7:ee0adf7c r6:ffffffff r5:60000153 r4:c000a2f4 r3:c000a2f0
[<c000a2b4>] (arch_cpu_idle) from [<c0050d48>] (cpu_startup_entry+0x2a8/0x34c)
[<c0050aa0>] (cpu_startup_entry) from [<c000e59c>] (secondary_start_kernel+0x118/0x124)
 r7:c069f7c0
[<c000e484>] (secondary_start_kernel) from [<40008704>] (0x40008704)
 r5:00000015 r4:6e09006a
---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004

So.. I will have to wait for another Odroid-specific patched version..

Robert Gadsdon.   March 11, 2015.