User avatar
DougieLawson
Posts: 36332
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: Moving Linux kernel to 4.19

Mon Jan 21, 2019 3:49 pm

Zofiel wrote:
Mon Jan 21, 2019 3:43 pm
1. Do you recommend to install kernel 4.19 now? Is It stable?
2. Can I back to kernel 4.14 simply running a rpi-update without BRANCH=next?
1. No, it's not stable enough. I'm still running eight of my eighteen Raspberries on 4.14.
2. If you have to ask that you shouldn't be running rpi-update, you can destroy your system with rpi-update
Note: Having anything humorous in your signature is completely banned on this forum. Wear a tin-foil hat and you'll get a ban.

Any DMs sent on Twitter will be answered next month.

This is a doctor free zone.

Zofiel
Posts: 7
Joined: Mon May 30, 2016 1:18 pm

Re: Moving Linux kernel to 4.19

Mon Jan 21, 2019 3:50 pm

DougieLawson wrote:
Mon Jan 21, 2019 3:49 pm
Zofiel wrote:
Mon Jan 21, 2019 3:43 pm
1. Do you recommend to install kernel 4.19 now? Is It stable?
2. Can I back to kernel 4.14 simply running a rpi-update without BRANCH=next?
1. No, it's not stable enough. I'm still running eight of my eighteen Raspberries on 4.14.
2. If you have to ask that you shouldn't be running rpi-update, you can destroy your system with rpi-update
Thanks for your help.

User avatar
kozman
Posts: 53
Joined: Tue Sep 11, 2018 3:40 pm

Re: Moving Linux kernel to 4.19

Tue Jan 22, 2019 4:54 pm

Zofiel wrote:
Mon Jan 21, 2019 3:43 pm
Hi team,

Do you recommend to install kernel 4.19 now? Is It stable?

Can I back to kernel 4.14 simply running a rpi-update without BRANCH=next?

thanks in advance
The best thing to do is backup or clone your SD card to another one if you really don't want to potentially break anything or have to go to great lengths to revert back to 4.14.x series. I have a few spare cloned SD cards so I can mess things up as I don't play around on my stable SD cards.

I would surmise that by 4.19.25+ (March / April?) is when we'll likely see things getting to be what can be considered stable. It's still too new a kernel and has lot of fixes that need back-porting to it for it to be more stable right now. For playing around, testing, non-production, etc. it works ok enough. I am testing it on my Retropie setup and it seems ok thus far. YMMV.

6by9
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 7458
Joined: Wed Dec 04, 2013 11:27 am
Location: ZZ9 Plural Z Alpha, aka just outside Cambridge.

Re: Moving Linux kernel to 4.19

Tue Jan 22, 2019 5:05 pm

Could someone else check whether the Fake KMS / vc4-fkms-v3d overlay works for them with 4.19? If so, which OS are you running?
Selecting it for me is causing boot to stall around the time of trying to mount drives, but I haven't excluded my Raspbian SD card image from being at fault. Legacy and Full KMS seem fine.

(Please be very aware that you may well have to go in with an SD card reader and edit /boot/config.txt to remove the "dtoverlay=vc4-fkms-v3d" line).
Software Engineer at Raspberry Pi Trading. Views expressed are still personal views.
I'm not interested in doing contracts for bespoke functionality - please don't ask.

tvjon
Posts: 710
Joined: Mon Jan 07, 2013 9:11 am

Re: Moving Linux kernel to 4.19

Tue Jan 22, 2019 6:10 pm

6by9 wrote:
Tue Jan 22, 2019 5:05 pm
Could someone else check whether the Fake KMS / vc4-fkms-v3d overlay works for them with 4.19? If so, which OS are you running?

1

Selecting it for me is causing boot to stall around the time of trying to mount drives, but I haven't excluded my Raspbian SD card image from being at fault. Legacy and Full KMS seem fine.

2

...
1.
Same as you. It fails to boot. I only tried it because I built a C++ app from Github using OpenGL, & I wondered if performance would improve, so still don't know.

$ uname -a
Linux sa1 4.19.15-v7+ #1190 SMP Mon Jan 14 19:27:10 GMT 2019 armv7l GNU/Linux

2.
Same again, but fairly sure µSD is sound.

I backed it up last week, & restored it at a local Jam Saturday & it worked just fine.

HTH.

6by9
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 7458
Joined: Wed Dec 04, 2013 11:27 am
Location: ZZ9 Plural Z Alpha, aka just outside Cambridge.

Re: Moving Linux kernel to 4.19

Tue Jan 22, 2019 6:19 pm

tvjon wrote:
Tue Jan 22, 2019 6:10 pm
1.
Same as you. It fails to boot. I only tried it because I built a C++ app from Github using OpenGL, & I wondered if performance would improve, so still don't know.

$ uname -a
Linux sa1 4.19.15-v7+ #1190 SMP Mon Jan 14 19:27:10 GMT 2019 armv7l GNU/Linux

2.
Same again, but fairly sure µSD is sound.

I backed it up last week, & restored it at a local Jam Saturday & it worked just fine.

HTH.
Thanks for trying it - at least I'm not going totally mad.
I was also trying to work out where a performance issue lay, so wanted to ditch the kernel side of full KMS.

I'll have to do some more digging. I suspect some part of the rendering pipeline isn't connecting up correctly and is therefore stalling. I get a load of stuff out on the serial console, but not enough to immediately tell where the problem lies.
Software Engineer at Raspberry Pi Trading. Views expressed are still personal views.
I'm not interested in doing contracts for bespoke functionality - please don't ask.

jimbojones
Posts: 15
Joined: Sun Apr 15, 2018 2:33 pm

Re: Moving Linux kernel to 4.19

Wed Jan 30, 2019 9:39 am

Am I imagining things, or is the arm64 arch in the 4.19.y branch getting more updates pulled to it by the maintainers than the old 4.14.y branch, which usually required a pull request be made first? Is this a sign that we could be seeing 64-bit as standard in an upcoming Raspbian image?

6by9
Raspberry Pi Engineer & Forum Moderator
Raspberry Pi Engineer & Forum Moderator
Posts: 7458
Joined: Wed Dec 04, 2013 11:27 am
Location: ZZ9 Plural Z Alpha, aka just outside Cambridge.

Re: Moving Linux kernel to 4.19

Wed Jan 30, 2019 12:35 pm

jimbojones wrote:
Wed Jan 30, 2019 9:39 am
Am I imagining things, or is the arm64 arch in the 4.19.y branch getting more updates pulled to it by the maintainers than the old 4.14.y branch, which usually required a pull request be made first? Is this a sign that we could be seeing 64-bit as standard in an upcoming Raspbian image?
4.19 is getting updated as it is the next LTS kernel release, and is expected to be the new standard kernel "soon". A number of the kernel APIs have moved on significantly, therefore it is easier to work on the more recent branch.

Yes, there are some commits for 64 bit kernel support as some of the new drivers are being written with 64 bit support in mind. Others are being updated so that some of the debugging tools work with a 64 bit kernel (eg vcdbg). Most are merely fixing up where people have used the wrong format specifier in logging messages or made invalid casts, others are fixing up the compat ioctl handling, and still others are having to change how the driver is working.

A 64 bit kernel does not require a 64 bit userspace.
Software Engineer at Raspberry Pi Trading. Views expressed are still personal views.
I'm not interested in doing contracts for bespoke functionality - please don't ask.

User avatar
Gavinmc42
Posts: 3936
Joined: Wed Aug 28, 2013 3:31 am

Re: Moving Linux kernel to 4.19

Thu Jan 31, 2019 11:22 am

Am I imagining things, or is the arm64 arch in the 4.19.y branch getting more updates pulled to it by the maintainers than the old 4.14.y
It could also be because there are now lots of A53-A72 boards out there now.
More low cost aarch64 PC's means more porting, testing, commits etc.
The Industry, embedded, industrial etc are using more ARM, even Internet backbone Servers are coming in ARM versions.
ARM use a bit less power and when you have a warehouse of them the power bills can be big.

So yes newer kernels will have more ARM support.
Things like Compilers for aarch64 are now way more common than just a few months ago.

We Pi users get the benefit of Industry jumping onboard, including all those phone makers who generally now only want aarch64
I'm dancing on Rainbows.
Raspberries are not Apples or Oranges

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

Re: Moving Linux kernel to 4.19

Mon Feb 18, 2019 4:37 pm

We have now bumped the master branch of rpi-update to 4.19 kernel for wider testing.

User avatar
DougieLawson
Posts: 36332
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: Moving Linux kernel to 4.19

Mon Feb 18, 2019 5:32 pm

dom wrote:
Mon Feb 18, 2019 4:37 pm
We have now bumped the master branch of rpi-update to 4.19 kernel for wider testing.
I've justed tested that OpenVPN bug and it's fixed in 4.19.23+.
Note: Having anything humorous in your signature is completely banned on this forum. Wear a tin-foil hat and you'll get a ban.

Any DMs sent on Twitter will be answered next month.

This is a doctor free zone.

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

Re: Moving Linux kernel to 4.19

Mon Feb 18, 2019 5:37 pm

DougieLawson wrote:
Mon Feb 18, 2019 5:32 pm
I've justed tested that OpenVPN bug and it's fixed in 4.19.23+.
Good to hear - it always seemed likely as it was an issue in upstream code that other platforms were likely to hit.

User avatar
kozman
Posts: 53
Joined: Tue Sep 11, 2018 3:40 pm

Re: Moving Linux kernel to 4.19

Mon Feb 18, 2019 6:54 pm

dom wrote:
Mon Feb 18, 2019 4:37 pm
We have now bumped the master branch of rpi-update to 4.19 kernel for wider testing.
This is great news. Should bring a lot more performance and possibilities to all the Pis out there. Thanks Devs!

User avatar
DougieLawson
Posts: 36332
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: Moving Linux kernel to 4.19

Mon Feb 18, 2019 6:57 pm

My 3B+ isn't happy. The WiFi network is very flaky.

Code: Select all

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.19.23-v7+ ([email protected]) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1202 SMP Mon Feb 18 15:55:19 GMT 2019
[    0.000000] CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: Raspberry Pi 3 Model B Plus Rev 1.3
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] cma: Reserved 8 MiB at 0x37800000
[    0.000000] On node 0 totalpages: 229376
[    0.000000]   Normal zone: 2016 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 229376 pages, LIFO batch:63
[    0.000000] random: get_random_bytes called from start_kernel+0xac/0x4b4 with crng_init=0
[    0.000000] percpu: Embedded 17 pages/cpu @(ptrval) s39488 r8192 d21952 u69632
[    0.000000] pcpu-alloc: s39488 r8192 d21952 u69632 alloc=17*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 227360
[    0.000000] Kernel command line: 8250.nr_uarts=0 bcm2708_fb.fbwidth=1366 bcm2708_fb.fbheight=768 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=PARTUUID=86c71275-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 886304K/917504K available (8192K kernel code, 626K rwdata, 2164K rodata, 1024K init, 821K bss, 23008K reserved, 8192K cma-reserved)
[    0.000000] Virtual kernel memory layout:
                   vector  : 0xffff0000 - 0xffff1000   (   4 kB)
                   fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
                   vmalloc : 0xb8800000 - 0xff800000   (1136 MB)
                   lowmem  : 0x80000000 - 0xb8000000   ( 896 MB)
                   modules : 0x7f000000 - 0x80000000   (  16 MB)
                     .text : 0x(ptrval) - 0x(ptrval)   (9184 kB)
                     .init : 0x(ptrval) - 0x(ptrval)   (1024 kB)
                     .data : 0x(ptrval) - 0x(ptrval)   ( 627 kB)
                      .bss : 0x(ptrval) - 0x(ptrval)   ( 822 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] ftrace: allocating 26209 entries in 77 pages
[    0.000000] rcu: Hierarchical RCU implementation.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] arch_timer: cp15 timer(s) running at 19.20MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
[    0.000007] sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
[    0.000018] Switching to timer-based delay loop, resolution 52ns
[    0.000280] Console: colour dummy device 80x30
[    0.000299] console [tty1] enabled
[    0.000342] Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
[    0.000358] pid_max: default: 32768 minimum: 301
[    0.000697] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000713] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001796] Disabling memory control group subsystem
[    0.001862] CPU: Testing write buffer coherency: ok
[    0.002331] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.002975] Setting up static identity map for 0x100000 - 0x10003c
[    0.003125] rcu: Hierarchical SRCU implementation.
[    0.003912] smp: Bringing up secondary CPUs ...
[    0.004799] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.005777] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.006688] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.006809] smp: Brought up 1 node, 4 CPUs
[    0.006821] SMP: Total of 4 processors activated (153.60 BogoMIPS).
[    0.006827] CPU: All CPU(s) started in HYP mode.
[    0.006832] CPU: Virtualization extensions available.
[    0.007791] devtmpfs: initialized
[    0.019720] VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4
[    0.019988] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.020006] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.020591] pinctrl core: initialized pinctrl subsystem
[    0.021460] NET: Registered protocol family 16
[    0.023817] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.029561] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.029569] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.029773] Serial: AMBA PL011 UART driver
[    0.032216] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[    0.068058] bcm2835-dma 3f007000.dma: DMA legacy API manager at (ptrval), dmachans=0x1
[    0.069704] SCSI subsystem initialized
[    0.069928] usbcore: registered new interface driver usbfs
[    0.069984] usbcore: registered new interface driver hub
[    0.070078] usbcore: registered new device driver usb
[    0.090260] raspberrypi-firmware soc:firmware: Attached to firmware from 2019-02-12 19:46, variant start_x
[    0.100504] raspberrypi-firmware soc:firmware: Firmware hash is 8eff5e4023657a8b3b59e1f90dc966f62d74908c
[    0.111949] clocksource: Switched to clocksource arch_sys_counter
[    0.201340] VFS: Disk quotas dquot_6.6.0
[    0.201422] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.201646] FS-Cache: Loaded
[    0.201872] CacheFiles: Loaded
[    0.211727] NET: Registered protocol family 2
[    0.212543] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes)
[    0.212580] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.212689] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.212875] TCP: Hash tables configured (established 8192 bind 8192)
[    0.213011] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.213063] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.213399] NET: Registered protocol family 1
[    0.213999] RPC: Registered named UNIX socket transport module.
[    0.214005] RPC: Registered udp transport module.
[    0.214011] RPC: Registered tcp transport module.
[    0.214017] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.215757] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available
[    0.218799] Initialise system trusted keyrings
[    0.218987] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[    0.228796] FS-Cache: Netfs 'nfs' registered for caching
[    0.229372] NFS: Registering the id_resolver key type
[    0.229401] Key type id_resolver registered
[    0.229407] Key type id_legacy registered
[    0.229423] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.231720] Key type asymmetric registered
[    0.231730] Asymmetric key parser 'x509' registered
[    0.231776] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[    0.232007] io scheduler noop registered
[    0.232014] io scheduler deadline registered (default)
[    0.232202] io scheduler cfq registered
[    0.232209] io scheduler mq-deadline registered (default)
[    0.232216] io scheduler kyber registered
[    0.234867] BCM2708FB: allocated DMA memory 0xf7840000
[    0.234910] BCM2708FB: allocated DMA channel 0
[    0.264725] Console: switching to colour frame buffer device 170x48
[    0.283477] bcm2835-rng 3f104000.rng: hwrng registered
[    0.283669] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
[    0.284204] vc-sm: Videocore shared memory driver
[    0.284534] gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
[    0.295355] brd: module loaded
[    0.305583] loop: module loaded
[    0.305596] Loading iSCSI transport class v2.0-870.
[    0.306360] libphy: Fixed MDIO Bus: probed
[    0.306469] usbcore: registered new interface driver lan78xx
[    0.306533] usbcore: registered new interface driver smsc95xx
[    0.306549] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[    0.332039] dwc_otg 3f980000.usb: base=(ptrval)
[    0.532284] Core Release: 2.80a
[    0.532294] Setting default values for core params
[    0.532325] Finished setting default values for core params
[    0.732590] Using Buffer DMA mode
[    0.732597] Periodic Transfer Interrupt Enhancement - disabled
[    0.732603] Multiprocessor Interrupt Enhancement - disabled
[    0.732610] OTG VER PARAM: 0, OTG VER FLAG: 0
[    0.732629] Dedicated Tx FIFOs mode
[    0.733099] WARN::dwc_otg_hcd_init:1049: FIQ DMA bounce buffers: virt = b7854000 dma = 0xf7854000 len=9024
[    0.733126] FIQ FSM acceleration enabled for :
               Non-periodic Split Transactions
               Periodic Split Transactions
               High-Speed Isochronous Endpoints
               Interrupt/Control Split Transaction hack enabled
[    0.733134] dwc_otg: Microframe scheduler enabled
[    0.733186] WARN::hcd_init_fiq:457: FIQ on core 1
[    0.733198] WARN::hcd_init_fiq:458: FIQ ASM at 80649df4 length 36
[    0.733210] WARN::hcd_init_fiq:484: MPHI regs_base at f0006000
[    0.733275] dwc_otg 3f980000.usb: DWC OTG Controller
[    0.733308] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[    0.733343] dwc_otg 3f980000.usb: irq 56, io mem 0x00000000
[    0.733390] Init: Port Power? op_state=1
[    0.733395] Init: Power Port (0)
[    0.733644] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    0.733655] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    0.733665] usb usb1: Product: DWC OTG Controller
[    0.733674] usb usb1: Manufacturer: Linux 4.19.23-v7+ dwc_otg_hcd
[    0.733682] usb usb1: SerialNumber: 3f980000.usb
[    0.734315] hub 1-0:1.0: USB hub found
[    0.734360] hub 1-0:1.0: 1 port detected
[    0.734951] dwc_otg: FIQ enabled
[    0.734957] dwc_otg: NAK holdoff enabled
[    0.734963] dwc_otg: FIQ split-transaction FSM enabled
[    0.734974] Module dwc_common_port init
[    0.735251] usbcore: registered new interface driver usb-storage
[    0.735433] mousedev: PS/2 mouse device common for all mice
[    0.736328] bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer
[    0.736651] bcm2835-cpufreq: min=600000 max=1400000
[    0.737133] sdhci: Secure Digital Host Controller Interface driver
[    0.737138] sdhci: Copyright(c) Pierre Ossman
[    0.737520] mmc-bcm2835 3f300000.mmc: could not get clk, deferring probe
[    0.737879] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
[    0.737999] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.739566] ledtrig-cpu: registered to indicate activity on CPUs
[    0.739718] hidraw: raw HID events driver (C) Jiri Kosina
[    0.739922] usbcore: registered new interface driver usbhid
[    0.739927] usbhid: USB HID core driver
[    0.740703] vchiq: vchiq_init_state: slot_zero = (ptrval), is_master = 0
[    0.742297] [vc_sm_connected_init]: start
[    0.751472] [vc_sm_connected_init]: end - returning 0
[    0.752555] Initializing XFRM netlink socket
[    0.752581] NET: Registered protocol family 17
[    0.752679] Key type dns_resolver registered
[    0.753222] Registering SWP/SWPB emulation handler
[    0.753867] registered taskstats version 1
[    0.753885] Loading compiled-in X.509 certificates
[    0.761244] uart-pl011 3f201000.serial: cts_event_workaround enabled
[    0.761324] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 81, base_baud = 0) is a PL011 rev2
[    0.763398] mmc-bcm2835 3f300000.mmc: mmc_debug:0 mmc_debug2:0
[    0.763409] mmc-bcm2835 3f300000.mmc: DMA channel allocated
[    0.789562] sdhost: log_buf @ (ptrval) (f7853000)
[    0.824688] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    0.826253] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    0.827818] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    0.830621] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    0.835452] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[    0.836760] of_cfs_init
[    0.836920] of_cfs_init: OK
[    0.837562] Waiting for root device PARTUUID=86c71275-02...
[    0.923602] random: fast init done
[    0.931756] mmc1: new high speed SDIO card at address 0001
[    0.962053] Indeed it is in host mode hprt0 = 00021501
[    1.191983] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    1.192108] Indeed it is in host mode hprt0 = 00001101
[    1.432225] usb 1-1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
[    1.432237] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.432825] hub 1-1:1.0: USB hub found
[    1.432916] hub 1-1:1.0: 4 ports detected
[    1.751979] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    1.882218] usb 1-1.1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3
[    1.882229] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    1.882742] hub 1-1.1:1.0: USB hub found
[    1.882829] hub 1-1.1:1.0: 3 ports detected
[    1.981979] usb 1-1.2: new high-speed USB device number 4 using dwc_otg
[    2.112536] usb 1-1.2: New USB device found, idVendor=0781, idProduct=5567, bcdDevice= 1.27
[    2.112547] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    2.112557] usb 1-1.2: Product: Cruzer Blade
[    2.112565] usb 1-1.2: Manufacturer: SanDisk
[    2.112574] usb 1-1.2: SerialNumber: 4C530201560318118102
[    2.113150] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[    2.113748] scsi host0: usb-storage 1-1.2:1.0
[    2.661981] usb 1-1.1.1: new high-speed USB device number 5 using dwc_otg
[    2.792339] usb 1-1.1.1: New USB device found, idVendor=0424, idProduct=7800, bcdDevice= 3.00
[    2.792352] usb 1-1.1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.056818] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): No External EEPROM. Setting MAC Speed
[    3.057751] libphy: lan78xx-mdiobus: probed
[    3.062739] lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): int urb period 64
[    3.193155] scsi 0:0:0:0: Direct-Access     SanDisk  Cruzer Blade     1.27 PQ: 0 ANSI: 6
[    3.194887] sd 0:0:0:0: [sda] 61056064 512-byte logical blocks: (31.3 GB/29.1 GiB)
[    3.196278] sd 0:0:0:0: [sda] Write Protect is off
[    3.196291] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[    3.196865] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    3.209206]  sda: sda1 sda2
[    3.213088] sd 0:0:0:0: [sda] Attached SCSI removable disk
[    3.260545] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[    3.260602] VFS: Mounted root (ext4 filesystem) readonly on device 8:2.
[    3.262012] devtmpfs: mounted
[    3.267994] Freeing unused kernel memory: 1024K
[    3.272348] Run /sbin/init as init process
[    3.742482] systemd[1]: System time before build time, advancing clock.
[    3.896919] NET: Registered protocol family 10
[    3.898359] Segment Routing with IPv6
[    3.936452] random: systemd: uninitialized urandom read (16 bytes read)
[    3.942762] systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
[    3.943356] systemd[1]: Detected architecture arm.
[    3.944910] systemd[1]: Set hostname to <hitchhiker>.
[    3.975677] random: systemd: uninitialized urandom read (16 bytes read)
[    3.996519] random: systemd-sysv-ge: uninitialized urandom read (16 bytes read)
[    5.583783] urandom_read: 5 callbacks suppressed
[    5.583793] random: systemd: uninitialized urandom read (16 bytes read)
[    5.583998] random: systemd: uninitialized urandom read (16 bytes read)
[    5.965231] systemd[1]: [/etc/systemd/system/media.mount:3] Failed to add dependency on network-online.targe, ignoring: Invalid argument
[    6.056343] systemd[1]: cron.service: Cannot add dependency job, ignoring: Unit cron.service is masked.
[    6.082206] systemd[1]: Created slice User and Session Slice.
[    6.082797] systemd[1]: Listening on udev Control Socket.
[    6.083075] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
[    6.083376] systemd[1]: Listening on Syslog Socket.
[    6.083594] systemd[1]: Listening on RPCbind Server Activation Socket.
[    6.205659] i2c /dev entries driver
[    6.286037] random: crng init done
[    6.877038] EXT4-fs (sda2): re-mounted. Opts: (null)
[    6.983358] systemd-journald[109]: Received request to flush runtime journal from PID 1
[    7.458462] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
[    7.460893] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
[    7.460909] [vc_sm_connected_init]: start
[    7.468291] media: Linux media interface: v0.10
[    7.472394] [vc_sm_connected_init]: installed successfully
[    7.504572] videodev: Linux video capture interface: v2.00
[    7.553595] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[    7.558100] bcm2835_alsa bcm2835_alsa: card created with 8 channels
[    7.566948] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[    7.596859] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[    7.607127] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
[    7.611821] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[    7.616115] bcm2835-codec bcm2835-codec: Loaded V4L2 encode codec
[    7.616546] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
[    7.618415] voicehat-codec voicehat-codec: property 'voicehat_sdmode_delay' not found default 5 mS
[    7.619764] bcm2835-codec bcm2835-codec: Loaded V4L2 decode codec
[    7.631115] snd-rpi-simple soc:sound: ASoC: CPU DAI (null) not registered - will retry
[    7.662202] snd-rpi-simple soc:sound: ASoC: CPU DAI (null) not registered - will retry
[    7.666562] snd-rpi-simple soc:sound: voicehat-codec <-> 3f203000.i2s mapping ok
[    7.835263] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    7.914576] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    7.917373] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    7.917395] cfg80211: failed to load regulatory.db
[    7.970026] usbcore: registered new interface driver uas
[    8.000886] brcmfmac: F1 signature read @0x18000000=0x15264345
[    8.012374] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    8.013384] usbcore: registered new interface driver brcmfmac
[    8.015796] lan78xx 1-1.1.1:1.0 enxb827eb3cd8c4: renamed from eth0
[    8.061118] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    8.245506] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[    8.263307] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
[    8.352380] brcmfmac mmc1:0001:1 wlxb827eb698d91: renamed from wlan0
[    9.724694] uart-pl011 3f201000.serial: no DMA platform data
[   10.846847] IPv6: ADDRCONF(NETDEV_UP): wlxb827eb698d91: link is not ready
[   10.846868] brcmfmac: power management disabled
[   11.095848] IPv6: ADDRCONF(NETDEV_UP): enxb827eb3cd8c4: link is not ready
[   11.299938] voicehat-codec voicehat-codec: Enabling audio amp...
[   11.369550] voicehat-codec voicehat-codec: Enabling audio amp...
[   11.532623] voicehat-codec voicehat-codec: Disabling audio amp...
[   12.543313] Adding 102396k swap on /var/swap.  Priority:-2 extents:1 across:102396k FS
[   16.820107] Bluetooth: Core ver 2.22
[   16.820202] NET: Registered protocol family 31
[   16.820209] Bluetooth: HCI device and connection manager initialized
[   16.820234] Bluetooth: HCI socket layer initialized
[   16.820254] Bluetooth: L2CAP socket layer initialized
[   16.820291] Bluetooth: SCO socket layer initialized
[   16.839562] Bluetooth: HCI UART driver ver 2.3
[   16.839576] Bluetooth: HCI UART protocol H4 registered
[   16.839674] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   16.839960] Bluetooth: HCI UART protocol Broadcom registered
[   19.320595] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   19.320607] Bluetooth: BNEP filters: protocol multicast
[   19.320627] Bluetooth: BNEP socket layer initialized
[   19.405541] Bluetooth: RFCOMM TTY layer initialized
[   19.405567] Bluetooth: RFCOMM socket layer initialized
[   19.405589] Bluetooth: RFCOMM ver 1.11
[   41.384915] FS-Cache: Duplicate cookie detected
[   41.384935] FS-Cache: O-cookie c=1a1a1f06 [p=bf83675e fl=222 nc=0 na=1]
[   41.384938] FS-Cache: O-cookie d=45209ba1 n=f2b432ef
[   41.384942] FS-Cache: O-key=[10] '0400020008010a0101e6'
[   41.384973] FS-Cache: N-cookie c=47697448 [p=bf83675e fl=2 nc=0 na=1]
[   41.384979] FS-Cache: N-cookie d=45209ba1 n=da3b8498
[   41.384982] FS-Cache: N-key=[10] '0400020008010a0101e6'
[   43.421645] IPv6: ADDRCONF(NETDEV_CHANGE): wlxb827eb698d91: link becomes ready
[   69.144067] fuse init (API version 7.27)
[   70.166434] voicehat-codec voicehat-codec: Enabling audio amp...
[   70.237066] voicehat-codec voicehat-codec: Enabling audio amp...
[  134.222334] brcmfmac: brcmf_run_escan: error (-52)
[  134.222345] brcmfmac: brcmf_cfg80211_scan: scan error (-52)
[  135.224605] brcmfmac: brcmf_run_escan: error (-52)
[  135.224620] brcmfmac: brcmf_cfg80211_scan: scan error (-52)
[  136.226775] brcmfmac: brcmf_run_escan: error (-52)
[  136.226784] brcmfmac: brcmf_cfg80211_scan: scan error (-52)
[  187.576068] FS-Cache: Duplicate cookie detected
[  187.576080] FS-Cache: O-cookie c=a51977c5 [p=bf83675e fl=222 nc=0 na=1]
[  187.576084] FS-Cache: O-cookie d=45209ba1 n=99727ac9
[  187.576087] FS-Cache: O-key=[10] '0400020008010a0101e6'
[  187.576112] FS-Cache: N-cookie c=eefd448e [p=bf83675e fl=2 nc=0 na=1]
[  187.576115] FS-Cache: N-cookie d=45209ba1 n=49c47ab3
[  187.576117] FS-Cache: N-key=[10] '0400020008010a0101e6'
[  187.644022] FS-Cache: Duplicate cookie detected
[  187.644043] FS-Cache: O-cookie c=c41dd5f4 [p=bf83675e fl=222 nc=0 na=1]
[  187.644046] FS-Cache: O-cookie d=45209ba1 n=9e9f68c3
[  187.644051] FS-Cache: O-key=[10] '0400020008010a0101e6'
[  187.644080] FS-Cache: N-cookie c=0248fcf1 [p=bf83675e fl=2 nc=0 na=1]
[  187.644083] FS-Cache: N-cookie d=45209ba1 n=e5e93162
[  187.644085] FS-Cache: N-key=[10] '0400020008010a0101e6'
[  194.231677] brcmfmac: brcmf_run_escan: error (-52)
[  194.231685] brcmfmac: brcmf_cfg80211_scan: scan error (-52)
[  195.241316] brcmfmac: brcmf_run_escan: error (-52)
[  195.241331] brcmfmac: brcmf_cfg80211_scan: scan error (-52)
[  196.244004] brcmfmac: brcmf_run_escan: error (-52)
[  196.244019] brcmfmac: brcmf_cfg80211_scan: scan error (-52)
[  474.072586] nfs: server 10.1.1.230 not responding, still trying
[  553.501959] nf_conntrack: default automatic helper assignment has been turned off for security reasons and CT-based  firewall rule not found. Use the iptables CT target to attach helpers instead.
[  732.131786] nfs: server 10.1.1.230 OK
That one is going back to 4.14.79-v7+

EDIT: I'm getting the same kind of failure on my 3A+ Raspberries.
Last edited by DougieLawson on Mon Feb 18, 2019 9:26 pm, edited 1 time in total.
Note: Having anything humorous in your signature is completely banned on this forum. Wear a tin-foil hat and you'll get a ban.

Any DMs sent on Twitter will be answered next month.

This is a doctor free zone.

mby
Posts: 11
Joined: Sat Dec 15, 2018 3:05 pm

Re: Moving Linux kernel to 4.19

Mon Feb 18, 2019 9:25 pm

Agreed, Wi-Fi performance is a challenge in my 3B+ and, if used before, one has to remember to uncomment the fake driver with #dtoverlay=vc4-fkms-v3d in /boot/config.txt to avoid the hang; other than that, everything else seem to work smoothly and fast, thank you!

suthernfriend
Posts: 1
Joined: Mon Dec 10, 2018 12:17 pm

Re: Moving Linux kernel to 4.19

Mon Feb 18, 2019 10:17 pm

thank you for this update, i've been waiting for a few months for it! :)

I'm going to test the 4.19 kernel during the next few days on 1500+ pis and will report problems that i might find here.

cjan
Posts: 737
Joined: Sun May 06, 2012 12:00 am

Re: Moving Linux kernel to 4.19

Tue Feb 19, 2019 12:12 am

why didn't update firmware still 4.14.94 ?

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

Re: Moving Linux kernel to 4.19

Tue Feb 19, 2019 12:13 pm

cjan wrote:
Tue Feb 19, 2019 12:12 am
why didn't update firmware still 4.14.94 ?
I think you'll have to explain what you have done to get any help.
Have you run rpi-update? What did it output? Have you rebooted? What does uname -a report?

cjan
Posts: 737
Joined: Sun May 06, 2012 12:00 am

Re: Moving Linux kernel to 4.19

Tue Feb 19, 2019 12:32 pm

dom wrote:
Tue Feb 19, 2019 12:13 pm
cjan wrote:
Tue Feb 19, 2019 12:12 am
why didn't update firmware still 4.14.94 ?
I think you'll have to explain what you have done to get any help.
Have you run rpi-update? What did it output? Have you rebooted? What does uname -a report?
don't know does it call firmware or not? but saw it in github

Code: Select all

modules	kernel bump to 4.19.23	20 hours ago
overlays	        kernel bump to 4.19.23	20 hours ago
vc	                kernel: Bump to 4.14.94	28 days ago

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

Re: Moving Linux kernel to 4.19

Tue Feb 19, 2019 4:02 pm

cjan wrote:
Tue Feb 19, 2019 12:32 pm
don't know does it call firmware or not? but saw it in github
Not really sure what you are saying. That shows the kernel and modules are at 4.19.23.
If you want to test it follow instructions in first post of this thread or you can wait until it reaches apt/raspbian later.

ncguk
Posts: 27
Joined: Fri Mar 07, 2014 10:04 pm

Re: Moving Linux kernel to 4.19

Tue Feb 19, 2019 8:26 pm

Have upgraded to 4.19 kernel on a Pi Zero W running Raspbian and a Raspberry Pi 2 running Arch. Both failed to start on first reboot, but after pulling the plug on them and cold booting them, both came up fine. Just posting that in case anyone runs into the same issue and thinks their install is knackered.

mby
Posts: 11
Joined: Sat Dec 15, 2018 3:05 pm

Re: Moving Linux kernel to 4.19

Tue Feb 19, 2019 10:36 pm

mby wrote:
Mon Feb 18, 2019 9:25 pm
Agreed, Wi-Fi performance is a challenge in my 3B+ and, if used before, one has to remember to uncomment the fake driver with #dtoverlay=vc4-fkms-v3d in /boot/config.txt to avoid the hang; other than that, everything else seem to work smoothly and fast, thank you!
With the additional update via update&upgrade from a few minutes ago, everything works again, thank you!

runboy93
Posts: 352
Joined: Tue Feb 28, 2017 1:17 pm
Location: Finland
Contact: Website

Re: Moving Linux kernel to 4.19

Tue Feb 19, 2019 11:05 pm

Whoa just noticed 4.19.23 quite nice, so next image downloads will be based on 4.19 kernels already? :o 4.14 wasn't so long online.

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

Re: Moving Linux kernel to 4.19

Tue Feb 19, 2019 11:14 pm

runboy93 wrote:
Tue Feb 19, 2019 11:05 pm
Whoa just noticed 4.19.23 quite nice, so next image downloads will be based on 4.19 kernels already? :o 4.14 wasn't so long online.
The first post says that moving to 4.19 for raspian sdcard images and apt upgrades is the final goal.
Currently we're still testing with users on rpi-update kernels.
Assuming no major issues apt and sdcard images will switch to 4.19 kernel in the next month or two.

dariuszb
Posts: 33
Joined: Sun Feb 21, 2016 3:55 pm

Re: Moving Linux kernel to 4.19

Wed Feb 20, 2019 10:44 am

Raspberry Pi 2 running Raspbian after upgrade to kernel 4.19 failed to reboot.Turning power off and on made it run however I noticed that sometimes when rebooting from command line it does not start again - I have to do hard restart. Will play a bit more and report more details.
Last edited by dariuszb on Wed Feb 20, 2019 5:53 pm, edited 1 time in total.

Return to “Advanced users”