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@xxxxxxxxxxx> > 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
