kernel 4.19.y freezes Raspberry B+

Open
#3,568 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c, linux, raspberry-pi

Research direction

Start by reviewing kernel.log and the reported kernel 4.19.y configuration, including the bcm2835_defconfig changes and the staging IL9486 driver. Compare the setup with the stable 4.4.y kernel and the listed Buildroot toolchain and firmware details. Done means identifying a reproducible cause or a focused subsystem and documenting evidence for the complete freeze.

Written by the indexing model from the issue text.

Description

Hi,

I have a problem, that kernel 4.19.y is freezing Raspberry B+ after few hours. Freezing does mean a complete freeze - all threads are dead - the device is not answering the serial debug interface or ethernet nor any led is on.

I have compiled the kernel by myself with buildroot 20.02 toolchain gcc 8.3.0 / glibc. The kernel has just a few changes to the bcm2835_defconfig (unneeded drivers disabled) and staging driver for tiny TFT IL9486.

The rootfs is a minimal buildroot embedded system. EXT4 with journaling disabled - mounted with noatime and nodiratime option. Minimal write accesses (once a day).

Firmware (bootcode.bin fixup.dat ...) are latest version dated 04/20/20.

The Raspberry is not overclocked. It seems not to be a power supply problem (kernel 4.4.y is running stable for months). The board is running with a core temperature of 38°C - RAM usage is 32 MB only - CPU usage 2% (before freezing). MicroSD seems to be OK (fsck).

Any suggestion? Here the kernel log:

kernel.log

Dominant language
C
Stars
13.2k
Forks
5.5k
Avg merge
2d 21h
Merged PRs (30d)
21

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/linux

All issues in raspberrypi/linux

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.