Clevo N850EL crashes / freezes under Ubuntu 18.04.1

Bug #1789214 reported by Joao Luis
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

The details of what I've attempted so far are in

https://askubuntu.com/questions/1068161/clevo-n850el-crashes-freezes-ubuntu-18-04-1-frequently

Any workaround help greatly appreciated. (I do not need NVIDIA graphics, but I do need VirtualBox).

Regards,

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-33-generic 4.15.0-33.36
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jpsl 1955 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 27 14:56:57 2018
InstallationDate: Installed on 2018-08-22 (4 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 5986:2110 Acer, Inc
 Bus 001 Device 004: ID 0461:4de3 Primax Electronics, Ltd
 Bus 001 Device 003: ID 8087:0025 Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Notebook N8xxEL
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=60daf8a6-ead0-4dc1-9b51-e7fa0fd7304c ro text crashkernel=384M-:4096M
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-33-generic N/A
 linux-backports-modules-4.15.0-33-generic N/A
 linux-firmware 1.173.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/27/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 7.004
dmi.board.asset.tag: Tag 12345
dmi.board.name: N8xxEL
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.004:bd04/27/2018:svnNotebook:pnN8xxEL:pvrNotApplicable:rvnNotebook:rnN8xxEL:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: N8xxEL
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook

Revision history for this message
Joao Luis (jpluis) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18.3

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Joao Luis (jpluis) wrote :

> Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

No upgrade. This is a fresh install, on a brand new laptop computer.

> Please test the latest v4.18 kernel[0].

I've tested the mainline kernel build v4.18.5, 2 days ago, which showed the same problem.

Tomorrow, I will test another proposed work-around of adding kernel parameter intel_idle.max_cstate=1 for about 8 hours. (It is looking good today, but only 1 hour of uptime so far...)

Then I will test the v4.18.3 kernel (if ok, the test will take at least 8 hours - 1 full day of work), and I will give feedback here.

Thank you for feedback.

Revision history for this message
Joao Luis (jpluis) wrote :

Good evening!

I can give feedback right away from the last 2 notes.

The other workaround proposed (in askubuntu.com) of adding a kernel parameter intel_idle.max_cstate=1 seems to work well (max uptime tested is 6h 45min so far).

Regarding the indication to use 4.18.3-041803-generic, I downloaded and installed the packages (for my own record):

linux-headers-4.18.3-041803_4.18.3-041803.201808180530_all.deb
linux-headers-4.18.3-041803-generic_4.18.3-041803.201808180530_amd64.deb
linux-image-unsigned-4.18.3-041803-generic_4.18.3-041803.201808180530_amd64.deb
linux-modules-4.18.3-041803-generic_4.18.3-041803.201808180530_amd64.deb

The boot cmdline was:

root@jpsl-N8xxEL:~# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.18.3-041803-generic root=UUID=60daf8a6-ead0-4dc1-9b51-e7fa0fd7304c ro text
(
( Note that, it is without intel_idle.max_cstate=1 ) the kernel 4.18.3-041803-generic crashes / freezes frequently also. Already tested 3 times, so I added the tag kernel-bug-exists-upstream

(I should also mention that if I give the command "reboot" or "poweroff" using this kernel, it always freezes - but I don't know if this is related or not).

tags: added: kernel-bug-exists-upstream
Joao Luis (jpluis)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joao Luis (jpluis) wrote :

Just for information, that trying out Ubuntu 18.10 kernel 4.18.0-10-generic booting from USB pen, the problem remains (and the intel_idle.max_cstate=1 workaround still works).

Brad Figg (brad-figg)
tags: added: cscc
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.