LM 18.2 crash with Kernel later than 4.4.0.98

Bug #1742335 reported by WindyWeather
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linux Mint
New
Undecided
Unassigned

Bug Description

I was offered a kernel upgrade on my system. But the new kernel would not boot.
It filled the screen with stuff that I cannot report since I don't know how.

The system info and a picture of the GRUB offered list of kernels is provided.
Booting with 4.4.0-098 works and I've been running that for a while.
Anything later than that fails, as far as I can tell.

Linux 18.2

Upgraded in System Upgrade app to accept new kernel.
System would not boot.
Used grub to back up to a previous kernel.
ALWAYS

- I need to remove these later kernels as options to boot. I'll ask on forums how to do that.

Revision history for this message
WindyWeather (windyweather) wrote :
Revision history for this message
WindyWeather (windyweather) wrote :

It was not a crash after all. Linux was working fine all along. It was an update to my AV receiver [ Marantz NR1504 ] that blacked the video. Apparently the change in the receiver was awaiting a reboot of the Linux system to decide to black the video. When I took the Linux system to another monitor - or directly to my Vizio P65 TV - Linux is fine on the latest kernel - 4.13.0-26. At least this is the latest kernel that I'm offered at the moment. The system is on LM 18.2.

I'm still investigating, but after a less than satisfying Tech Support call to Marantz, where they said among other things that they don't support PCs attached to their devices, I'm considering a new receiver from a company that lists PC Gaming as a product focus. Denon and Onkyo both seem to understand that folks want to hook PCs to their receivers and say so clearly in product literature. Also maybe these companies know how to support a complex network device and can offer backing out of updates, which Marantz refused me.

Time for an upgrade anyway since my TV is 4K / HDR capable and my receiver is not.
Sorry for the confusion.

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.