Bug 17907 - kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000060
Summary: kernel: BUG: unable to handle kernel NULL pointer dereference at 000000000000...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-08 09:51 CET by Marja Van Waes
Modified: 2019-02-19 09:37 CET (History)
0 users

See Also:
Source RPM: kernel-4.4.4-1.mga6
CVE:
Status comment:


Attachments
kernel trace (3.70 KB, text/plain)
2016-03-08 09:52 CET, Marja Van Waes
Details

Description Marja Van Waes 2016-03-08 09:51:37 CET
Occasionally, when switching from Plasma5 to tty2 or another VT, my system crashes.

This has happened at least 3 times since I made a clean Mga5 install to replace my broken cauldron on January 18 and upgraded to cauldron on the same day.
However, I see the error from the Summary 7 times, just don't remember at all whether I switched to a VT from Plasma5, too at those times and am too lazy to check (will do when told it matters)

I'll attach the last trace later, forgot to use the expert bug form
Comment 1 Marja Van Waes 2016-03-08 09:52:15 CET
Created attachment 7525 [details]
kernel trace
Comment 2 Marja Van Waes 2016-03-08 10:00:19 CET
(In reply to Marja van Waes from comment #0)
 just don't remember at
> all whether I switched to a VT from Plasma5, too at those times and am too
> lazy to check (will do when told it matters

It is impossible to see whether I was switching to a VT in the journal.
However, it happened both when already logged in in that VT before, and when not yet logged in.
Comment 3 Marja Van Waes 2016-08-26 11:43:24 CEST
Mass-reassigning all bugs with "kernel" in the Source RPM field that are assigned to tmb, to the kernel packagers group, because tmb is currently MIA.

Assignee: tmb => kernel

Comment 4 Marja Van Waes 2019-02-19 09:37:50 CET
I don't remember having seen such crashes in Mageia 6 or later, so closing

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.