LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: wim <wim@djo.tudelft.nl>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
	wim <wim@djo.tudelft.nl>
Subject: Re: kernel-4.9.270 crash
Date: Sat, 11 Sep 2021 22:49:05 +0200	[thread overview]
Message-ID: <20210911204905.GA18345@djo.tudelft.nl> (raw)
In-Reply-To: <YThKidnH3d1fb18g@kroah.com>

On Wed, Sep 08, 2021 at 07:30:49AM +0200, Greg KH wrote:
> 
> That is a vt change that handles an issue with a console driver, so this
> feels like a false failure.
> 
> If you revert this change on a newer kernel release, does it work?

Oh, you mean a higher version number (which wasn't directly obvious to me).
Make oldconfig gives an awful lot of output which I'm not going to read.
Just keep pressing the return key for all the defaults.
Kernel-5.10.10 runs into a black screen, I can perform a blind login and
play an audio file. I then tried to revert the patch, but git couldn't
complete it. The closest uplevel version is 4.14.246 which I then tried.
It runs into a black screen, but I can login and play audio, but no reaction
on modprobe fbcon. Git revert ran fine, but that also gave me a black
screen. It appeared that there was no fbcon.ko, even worse, the option to
modularize it was gone! Insane.
Since that option was now invalid, make oldconfig chose for a default no,
which I didn't know. In-kernel fbcon gives no problems, I guess.
This led to the discovery that the hard crash in 4.9.270(-282) did NOT occur
when fbcon.ko was not loaded. Modprobe fbcon after i915 went fine.

So here you have another reason to not wanting to run a kernel version above 4.9.
I need fbcon.ko as a diagnostics tool. In many machines with i915 I loose
sound when i915.ko gets loaded. I need to fiddle with the rc scripts to make
sure that the snd modules got loaded first. And because the changing fonts and
layout drives me nuts while looking at the progress, I need to put fbcon/i915
the very last (in rc.local).

Regards, Wim.

      parent reply	other threads:[~2021-09-11 20:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210904235231.GA31607@djo.tudelft.nl>
2021-09-05 19:00 ` wim
2021-09-06  4:59   ` Greg KH
2021-09-06  9:36     ` wim
2021-09-06 10:52       ` Greg KH
2021-09-08  1:51         ` wim
2021-09-08  5:30           ` Greg KH
2021-09-09  0:57             ` wim
2021-09-11 20:49             ` wim [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210911204905.GA18345@djo.tudelft.nl \
    --to=wim@djo.tudelft.nl \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --subject='Re: kernel-4.9.270 crash' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).