I see a couple of other posts with same issue.
https://www.reddit.com/r/voidlinux/comments/nchtph/kernel_51037_1_boot_probl...
Charles Wright wrote...
I see a couple of other posts with same issue.
Count me in. It's not a global issue, though, various machine rebooted without any problems. Only failing device so far was an old x200 Thinkpad - stalls before console gets intialized, so I have no idea at all what went wrong there. And I'm sorry, I don't have the time for bisecting at the moment.
Christoph
On Sun, May 16, 2021 at 06:00:14PM +0200, Christoph Biedl wrote:
Charles Wright wrote...
I see a couple of other posts with same issue.
Count me in. It's not a global issue, though, various machine rebooted without any problems. Only failing device so far was an old x200 Thinkpad - stalls before console gets intialized, so I have no idea at all what went wrong there. And I'm sorry, I don't have the time for bisecting at the moment.
Hopefully now fixed in the stable queue, I'll push out new -rc releases today for people to test.
thanks,
greg k-h
On Mon, May 17, 2021 at 01:38:34PM +0200, Christoph Biedl wrote:
Greg KH wrote...
Hopefully now fixed in the stable queue, I'll push out new -rc releases today for people to test.
Thanks for taking care, unfortunately no improvement with 5.10.38-rc1 here.
There is no -rc kernel out yet.
Ah, you must be looking at the stable-rc tree, here, let me push out a newer one...
Christoph Biedl wrote...
Thanks for taking care, unfortunately no improvement with 5.10.38-rc1 here.
So in case this is related to the .config, I'm attaching it. Hardware is, as said before, an old Thinkpad x200, vendor BIOS and no particular modifications. After disabling all vga/video/fbcon parameters I see the system suffers a kernel panic but unfortunately only the last 25 lines are visible. Possibly (typos are mine)
RIP: 0010:__domain_mapping+0xa7/0x3a0
is a hint into the right direction?
Chistoph
+cc iommu list.
Christoph Biedl linux-kernel.bfrz@manchmal.in-ulm.de 于2021年5月17日周一 下午1:52写道:
Christoph Biedl wrote...
Thanks for taking care, unfortunately no improvement with 5.10.38-rc1 here.
So in case this is related to the .config, I'm attaching it. Hardware is, as said before, an old Thinkpad x200, vendor BIOS and no particular modifications. After disabling all vga/video/fbcon parameters I see the system suffers a kernel panic but unfortunately only the last 25 lines are visible. Possibly (typos are mine)
RIP: 0010:__domain_mapping+0xa7/0x3a0
is a hint into the right direction?
This looks intel_iommu related, can you try boot with "intel_iommu=off" in kernel parameter?
Chistoph
Regards, Jack Wang
Jack Wang wrote...
Christoph Biedl linux-kernel.bfrz@manchmal.in-ulm.de 于2021年5月17日周一 下午1:52写道:
Christoph Biedl wrote...
Thanks for taking care, unfortunately no improvement with 5.10.38-rc1 here.
So in case this is related to the .config, I'm attaching it. Hardware is, as said before, an old Thinkpad x200, vendor BIOS and no particular modifications. After disabling all vga/video/fbcon parameters I see the system suffers a kernel panic but unfortunately only the last 25 lines are visible. Possibly (typos are mine)
RIP: 0010:__domain_mapping+0xa7/0x3a0
is a hint into the right direction?
This looks intel_iommu related, can you try boot with "intel_iommu=off" in kernel parameter?
Gotcha. System boots up fine then.
Christoph
Christoph Biedl linux-kernel.bfrz@manchmal.in-ulm.de 于2021年5月17日周一 下午2:25写道:
Jack Wang wrote...
Christoph Biedl linux-kernel.bfrz@manchmal.in-ulm.de 于2021年5月17日周一 下午1:52写道:
Christoph Biedl wrote...
Thanks for taking care, unfortunately no improvement with 5.10.38-rc1 here.
So in case this is related to the .config, I'm attaching it. Hardware is, as said before, an old Thinkpad x200, vendor BIOS and no particular modifications. After disabling all vga/video/fbcon parameters I see the system suffers a kernel panic but unfortunately only the last 25 lines are visible. Possibly (typos are mine)
RIP: 0010:__domain_mapping+0xa7/0x3a0
is a hint into the right direction?
This looks intel_iommu related, can you try boot with "intel_iommu=off" in kernel parameter?
Gotcha. System boots up fine then.
Christoph
So it's caused by this commit[1], and it should be fixed by latest 5.10.38-rc1 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/l... [1]https://lore.kernel.org/stable/20210515132855.4bn7ve2ozvdhpnj4@nabokov.fritz...
On Mon, May 17, 2021 at 02:45:01PM +0200, Jack Wang wrote:
Christoph Biedl linux-kernel.bfrz@manchmal.in-ulm.de 于2021年5月17日周一 下午2:25写道:
Jack Wang wrote...
Christoph Biedl linux-kernel.bfrz@manchmal.in-ulm.de 于2021年5月17日周一 下午1:52写道:
Christoph Biedl wrote...
Thanks for taking care, unfortunately no improvement with 5.10.38-rc1 here.
So in case this is related to the .config, I'm attaching it. Hardware is, as said before, an old Thinkpad x200, vendor BIOS and no particular modifications. After disabling all vga/video/fbcon parameters I see the system suffers a kernel panic but unfortunately only the last 25 lines are visible. Possibly (typos are mine)
RIP: 0010:__domain_mapping+0xa7/0x3a0
is a hint into the right direction?
This looks intel_iommu related, can you try boot with "intel_iommu=off" in kernel parameter?
Gotcha. System boots up fine then.
Christoph
So it's caused by this commit[1], and it should be fixed by latest 5.10.38-rc1 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/l... [1]https://lore.kernel.org/stable/20210515132855.4bn7ve2ozvdhpnj4@nabokov.fritz...
Hopefully the "real" 5.10.38-rc1 release that is out now should fix this. If not, please let us know.
thanks,
greg k-h
Greg KH wrote...
On Mon, May 17, 2021 at 02:45:01PM +0200, Jack Wang wrote:
So it's caused by this commit[1], and it should be fixed by latest 5.10.38-rc1 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/l... [1]https://lore.kernel.org/stable/20210515132855.4bn7ve2ozvdhpnj4@nabokov.fritz...
Hopefully the "real" 5.10.38-rc1 release that is out now should fix this. If not, please let us know.
Good news: Fixed with that "real" 5.10.38-rc1.
Christoph
On Tue, May 18, 2021 at 12:30:15AM +0200, Christoph Biedl wrote:
Greg KH wrote...
On Mon, May 17, 2021 at 02:45:01PM +0200, Jack Wang wrote:
So it's caused by this commit[1], and it should be fixed by latest 5.10.38-rc1 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/l... [1]https://lore.kernel.org/stable/20210515132855.4bn7ve2ozvdhpnj4@nabokov.fritz...
Hopefully the "real" 5.10.38-rc1 release that is out now should fix this. If not, please let us know.
Good news: Fixed with that "real" 5.10.38-rc1.
Wonderful! Thanks for testing and letting us know.
greg k-h
linux-stable-mirror@lists.linaro.org