On 24/09/17 22:32, Sebastian Roth wrote:
757ab9 - Wed, 4 May 2016 - Hang
c917687 - Mon, 20 Jun 2016 - Hang
694c18 - Mon, 20 Jun 2016 - Hang
e09331a - Wed, 7 Dec 2016 - Hang
5cf5ffe - Wed, 7 Dec 2016 - No hang
d37e025 - Wed, 25 Jan 2017 - No hang
302f1ee - Thu, 26 Jan 2017 - wont boot at all on the surface
d46c53c - Wed, 13 Sep 2017 - Hang
Thank you for all this testing! The failure introduced in
http://git.ipxe.org/ipxe.git/commitdiff/302f1ee
was probably fixed six commits later in
http://git.ipxe.org/ipxe.git/commitdiff/a8f80a7
which means that there may be another range of working commits (and
hence a more recent culprit for inducing failure).
Could you possibly test commit a8f80a7? If that works, then it would be
worth using http://ipxe.org/howto/bisect to find the most recent cause
of failure.
Also, which iPXE binary are you using? We've encountered some failures
on the Surface due to the extremely buggy UNDI driver that Microsoft
provides:
http://git.ipxe.org/ipxe.git/commitdiff/97f0f56
Michael
_______________________________________________
ipxe-devel mailing list
[email protected]
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
