You are not logged in.
Upgrading from linux 4.17 to 4.18 provided me with unbootable kernel. Linux 4.18 does not boot even in fallback mode. 4.19-rc3 is also affected. This is my first time debugging the kernel.
I have HP 6730b laptop with Intel Core 2 Duo P8600 CPU, so I thought my issue was related to this thread. But after I bisected linux-git, it looks like my issue is something different.
I bisected linux-git by the instructions given in the wiki and that provided me with this:
84c8b58ed3addf17d3beb2e5037b001ffa65c5ef is the first bad commit
https://git.kernel.org/pub/scm/linux/ke … 1ffa65c5ef
Do I have enough information to report this upstream? Or may this be something only related to Arch?
Last edited by GoatWarning (2018-09-18 03:31:34)
Offline
As a cross check you could checkout v4.18 then revert 84c8b58ed3addf17d3beb2e5037b001ffa65c5 and test if that boots successfully.
Offline
Yes, reverting 84c8b58ed3addf17d3beb2e5037b001ffa65c5 made 4.18 boot successfully.
Offline
Report it upstream to the kernel developers/maintainers.
According to the script get_maintainer.pl for drivers/pci/hotplug/acpiphp_glue.c:
"Rafael J. Wysocki" <rjw@rjwysocki.net> (supporter:ACPI)
Len Brown <lenb@kernel.org> (supporter:ACPI)
Bjorn Helgaas <bhelgaas@google.com> (supporter:PCI SUBSYSTEM)
linux-acpi@vger.kernel.org (open list:ACPI)
linux-pci@vger.kernel.org (open list:PCI SUBSYSTEM)
linux-kernel@vger.kernel.org (open list)
These are to be contacted for your issue depending on their preference.
You should either report it to https://bugzilla.kernel.org or to the corresponding mailing list(s).
Offline
As loqs, a while ago, pointed out to me, follow this bug reporting guide: https://www.kernel.org/doc/html/latest/ … -bugs.html
Offline
Thanks NiceGuy, I already had found that guide and used get_maintainer.pl to get those maintainers
I already reported this on at Bugzilla as the MAINTAINERS file has a line "B: https://bugzilla.kernel.org" on the ACPI section. But Greg Kroah-Hartman pointed me to the linux-pci@vger.kernel.org mailing list and I sent my report there.
This is the original bug report:
https://bugzilla.kernel.org/show_bug.cgi?id=201127
I only sent mail to the linux-pci@vger.kernel.org (as given by GKH). Maybe I should have sent to all the maintainers listed by the get_maintainer.pl script. I'm not very familiar with mailing lists, (how) should I correct this?
Offline
Do as you were instructed to do it, otherwise you might get a "strong" and overly annoyed reply by the already overworked kernel developers.
Depending on their mood, some would call it "cursing".
Offline
[Edited:] after re-reading GoatWarning's previous post and not providing any additional info here I stripped this forum post. My bad.
Last edited by NiceGuy (2018-09-14 13:34:58)
Offline
I only sent mail to the linux-pci@vger.kernel.org (as given by GKH). Maybe I should have sent to all the maintainers listed by the get_maintainer.pl script. I'm not very familiar with mailing lists, (how) should I correct this?
Then you are done. Just wait for a response. This could take a few days, so after the weekend you should get a reply from the kernel developers.
Last edited by NiceGuy (2018-09-14 13:36:15)
Offline
I can not find the email in the list archive at https://www.spinics.net/lists/linux-pci/index.html. Can you please post a link to your thread.
Offline
Offline
Upgrading from linux 4.17 to 4.18 provided me with unbootable kernel. Linux 4.18 does not boot even in fallback mode. 4.19-rc3 is also affected. This is my first time debugging the kernel.
...
Having had a similar problem with a relatives core 2 duo laptop,
and noting your other post, I have to ask; Have you tried to
grub-mkconfig / grub-install ( or simply use "grub customizer"
to do the same thing ) recently ???
Offline
Having had a similar problem with a relatives core 2 duo laptop,
and noting your other post, I have to ask; Have you tried to
grub-mkconfig / grub-install ( or simply use "grub customizer"
to do the same thing ) recently ???
No I haven't. I don't use grub. I boot my system using systemd-boot.
Offline
I re-sent the bug report as I was missing important recipients. After all, the Linux bug reporting guide says:
... regressions, kernel crashes, security holes, or userspace breakage caused by new kernel behavior. Those bugs should be addressed by the maintainers ASAP.
I know this was over a weekend, but I wanted to be sure that the bug report gets the developers as soon as it can. I hadn't had response to the old mail yet. I sent a note to the old thread to note that I resent the report and to ignore the old thread. It seems that the linux-pci archive has some delay so my post doesn't show up yet.
New thread:
https://marc.info/?l=linux-acpi&m=153716394411357
Last edited by GoatWarning (2018-09-19 11:02:06)
Offline
You could try emailing mika.westerberg@linux.intel.com the author of the commit with a Cc to bhelgaas@google.com the committer although I would suggest waiting (although I do not know how long for).
Edit:
email them pointing to your email on the list.
Edit2:
I see upstream is now working with you and have provide a test patch for you to try.
Last edited by loqs (2018-09-17 17:00:18)
Offline
I see upstream is now working with you and have provide a test patch for you to try.
Yes, I just finished building the kernel twice. And found that commenting out the line(s) work.
https://bugzilla.kernel.org/show_bug.cgi?id=201127#c4
Offline
It's also nice, if this is backported to a stable 4.18.y release.
Either the developer does it or you could e-mail stable@vger.kernel.org with the exact commit after it lands in mainline.
[Edited:] 4.19-rcX to mainline
Last edited by NiceGuy (2018-09-21 15:07:48)
Offline
More info how to proceed with stable-releases:
https://www.kernel.org/doc/html/latest/ … rules.html
Offline
It's also nice, if this is backported to a stable 4.18.y release.
Either the developer does it or you could e-mail stable@vger.kernel.org with the exact commit after it lands in 4.19-rcX.
I'll look into that after it lands in mainline.
Most recent version of the patch:
https://www.spinics.net/lists/linux-pci/msg76587.html
Last edited by GoatWarning (2018-09-25 06:50:51)
Offline
https://git.kernel.org/pub/scm/linux/ke … f421079fe9
queued for 4.18.12
Offline