On Sun, Dec 09, 2018 at 08:21:11AM +1300, Michael Cree wrote: > On Sun, Dec 09, 2018 at 07:54:52AM +1300, Michael Cree wrote: > > On Sat, Dec 08, 2018 at 12:01:23PM +1300, Michael Cree wrote: > > > On Fri, Dec 07, 2018 at 10:39:58PM +0100, Frank Scheiner wrote: > > > > On 12/7/18 22:06, Michael Cree wrote: > > > > > On Tue, Dec 04, 2018 at 05:38:51PM +0100, Frank Scheiner wrote: > > > > > > As per [1] and our recent discussions the generic 4.x kernels seem > > > > > > to no > > > > > > longer work on Alpha machines which also renders any installer > > > > > > images using > > > > > > the generic 4.x kernels non-working. > > > > Bisection leads to: > > > > dca496451bddea9aa87b7510dc2eb413d1a19dfd is the first bad commit > > Actually I am not so sure about that. It appears that sometimes a > bad kernel can boot which might have lead me astray. That commit > after failing once (assuming I did not make a mistake in the > bisection) is now booting...
It would appear that I accidently marked one step in the bisection incorrectly but I have now identified the problem commit and it makes a lot more sense. The first bad commit is commit b38d08f3181c5025a7ce84646494cc4748492a3b Author: Tejun Heo <[email protected]> Date: Tue Sep 2 14:46:02 2014 -0400 percpu: restructure locking The commit prior to that one boots reliably but this one fails to boot a generic kernel. I'll report it to the linux kernel mail list. Cheers, Michael.
