From: Greg KH <gregkh@linuxfoundation.org>
To: wim <wim@djo.tudelft.nl>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: kernel-4.9.270 crash
Date: Wed, 8 Sep 2021 07:30:49 +0200 [thread overview]
Message-ID: <YThKidnH3d1fb18g@kroah.com> (raw)
In-Reply-To: <20210908015139.GA26272@djo.tudelft.nl>
On Wed, Sep 08, 2021 at 03:51:39AM +0200, wim wrote:
> On Mon, Sep 06, 2021 at 12:52:20PM +0200, Greg KH wrote:
> > > > > >
> > > > > > from kernel-4.9.270 up until now (4.9.282) I experience kernel crashes upon
> > > > > > loading a GPU module.
> > > > > > ...
> > > >
> > > > Do you have any kernel log messages when these crashes happen?
> > > ...
> > > Aug 1 20:51:24 djo kernel: [<f8bc4ef7>] ? 0xf8bc4ef7
> >
> > <snip>
> >
> > These aren't going to help us much, can you turn on debugging symbols
> > for these crashes for us to see the symbol names?
>
> ERROR: not enough memory to load nouveau.ko
That's the only error? Maybe you don't have enough memory?
> i915.ko is smaller and my laptop is bigger. Identical crash, no symbols.
Odd.
> > > > Can you use 'git bisect' to track down the offending commit?
> > >
> > > If I would know how to do that
> >
> > 'man git bisect' should provide a tutorial on how to do this.
>
> No, it does not.
> It would have taken an enormous amount of time and GBs less if I'd found
> earlier the only pointer on internet that stated:
>
> cd linux
> git remote add stable git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
>
> and that brought me reasonably fast to this:
>
> 3bd3a8ca5a7b1530f463b6e1cc811c085e6ffa01 is the first bad commit
> commit 3bd3a8ca5a7b1530f463b6e1cc811c085e6ffa01
> Author: Maciej W. Rozycki <macro@orcam.me.uk>
> Date: Thu May 13 11:51:50 2021 +0200
> ...
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?
And what about showing us the symbols of that traceback?
thanks,
greg k-h
next prev parent reply other threads:[~2021-09-08 5:31 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 ` kernel-4.9.270 crash 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 [this message]
2021-09-09 0:57 ` wim
2021-09-11 20:49 ` wim
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=YThKidnH3d1fb18g@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=wim@djo.tudelft.nl \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).