Hi Russell, As it happens, I just finished bisecting the stable tree yesterday. The offending patch (459e3a21535ae3c7a9a123650e54f5c882b8fcbf) addresses some gcc-9 warnings. Reverting that patch fixes everything.
I submitted bug 203935 to bugzilla.kernel.org today. More observations below, Cheers ... Duncan. On Wed, Jun 19, 2019 at 11:16:41PM +1000, luv-main wrote: > On Tuesday, 28 May 2019 4:27:53 PM AEST Duncan Roe via luv-main wrote: > > Following Andrew's exhortations at the last main meeting, I built 5.1 and > > installed it on my laptop. > > I usually try to avoid building kernels, compiling a kernel with the same > settings as Debian uses takes too long and changing the settings to a minimal > set that matches what I want to do is more effort than I want. Currently > Debian/Experimental only has 5.0. I have a customised version of the standard Slackware .config. Running *make xconfig* on successive kernel revisions keeps it updated. I do keep it under tight revision control, keeping automatic updates separate from any I do. > > > I went back to 5.0 and checked what was in debug.log (which logs > > everything). And there was nothing at all! No hint that 5.1 had ever > > started - just a 7 minute gap between the last 5.0 shutdown and 5.0 > > starting. > > Did any other log file have anything in that time period? No > > Was networking operational, could you ping it? If so network logging might > work. Didn't try a ping from another system, that would have been a nice idea. > > Did you try configuring your system to disable video mode changes? No > > Serial console might be an option, but not many systems have proper serial > ports nowadays. I had a console all right. But I couldn't log in. > > > Have you seen this email before? Please mail me off-list if so. > > > > I originally sent this on 13th May but didn't see it come back. > > It got delivered to me then and was in my lists folder with lots of other > unread mail from months ago. Maybe people just couldn't think of good > suggestions to offer you. Maybe so. Bit *I* didn't see my own email even though I configured to see it. Mail to the list owner about that has gone unanswered. It took me weeks to think of trying a bisect. That required acceptance that the problem was with the kernel. _______________________________________________ luv-main mailing list [email protected] https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
