unable to handle kernel NULL pointer dereference

Bug #1710283 reported by davidak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
elementary OS
New
Undecided
Unassigned
linux (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

The system was frozen and never recovered. I waited 1 hour!

Last command i executed short before this happened:

mv code/ kk

(the directory contains 2.2 GB of git repositorys)

see attached syslog output.

---

elementary OS 0.4.1 Loki (based on Ubuntu 16.04.2 LTS)
Kernel: Linux 4.10.0-32-generic
on Dell Latitude E5470 (Intel i5, 8 GB RAM)

ProblemType: Bug
DistroRelease: elementary 0.4.1
Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Pantheon
Date: Fri Aug 11 21:18:04 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-08-10 (1 days ago)
InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170517)
SourcePackage: linux-hwe
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
davidak (davidak) wrote :
affects: linux-hwe (Ubuntu) → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1710283

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: zesty
Revision history for this message
davidak (davidak) wrote :

There are many logs attached like the syslog, so you should have any information.

I'm not running the software or have access to the hardware anymore.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.