Kernel panic: Fatal exception in interrupt

Open
#4,012 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
c, linux

Research direction

No source file, test, or reproducible steps are identified. Start by reproducing the large-file transfer on the Raspberry Pi 4 with Manjaro ARM and capture a complete panic log; done means identifying a reproducible kernel fault and a focused fix or confirmed report.

Written by the indexing model from the issue text.

Description

Describe the bug
Hard to describe, probably during transferring of a large file (3GB) a kernel panic occured.

To reproduce
No idea.

System
This is a Manjaro ARM, there is no raspinfo there.

  • Which model of Raspberry Pi? e.g. Pi3B+, PiZeroW
    Hardware : BCM2835
    Revision : c03111
    Model : Raspberry Pi 4 Model B Rev 1.1

  • Which OS and version (cat /etc/rpi-issue)?
    DISTRIB_ID=Manjaro-ARM
    DISTRIB_RELEASE=20.10
    DISTRIB_CODENAME=
    DISTRIB_DESCRIPTION="Manjaro ARM Linux"
    NAME="Manjaro-ARM"
    ID=manjaro-arm
    ID_LIKE=manjaro arch
    PRETTY_NAME="Manjaro ARM"
    ANSI_COLOR="1;32"
    HOME_URL="https://www.manjaro.org/"
    SUPPORT_URL="https://forum.manjaro.org/c/arm/"

  • Which firmware version (vcgencmd version)?
    Nov 18 2020 19:55:43
    Copyright (c) 2012 Broadcom
    version 8e01026adc5a87d80f8748fc6a4fecb9012393cc (clean) (release) (start_cd)

  • Which kernel version (uname -a)?
    Linux malina 5.4.80-1-MANJARO-ARM #1 SMP PREEMPT Mon Nov 30 08:56:01 CST 2020 aarch64 GNU/Linux

Logs
The only this that I got is a picture taken from console after the kernel panic.
1608318086029

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.