Hi guys,
I am still refining the P2B family of boards, now including the infamous P3B-F with an unusual appetite for hacks to make work.
That said, I'm now finding that, on P3B-F, SeaBIOS hangs when it tries to relocate itself as part of its usual chores. Having just learned git bisect, I decided to try it out.
It was commit 3b02006afe8a85477dafa1bd149f1f0dba02afc7 [1] that broke my SeaBIOS. It doesn't affect my newer toy the P8Z77-M as much as P3B-F, but I still want to blame that, and probably the very next commit as well, as they both deal with some very modern aspects of PCI that well predates the 440BX.
Is there anything we can do to fix 3b02006afe?
Meanwhile I ported the P3B-F board enable to flashrom [2], which got a heavy workout during this bisect, through vendor firmware and both good and bad builds of coreboot. In all cases I can flash internal, no longer having to haul out my P2B-LS just to use it as a flasher.
Enjoy this long overdue board enable. If it gets submitted, I'll retract the ramstage hack[3] doing the same as redundant.
Keith
[1] https://review.coreboot.org/c/coreboot/+/39486 [2] https://review.coreboot.org/c/flashrom/+/41354 [3] https://review.coreboot.org/c/coreboot/+/41224
Dear Keith,
Am 13.05.20 um 05:21 schrieb Keith Hui:
I am still refining the P2B family of boards, now including the infamous P3B-F with an unusual appetite for hacks to make work.
That said, I'm now finding that, on P3B-F, SeaBIOS hangs when it tries to relocate itself as part of its usual chores. Having just learned git bisect, I decided to try it out.
It was commit 3b02006afe8a85477dafa1bd149f1f0dba02afc7 [1] that broke my SeaBIOS. It doesn't affect my newer toy the P8Z77-M as much as P3B-F, but I still want to blame that, and probably the very next commit as well, as they both deal with some very modern aspects of PCI that well predates the 440BX.
Is there anything we can do to fix 3b02006afe?
I commented in the change-set [1] to make the author and reviewers aware of this issue and referenced your list message, and ask to comment here.
Could you please provide the debug log of coreboot and SeaBIOS?
Meanwhile I ported the P3B-F board enable to flashrom [2], which got a heavy workout during this bisect, through vendor firmware and both good and bad builds of coreboot. In all cases I can flash internal, no longer having to haul out my P2B-LS just to use it as a flasher.
Enjoy this long overdue board enable. If it gets submitted, I'll retract the ramstage hack[3] doing the same as redundant.
Very nice! It’s always amazing, how after so many years, when the vendor already stopped supporting the device, the community still supports the device and improves the firmware showing that Free Software is the more sustainable way.
Kind regards,
Paul
[1] https://review.coreboot.org/c/coreboot/+/39486 [2] https://review.coreboot.org/c/flashrom/+/41354 [3] https://review.coreboot.org/c/coreboot/+/41224
Thanks for the report Keith!
On Wed, May 13, 2020 at 3:42 AM Paul Menzel pmenzel@molgen.mpg.de wrote:
Dear Keith,
Am 13.05.20 um 05:21 schrieb Keith Hui:
I am still refining the P2B family of boards, now including the infamous P3B-F with an unusual appetite for hacks to make work.
That said, I'm now finding that, on P3B-F, SeaBIOS hangs when it tries to relocate itself as part of its usual chores. Having just learned git bisect, I decided to try it out.
It was commit 3b02006afe8a85477dafa1bd149f1f0dba02afc7 [1] that broke my SeaBIOS. It doesn't affect my newer toy the P8Z77-M as much as P3B-F, but I still want to blame that, and probably the very next commit as well, as they both deal with some very modern aspects of PCI that well predates the 440BX.
Is there anything we can do to fix 3b02006afe?
I commented in the change-set [1] to make the author and reviewers aware of this issue and referenced your list message, and ask to comment here.
Could you please provide the debug log of coreboot and SeaBIOS?
As Paul mentioned, can you please provide the debug logs for coreboot and SeaBIOS both with ToT coreboot and with HEAD set before the change 3b02006afe where it does not hang? Thanks!
Meanwhile I ported the P3B-F board enable to flashrom [2], which got a heavy workout during this bisect, through vendor firmware and both good and bad builds of coreboot. In all cases I can flash internal, no longer having to haul out my P2B-LS just to use it as a flasher.
Enjoy this long overdue board enable. If it gets submitted, I'll retract the ramstage hack[3] doing the same as redundant.
Very nice! It’s always amazing, how after so many years, when the vendor already stopped supporting the device, the community still supports the device and improves the firmware showing that Free Software is the more sustainable way.
Kind regards,
Paul
[1] https://review.coreboot.org/c/coreboot/+/39486 [2] https://review.coreboot.org/c/flashrom/+/41354 [3] https://review.coreboot.org/c/coreboot/+/41224
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
Thanks Furquan.
Here are 3 logs. Log 1 is at the commit just before the problem. Log 2 is at the problem commit. Log 3 is at the current master, if that's what you meant by ToT.
I'm using SeaBIOS 1.13.0, compiled once using the attached .config before taking these logs. All 3 runs are taken using the same SeaBIOS binary.
Then I recompiled SeaBIOS with CONFIG_RELOCATE_INIT off, replaced the payload used in run 3, and took an extra run. In this case the board reset on its own at "Scanning option roms", looping infinitely.
Hope this helps Keith
On Wed, May 13, 2020 at 7:38 AM Furquan Shaikh furquan.m.shaikh@gmail.com wrote:
Thanks for the report Keith!
On Wed, May 13, 2020 at 3:42 AM Paul Menzel pmenzel@molgen.mpg.de wrote:
Dear Keith,
Am 13.05.20 um 05:21 schrieb Keith Hui:
I am still refining the P2B family of boards, now including the infamous P3B-F with an unusual appetite for hacks to make work.
That said, I'm now finding that, on P3B-F, SeaBIOS hangs when it tries to relocate itself as part of its usual chores. Having just learned git bisect, I decided to try it out.
It was commit 3b02006afe8a85477dafa1bd149f1f0dba02afc7 [1] that broke my SeaBIOS. It doesn't affect my newer toy the P8Z77-M as much as P3B-F, but I still want to blame that, and probably the very next commit as well, as they both deal with some very modern aspects of PCI that well predates the 440BX.
Is there anything we can do to fix 3b02006afe?
I commented in the change-set [1] to make the author and reviewers aware of this issue and referenced your list message, and ask to comment here.
Could you please provide the debug log of coreboot and SeaBIOS?
As Paul mentioned, can you please provide the debug logs for coreboot and SeaBIOS both with ToT coreboot and with HEAD set before the change 3b02006afe where it does not hang? Thanks!
Meanwhile I ported the P3B-F board enable to flashrom [2], which got a heavy workout during this bisect, through vendor firmware and both good and bad builds of coreboot. In all cases I can flash internal, no longer having to haul out my P2B-LS just to use it as a flasher.
Enjoy this long overdue board enable. If it gets submitted, I'll retract the ramstage hack[3] doing the same as redundant.
Very nice! It’s always amazing, how after so many years, when the vendor already stopped supporting the device, the community still supports the device and improves the firmware showing that Free Software is the more sustainable way.
Kind regards,
Paul
[1] https://review.coreboot.org/c/coreboot/+/39486 [2] https://review.coreboot.org/c/flashrom/+/41354 [3] https://review.coreboot.org/c/coreboot/+/41224
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
I think the following patch will fix things up: https://review.coreboot.org/c/coreboot/+/41363 Please let me know.
On Wed, May 13, 2020 at 8:43 AM Keith Hui buurin@gmail.com wrote:
Thanks Furquan.
Here are 3 logs. Log 1 is at the commit just before the problem. Log 2 is at the problem commit. Log 3 is at the current master, if that's what you meant by ToT.
I'm using SeaBIOS 1.13.0, compiled once using the attached .config before taking these logs. All 3 runs are taken using the same SeaBIOS binary.
Then I recompiled SeaBIOS with CONFIG_RELOCATE_INIT off, replaced the payload used in run 3, and took an extra run. In this case the board reset on its own at "Scanning option roms", looping infinitely.
Hope this helps Keith
On Wed, May 13, 2020 at 7:38 AM Furquan Shaikh furquan.m.shaikh@gmail.com wrote:
Thanks for the report Keith!
On Wed, May 13, 2020 at 3:42 AM Paul Menzel pmenzel@molgen.mpg.de
wrote:
Dear Keith,
Am 13.05.20 um 05:21 schrieb Keith Hui:
I am still refining the P2B family of boards, now including the infamous P3B-F with an unusual appetite for hacks to make work.
That said, I'm now finding that, on P3B-F, SeaBIOS hangs when it
tries
to relocate itself as part of its usual chores. Having just learned git bisect, I decided to try it out.
It was commit 3b02006afe8a85477dafa1bd149f1f0dba02afc7 [1] that broke my SeaBIOS. It doesn't affect my newer toy the P8Z77-M as much as P3B-F, but I still want to blame that, and probably the very next commit as well, as they both deal with some very modern aspects of
PCI
that well predates the 440BX.
Is there anything we can do to fix 3b02006afe?
I commented in the change-set [1] to make the author and reviewers
aware
of this issue and referenced your list message, and ask to comment
here.
Could you please provide the debug log of coreboot and SeaBIOS?
As Paul mentioned, can you please provide the debug logs for coreboot and SeaBIOS both with ToT coreboot and with HEAD set before the change 3b02006afe where it does not hang? Thanks!
Meanwhile I ported the P3B-F board enable to flashrom [2], which got
a
heavy workout during this bisect, through vendor firmware and both good and bad builds of coreboot. In all cases I can flash internal,
no
longer having to haul out my P2B-LS just to use it as a flasher.
Enjoy this long overdue board enable. If it gets submitted, I'll retract the ramstage hack[3] doing the same as redundant.
Very nice! It’s always amazing, how after so many years, when the
vendor
already stopped supporting the device, the community still supports the device and improves the firmware showing that Free Software is the more sustainable way.
Kind regards,
Paul
[1] https://review.coreboot.org/c/coreboot/+/39486 [2] https://review.coreboot.org/c/flashrom/+/41354 [3] https://review.coreboot.org/c/coreboot/+/41224
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
Hi Aaron,
It didn't help. There still a way out of whack entry in the coreboot table and e820 entry ending at 000003ffffffffff, which I think have more to do than the 41363's scope.
Keith
On Wed, May 13, 2020 at 12:24 PM Aaron Durbin adurbin@google.com wrote:
I think the following patch will fix things up: https://review.coreboot.org/c/coreboot/+/41363 Please let me know.
On Wed, May 13, 2020 at 8:43 AM Keith Hui buurin@gmail.com wrote:
Thanks Furquan.
Here are 3 logs. Log 1 is at the commit just before the problem. Log 2 is at the problem commit. Log 3 is at the current master, if that's what you meant by ToT.
I'm using SeaBIOS 1.13.0, compiled once using the attached .config before taking these logs. All 3 runs are taken using the same SeaBIOS binary.
Then I recompiled SeaBIOS with CONFIG_RELOCATE_INIT off, replaced the payload used in run 3, and took an extra run. In this case the board reset on its own at "Scanning option roms", looping infinitely.
Hope this helps Keith
On Wed, May 13, 2020 at 7:38 AM Furquan Shaikh furquan.m.shaikh@gmail.com wrote:
Thanks for the report Keith!
On Wed, May 13, 2020 at 3:42 AM Paul Menzel pmenzel@molgen.mpg.de wrote:
Dear Keith,
Am 13.05.20 um 05:21 schrieb Keith Hui:
I am still refining the P2B family of boards, now including the infamous P3B-F with an unusual appetite for hacks to make work.
That said, I'm now finding that, on P3B-F, SeaBIOS hangs when it tries to relocate itself as part of its usual chores. Having just learned git bisect, I decided to try it out.
It was commit 3b02006afe8a85477dafa1bd149f1f0dba02afc7 [1] that broke my SeaBIOS. It doesn't affect my newer toy the P8Z77-M as much as P3B-F, but I still want to blame that, and probably the very next commit as well, as they both deal with some very modern aspects of PCI that well predates the 440BX.
Is there anything we can do to fix 3b02006afe?
I commented in the change-set [1] to make the author and reviewers aware of this issue and referenced your list message, and ask to comment here.
Could you please provide the debug log of coreboot and SeaBIOS?
As Paul mentioned, can you please provide the debug logs for coreboot and SeaBIOS both with ToT coreboot and with HEAD set before the change 3b02006afe where it does not hang? Thanks!
Meanwhile I ported the P3B-F board enable to flashrom [2], which got a heavy workout during this bisect, through vendor firmware and both good and bad builds of coreboot. In all cases I can flash internal, no longer having to haul out my P2B-LS just to use it as a flasher.
Enjoy this long overdue board enable. If it gets submitted, I'll retract the ramstage hack[3] doing the same as redundant.
Very nice! It’s always amazing, how after so many years, when the vendor already stopped supporting the device, the community still supports the device and improves the firmware showing that Free Software is the more sustainable way.
Kind regards,
Paul
[1] https://review.coreboot.org/c/coreboot/+/39486 [2] https://review.coreboot.org/c/flashrom/+/41354 [3] https://review.coreboot.org/c/coreboot/+/41224
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
OK. I'll take a look at your logs and see what's going on. The patch link I sent was based off of someone else's mainboard logs.
On Wed, May 13, 2020 at 10:59 AM Keith Hui buurin@gmail.com wrote:
Hi Aaron,
It didn't help. There still a way out of whack entry in the coreboot table and e820 entry ending at 000003ffffffffff, which I think have more to do than the 41363's scope.
Keith
On Wed, May 13, 2020 at 12:24 PM Aaron Durbin adurbin@google.com wrote:
I think the following patch will fix things up:
https://review.coreboot.org/c/coreboot/+/41363 Please let me know.
On Wed, May 13, 2020 at 8:43 AM Keith Hui buurin@gmail.com wrote:
Thanks Furquan.
Here are 3 logs. Log 1 is at the commit just before the problem. Log 2 is at the problem commit. Log 3 is at the current master, if that's what you meant by ToT.
I'm using SeaBIOS 1.13.0, compiled once using the attached .config before taking these logs. All 3 runs are taken using the same SeaBIOS binary.
Then I recompiled SeaBIOS with CONFIG_RELOCATE_INIT off, replaced the payload used in run 3, and took an extra run. In this case the board reset on its own at "Scanning option roms", looping infinitely.
Hope this helps Keith
On Wed, May 13, 2020 at 7:38 AM Furquan Shaikh furquan.m.shaikh@gmail.com wrote:
Thanks for the report Keith!
On Wed, May 13, 2020 at 3:42 AM Paul Menzel pmenzel@molgen.mpg.de
wrote:
Dear Keith,
Am 13.05.20 um 05:21 schrieb Keith Hui:
I am still refining the P2B family of boards, now including the infamous P3B-F with an unusual appetite for hacks to make work.
That said, I'm now finding that, on P3B-F, SeaBIOS hangs when it
tries
to relocate itself as part of its usual chores. Having just
learned
git bisect, I decided to try it out.
It was commit 3b02006afe8a85477dafa1bd149f1f0dba02afc7 [1] that
broke
my SeaBIOS. It doesn't affect my newer toy the P8Z77-M as much as P3B-F, but I still want to blame that, and probably the very next commit as well, as they both deal with some very modern aspects
of PCI
that well predates the 440BX.
Is there anything we can do to fix 3b02006afe?
I commented in the change-set [1] to make the author and reviewers
aware
of this issue and referenced your list message, and ask to comment
here.
Could you please provide the debug log of coreboot and SeaBIOS?
As Paul mentioned, can you please provide the debug logs for coreboot and SeaBIOS both with ToT coreboot and with HEAD set before the change 3b02006afe where it does not hang? Thanks!
Meanwhile I ported the P3B-F board enable to flashrom [2], which
got a
heavy workout during this bisect, through vendor firmware and both good and bad builds of coreboot. In all cases I can flash
internal, no
longer having to haul out my P2B-LS just to use it as a flasher.
Enjoy this long overdue board enable. If it gets submitted, I'll retract the ramstage hack[3] doing the same as redundant.
Very nice! It’s always amazing, how after so many years, when the
vendor
already stopped supporting the device, the community still supports
the
device and improves the firmware showing that Free Software is the
more
sustainable way.
Kind regards,
Paul
[1] https://review.coreboot.org/c/coreboot/+/39486 [2] https://review.coreboot.org/c/flashrom/+/41354 [3] https://review.coreboot.org/c/coreboot/+/41224
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
i440x chipset is doing things in the wrong way like sandybridge. I uploaded this fix for sandy: https://review.coreboot.org/c/coreboot/+/41364 We'll need to do the equivalent for i440x.
On Wed, May 13, 2020 at 11:13 AM Aaron Durbin adurbin@google.com wrote:
OK. I'll take a look at your logs and see what's going on. The patch link I sent was based off of someone else's mainboard logs.
On Wed, May 13, 2020 at 10:59 AM Keith Hui buurin@gmail.com wrote:
Hi Aaron,
It didn't help. There still a way out of whack entry in the coreboot table and e820 entry ending at 000003ffffffffff, which I think have more to do than the 41363's scope.
Keith
On Wed, May 13, 2020 at 12:24 PM Aaron Durbin adurbin@google.com wrote:
I think the following patch will fix things up:
https://review.coreboot.org/c/coreboot/+/41363 Please let me know.
On Wed, May 13, 2020 at 8:43 AM Keith Hui buurin@gmail.com wrote:
Thanks Furquan.
Here are 3 logs. Log 1 is at the commit just before the problem. Log 2 is at the problem commit. Log 3 is at the current master, if that's what you meant by ToT.
I'm using SeaBIOS 1.13.0, compiled once using the attached .config before taking these logs. All 3 runs are taken using the same SeaBIOS binary.
Then I recompiled SeaBIOS with CONFIG_RELOCATE_INIT off, replaced the payload used in run 3, and took an extra run. In this case the board reset on its own at "Scanning option roms", looping infinitely.
Hope this helps Keith
On Wed, May 13, 2020 at 7:38 AM Furquan Shaikh furquan.m.shaikh@gmail.com wrote:
Thanks for the report Keith!
On Wed, May 13, 2020 at 3:42 AM Paul Menzel pmenzel@molgen.mpg.de
wrote:
Dear Keith,
Am 13.05.20 um 05:21 schrieb Keith Hui:
> I am still refining the P2B family of boards, now including the > infamous P3B-F with an unusual appetite for hacks to make work. > > That said, I'm now finding that, on P3B-F, SeaBIOS hangs when it
tries
> to relocate itself as part of its usual chores. Having just
learned
> git bisect, I decided to try it out. > > It was commit 3b02006afe8a85477dafa1bd149f1f0dba02afc7 [1] that
broke
> my SeaBIOS. It doesn't affect my newer toy the P8Z77-M as much as > P3B-F, but I still want to blame that, and probably the very next > commit as well, as they both deal with some very modern aspects
of PCI
> that well predates the 440BX. > > Is there anything we can do to fix 3b02006afe?
I commented in the change-set [1] to make the author and reviewers
aware
of this issue and referenced your list message, and ask to comment
here.
Could you please provide the debug log of coreboot and SeaBIOS?
As Paul mentioned, can you please provide the debug logs for coreboot and SeaBIOS both with ToT coreboot and with HEAD set before the
change
3b02006afe where it does not hang? Thanks!
> Meanwhile I ported the P3B-F board enable to flashrom [2], which
got a
> heavy workout during this bisect, through vendor firmware and
both
> good and bad builds of coreboot. In all cases I can flash
internal, no
> longer having to haul out my P2B-LS just to use it as a flasher. > > Enjoy this long overdue board enable. If it gets submitted, I'll > retract the ramstage hack[3] doing the same as redundant.
Very nice! It’s always amazing, how after so many years, when the
vendor
already stopped supporting the device, the community still
supports the
device and improves the firmware showing that Free Software is the
more
sustainable way.
Kind regards,
Paul
> [1] https://review.coreboot.org/c/coreboot/+/39486 > [2] https://review.coreboot.org/c/flashrom/+/41354 > [3] https://review.coreboot.org/c/coreboot/+/41224 _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
Similar fix for i440x: https://review.coreboot.org/c/coreboot/+/41368
On Wed, May 13, 2020 at 11:29 AM Aaron Durbin adurbin@google.com wrote:
i440x chipset is doing things in the wrong way like sandybridge. I uploaded this fix for sandy: https://review.coreboot.org/c/coreboot/+/41364 We'll need to do the equivalent for i440x.
On Wed, May 13, 2020 at 11:13 AM Aaron Durbin adurbin@google.com wrote:
OK. I'll take a look at your logs and see what's going on. The patch link I sent was based off of someone else's mainboard logs.
On Wed, May 13, 2020 at 10:59 AM Keith Hui buurin@gmail.com wrote:
Hi Aaron,
It didn't help. There still a way out of whack entry in the coreboot table and e820 entry ending at 000003ffffffffff, which I think have more to do than the 41363's scope.
Keith
On Wed, May 13, 2020 at 12:24 PM Aaron Durbin adurbin@google.com wrote:
I think the following patch will fix things up: https://review.coreboot.org/c/coreboot/+/41363 Please let me know.
On Wed, May 13, 2020 at 8:43 AM Keith Hui buurin@gmail.com wrote:
Thanks Furquan.
Here are 3 logs. Log 1 is at the commit just before the problem. Log 2 is at the problem commit. Log 3 is at the current master, if that's what you meant by ToT.
I'm using SeaBIOS 1.13.0, compiled once using the attached .config before taking these logs. All 3 runs are taken using the same SeaBIOS binary.
Then I recompiled SeaBIOS with CONFIG_RELOCATE_INIT off, replaced the payload used in run 3, and took an extra run. In this case the board reset on its own at "Scanning option roms", looping infinitely.
Hope this helps Keith
On Wed, May 13, 2020 at 7:38 AM Furquan Shaikh furquan.m.shaikh@gmail.com wrote:
Thanks for the report Keith!
On Wed, May 13, 2020 at 3:42 AM Paul Menzel pmenzel@molgen.mpg.de wrote: > > Dear Keith, > > > Am 13.05.20 um 05:21 schrieb Keith Hui: > > > I am still refining the P2B family of boards, now including the > > infamous P3B-F with an unusual appetite for hacks to make work. > > > > That said, I'm now finding that, on P3B-F, SeaBIOS hangs when it tries > > to relocate itself as part of its usual chores. Having just learned > > git bisect, I decided to try it out. > > > > It was commit 3b02006afe8a85477dafa1bd149f1f0dba02afc7 [1] that broke > > my SeaBIOS. It doesn't affect my newer toy the P8Z77-M as much as > > P3B-F, but I still want to blame that, and probably the very next > > commit as well, as they both deal with some very modern aspects of PCI > > that well predates the 440BX. > > > > Is there anything we can do to fix 3b02006afe? > > I commented in the change-set [1] to make the author and reviewers aware > of this issue and referenced your list message, and ask to comment here. > > Could you please provide the debug log of coreboot and SeaBIOS?
As Paul mentioned, can you please provide the debug logs for coreboot and SeaBIOS both with ToT coreboot and with HEAD set before the change 3b02006afe where it does not hang? Thanks!
> > > > Meanwhile I ported the P3B-F board enable to flashrom [2], which got a > > heavy workout during this bisect, through vendor firmware and both > > good and bad builds of coreboot. In all cases I can flash internal, no > > longer having to haul out my P2B-LS just to use it as a flasher. > > > > Enjoy this long overdue board enable. If it gets submitted, I'll > > retract the ramstage hack[3] doing the same as redundant. > > Very nice! It’s always amazing, how after so many years, when the vendor > already stopped supporting the device, the community still supports the > device and improves the firmware showing that Free Software is the more > sustainable way. > > > Kind regards, > > Paul > > > > [1] https://review.coreboot.org/c/coreboot/+/39486 > > [2] https://review.coreboot.org/c/flashrom/+/41354 > > [3] https://review.coreboot.org/c/coreboot/+/41224 > _______________________________________________ > coreboot mailing list -- coreboot@coreboot.org > To unsubscribe send an email to coreboot-leave@coreboot.org
coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
Hi guys,
I tested these fixes on my board, and I have to say there's still something wrong. They did address the hang or reset in SeaBIOS I first described, but now either my ATA hard drive failed to boot (it tried to hand off to GRUB on my drive, but didn't get there), or it can't find the option ROM of my video card, meaning no display.
Now I want to try the other way, testing a build with all changes related to the problem backed out instead. So besides the one I first identified, what other related patches should I try backing out?
Thanks Keith
On Wed, May 13, 2020 at 11:54 PM Furquan Shaikh furquan.m.shaikh@gmail.com wrote:
Similar fix for i440x: https://review.coreboot.org/c/coreboot/+/41368
On Wed, May 13, 2020 at 11:29 AM Aaron Durbin adurbin@google.com wrote:
i440x chipset is doing things in the wrong way like sandybridge. I uploaded this fix for sandy: https://review.coreboot.org/c/coreboot/+/41364 We'll need to do the equivalent for i440x.
On Wed, May 13, 2020 at 11:13 AM Aaron Durbin adurbin@google.com wrote:
OK. I'll take a look at your logs and see what's going on. The patch link I sent was based off of someone else's mainboard logs.
On Wed, May 13, 2020 at 10:59 AM Keith Hui buurin@gmail.com wrote:
Hi Aaron,
It didn't help. There still a way out of whack entry in the coreboot table and e820 entry ending at 000003ffffffffff, which I think have more to do than the 41363's scope.
Keith
On Wed, May 13, 2020 at 12:24 PM Aaron Durbin adurbin@google.com wrote:
I think the following patch will fix things up: https://review.coreboot.org/c/coreboot/+/41363 Please let me know.
On Wed, May 13, 2020 at 8:43 AM Keith Hui buurin@gmail.com wrote:
Thanks Furquan.
Here are 3 logs. Log 1 is at the commit just before the problem. Log 2 is at the problem commit. Log 3 is at the current master, if that's what you meant by ToT.
I'm using SeaBIOS 1.13.0, compiled once using the attached .config before taking these logs. All 3 runs are taken using the same SeaBIOS binary.
Then I recompiled SeaBIOS with CONFIG_RELOCATE_INIT off, replaced the payload used in run 3, and took an extra run. In this case the board reset on its own at "Scanning option roms", looping infinitely.
Hope this helps Keith
On Wed, May 13, 2020 at 7:38 AM Furquan Shaikh furquan.m.shaikh@gmail.com wrote: > > Thanks for the report Keith! > > On Wed, May 13, 2020 at 3:42 AM Paul Menzel pmenzel@molgen.mpg.de wrote: > > > > Dear Keith, > > > > > > Am 13.05.20 um 05:21 schrieb Keith Hui: > > > > > I am still refining the P2B family of boards, now including the > > > infamous P3B-F with an unusual appetite for hacks to make work. > > > > > > That said, I'm now finding that, on P3B-F, SeaBIOS hangs when it tries > > > to relocate itself as part of its usual chores. Having just learned > > > git bisect, I decided to try it out. > > > > > > It was commit 3b02006afe8a85477dafa1bd149f1f0dba02afc7 [1] that broke > > > my SeaBIOS. It doesn't affect my newer toy the P8Z77-M as much as > > > P3B-F, but I still want to blame that, and probably the very next > > > commit as well, as they both deal with some very modern aspects of PCI > > > that well predates the 440BX. > > > > > > Is there anything we can do to fix 3b02006afe? > > > > I commented in the change-set [1] to make the author and reviewers aware > > of this issue and referenced your list message, and ask to comment here. > > > > Could you please provide the debug log of coreboot and SeaBIOS? > > As Paul mentioned, can you please provide the debug logs for coreboot > and SeaBIOS both with ToT coreboot and with HEAD set before the change > 3b02006afe where it does not hang? Thanks! > > > > > > > > Meanwhile I ported the P3B-F board enable to flashrom [2], which got a > > > heavy workout during this bisect, through vendor firmware and both > > > good and bad builds of coreboot. In all cases I can flash internal, no > > > longer having to haul out my P2B-LS just to use it as a flasher. > > > > > > Enjoy this long overdue board enable. If it gets submitted, I'll > > > retract the ramstage hack[3] doing the same as redundant. > > > > Very nice! It’s always amazing, how after so many years, when the vendor > > already stopped supporting the device, the community still supports the > > device and improves the firmware showing that Free Software is the more > > sustainable way. > > > > > > Kind regards, > > > > Paul > > > > > > > [1] https://review.coreboot.org/c/coreboot/+/39486 > > > [2] https://review.coreboot.org/c/flashrom/+/41354 > > > [3] https://review.coreboot.org/c/coreboot/+/41224 > > _______________________________________________ > > coreboot mailing list -- coreboot@coreboot.org > > To unsubscribe send an email to coreboot-leave@coreboot.org _______________________________________________ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-leave@coreboot.org
On Wed, May 13, 2020 at 10:51 PM Keith Hui buurin@gmail.com wrote:
Hi guys,
I tested these fixes on my board, and I have to say there's still something wrong. They did address the hang or reset in SeaBIOS I first described, but now either my ATA hard drive failed to boot (it tried to hand off to GRUB on my drive, but didn't get there), or it can't find the option ROM of my video card, meaning no display.
Now I want to try the other way, testing a build with all changes related to the problem backed out instead. So besides the one I first identified, what other related patches should I try backing out?
Just go to the parent of the identified patch. As for the other symptoms you are seeing, I'd love to see logs with the patches we identified so we can root cause.
Thanks.
-Aaron
On Wed, May 13, 2020 at 11:54 PM Furquan Shaikh furquan.m.shaikh@gmail.com wrote:
Similar fix for i440x: https://review.coreboot.org/c/coreboot/+/41368
On Wed, May 13, 2020 at 11:29 AM Aaron Durbin adurbin@google.com
wrote:
i440x chipset is doing things in the wrong way like sandybridge. I
uploaded this fix for sandy: https://review.coreboot.org/c/coreboot/+/41364 We'll need to do the equivalent for i440x.
On Wed, May 13, 2020 at 11:13 AM Aaron Durbin adurbin@google.com
wrote:
OK. I'll take a look at your logs and see what's going on. The patch
link I sent was based off of someone else's mainboard logs.
On Wed, May 13, 2020 at 10:59 AM Keith Hui buurin@gmail.com wrote:
Hi Aaron,
It didn't help. There still a way out of whack entry in the coreboot table and e820 entry ending at 000003ffffffffff, which I think have more to do than the 41363's scope.
Keith
On Wed, May 13, 2020 at 12:24 PM Aaron Durbin adurbin@google.com
wrote:
I think the following patch will fix things up:
https://review.coreboot.org/c/coreboot/+/41363 Please let me know.
On Wed, May 13, 2020 at 8:43 AM Keith Hui buurin@gmail.com
wrote:
> > Thanks Furquan. > > Here are 3 logs. Log 1 is at the commit just before the problem.
Log 2
> is at the problem commit. Log 3 is at the current master, if
that's
> what you meant by ToT. > > I'm using SeaBIOS 1.13.0, compiled once using the attached .config > before taking these logs. All 3 runs are taken using the same
SeaBIOS
> binary. > > Then I recompiled SeaBIOS with CONFIG_RELOCATE_INIT off, replaced
the
> payload used in run 3, and took an extra run. In this case the
board
> reset on its own at "Scanning option roms", looping infinitely. > > Hope this helps > Keith > > On Wed, May 13, 2020 at 7:38 AM Furquan Shaikh > furquan.m.shaikh@gmail.com wrote: > > > > Thanks for the report Keith! > > > > On Wed, May 13, 2020 at 3:42 AM Paul Menzel <
pmenzel@molgen.mpg.de> wrote:
> > > > > > Dear Keith, > > > > > > > > > Am 13.05.20 um 05:21 schrieb Keith Hui: > > > > > > > I am still refining the P2B family of boards, now including
the
> > > > infamous P3B-F with an unusual appetite for hacks to make
work.
> > > > > > > > That said, I'm now finding that, on P3B-F, SeaBIOS hangs
when it tries
> > > > to relocate itself as part of its usual chores. Having just
learned
> > > > git bisect, I decided to try it out. > > > > > > > > It was commit 3b02006afe8a85477dafa1bd149f1f0dba02afc7 [1]
that broke
> > > > my SeaBIOS. It doesn't affect my newer toy the P8Z77-M as
much as
> > > > P3B-F, but I still want to blame that, and probably the
very next
> > > > commit as well, as they both deal with some very modern
aspects of PCI
> > > > that well predates the 440BX. > > > > > > > > Is there anything we can do to fix 3b02006afe? > > > > > > I commented in the change-set [1] to make the author and
reviewers aware
> > > of this issue and referenced your list message, and ask to
comment here.
> > > > > > Could you please provide the debug log of coreboot and
SeaBIOS?
> > > > As Paul mentioned, can you please provide the debug logs for
coreboot
> > and SeaBIOS both with ToT coreboot and with HEAD set before the
change
> > 3b02006afe where it does not hang? Thanks! > > > > > > > > > > > > Meanwhile I ported the P3B-F board enable to flashrom [2],
which got a
> > > > heavy workout during this bisect, through vendor firmware
and both
> > > > good and bad builds of coreboot. In all cases I can flash
internal, no
> > > > longer having to haul out my P2B-LS just to use it as a
flasher.
> > > > > > > > Enjoy this long overdue board enable. If it gets submitted,
I'll
> > > > retract the ramstage hack[3] doing the same as redundant. > > > > > > Very nice! It’s always amazing, how after so many years, when
the vendor
> > > already stopped supporting the device, the community still
supports the
> > > device and improves the firmware showing that Free Software
is the more
> > > sustainable way. > > > > > > > > > Kind regards, > > > > > > Paul > > > > > > > > > > [1] https://review.coreboot.org/c/coreboot/+/39486 > > > > [2] https://review.coreboot.org/c/flashrom/+/41354 > > > > [3] https://review.coreboot.org/c/coreboot/+/41224 > > > _______________________________________________ > > > coreboot mailing list -- coreboot@coreboot.org > > > To unsubscribe send an email to coreboot-leave@coreboot.org > _______________________________________________ > coreboot mailing list -- coreboot@coreboot.org > To unsubscribe send an email to coreboot-leave@coreboot.org