On Wed, 15 Apr 2020 17:13:30 +0100 Ken Moffat <[email protected]> wrote:
> On Wed, Apr 15, 2020 at 10:41:27AM +0200, Stephen Berman wrote: [...] >> > 1. Configure the kernel. Is it nessary to do `make oldconfig' using the >> > 4.20.12 config file, or could I just run make with that config file >> > on later kernel sources? >> > 2. Build and install the kernel and modules. >> > 3. Reboot and then do `shutdown -h now'. >> > 4. Reboot. >> > 5. Lather, rinse, repeat. >> >> What I described here is a manual bisection; I don't see how I can use >> `git bisect' to do this, because I have to restart the process after >> each reboot. If I've misunderstood, I'd appreciate it if someone would >> give me a step by step recipe for how to do it. >> > > Git stores its state in the '.git/' and works fine across reboots. Ah, thanks, that didn't occur to me. > Look for information on 'git bisect' to better understand the > process. It is absolutely normal for kernel problems to be bisected > on the machine where the problem is happening. > > But - > >> Be that as it may, in the mean time I've cloned the mainline kernel >> repository, checked out 5.3.0 as the approximate midpoint between the >> known good (4.20.12) and bad (5.5.9) versions of the stable kernel, >> built and installed it, rebooted with this kernel, and here, too, >> `shutdown -h now' failed to power off the computer. One difference from >> 5.5.9 and 5.6.4 is that there was no "timing out command" message after >> "Bringing down the loopback interface", even though I waited more than >> two minutes. >> > Possibly two bugs, or an added descriptive message in a later commit > to highlight the problem. That's what I think too. >> However, I have discovered a pattern which seems significant: if, after >> booting, I immediately do `shutdown -h now' (i.e., from the tty, without >> starting X or any other program), then the machine does power off, 20 >> seconds after the "Bringing down the loopback interface" message; I've >> replicated this with 5.3.0 and 5.6.4. But if I run another program >> before shutdown (the two cases I've tried are startx and emacs in the >> tty), then shutdown does not power off the machine. >> > > So, something in userspace is triggering this. Which window manager > are you using for this ? Openbox, but as I noted, the poweroff failure also happened when I ran emacs in a tty, i.e., without starting X at all. Steve Berman -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
