Bug 255072 - boot (legacy): no progress beyond 'BIOS DRIVE D: is disk1'
Summary: boot (legacy): no progress beyond 'BIOS DRIVE D: is disk1'
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: standards (show other bugs)
Version: Unspecified
Hardware: amd64 Any
: --- Affects Some People
Assignee: freebsd-standards (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-15 02:54 UTC by Graham Perrin
Modified: 2021-04-20 14:40 UTC (History)
3 users (show)

See Also:


Attachments
Photograph of the bug. (117.28 KB, image/jpeg)
2021-04-15 02:54 UTC, Graham Perrin
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Graham Perrin 2021-04-15 02:54:16 UTC
Created attachment 224121 [details]
Photograph of the bug.

FreeBSD-13.0-RELEASE-amd64-memstick.img

HP ProBook 440 G7
<https://support.hp.com/gb-en/document/c06474914>

Comparative test results: 
<https://gist.github.com/grahamperrin/5eca8231fa7e6a94a1f55991bcd7f3c4#freebsd-130-release-amd64-memstickimg>

> below BIOS DRIVE D: is disk1, a flickering cursor.
Comment 1 Graham Perrin 2021-04-15 03:12:32 UTC
> HP ProBook 440 G7

Adjacent bug 255073 for the same hardware not booting in UEFI mode.
Comment 2 spell 2021-04-19 20:25:06 UTC
I have the analogous case.

FreeBSD-13.0-RELEASE-i386-mini-memstick.img
HP EliteBook 2570p
BIOS Mode Legacy
For a moment these strings:

Consoles: internal video/keyboard
BIOS Drive C: disk0
BIOS Drive D: disk1

are displayed and then the notebook reboots.

FreeBSD-12.2-RELEASE-i386-mini-memstick.img - the same behavior (except for the picture displayed has additional string at the start about BTX loader).

FreeBSD-11.2-RELEASE-i386-mini-memstick.img loads successfully.
Comment 3 Graham Perrin 2021-04-20 12:07:33 UTC
Thank you, 

(In reply to spell from comment #2)

> … 
> FreeBSD-13.0-RELEASE-i386-mini-memstick.img
> HP EliteBook 2570p
> BIOS Mode Legacy
> For a moment these strings:

> … are displayed and then the notebook reboots.

In the moment(s) before the reboot, is a flickering cursor visible? 


----

With the HP ProBook 440 G7, which does not automatically reboot, the flickering is _very_ rapid and barely perceptible. 


<https://h20195.www2.hp.com/v2/getpdf.aspx/c06424517.pdf> QuickSpecs
<https://support.hp.com/gb-en/document/c06474914>         specifications
<https://support.hp.com/gb-en/product/hp-probook-440-g7-notebook-pc/29090063>

----

HP EliteBook 2570p

<https://support.hp.com/gb-en/document/c03412731> specifications
<https://support.hp.com/gb-en/product/hp-elitebook-2570p-notebook-pc/5259393/>

> Intel HD Graphics 4000
Comment 4 spell 2021-04-20 12:37:44 UTC
(In reply to Graham Perrin from comment #3)

> In the moment(s) before the reboot, is a flickering cursor visible?

No at all. That is very short moment, I hardly managed to read those three strings. My cam also can't catch it.

Thank to you too for the PR.
Comment 5 Toomas Soome freebsd_committer 2021-04-20 12:40:26 UTC
(In reply to spell from comment #4)


Latest BIOS?
Comment 6 spell 2021-04-20 12:54:44 UTC
(In reply to Toomas Soome from comment #5)

> Latest BIOS?

Believe yes, I've updated it recently in a service center.
Do you need more info about the version?
Comment 7 Toomas Soome freebsd_committer 2021-04-20 13:05:20 UTC
(In reply to spell from comment #6)

We got disk names, meaning the biosdisk.c probe functions did ok (more or less). After biosdisk, the zfs probe is run, and most likely it is causing the system to hung, because there are no other messages.

Bios version does not help too much (I do not have the hw anyhow). Normally at such case we start with ellimination and inserting diag printouts.
Comment 8 Toomas Soome freebsd_committer 2021-04-20 14:01:38 UTC
(In reply to Toomas Soome from comment #7)

What we should do next is to try to investigate why exactly are we get stuck and this would require building debug loader. I can do this for you.

Before that, I'd like you to test if you can get boot: prompt -- when system is starting, on very first spinner, press space. You should get boot: prompt, there you can enter status or ?/ or ?/boot to list directory contents. Also you can enter file name like: /boot/loader to start next boot phase.
Comment 9 spell 2021-04-20 14:40:54 UTC
(In reply to Toomas Soome from comment #8)

Don't see any spinner but if tapping Space at a right moment I do enter boot prompt and can run /boot/loader or whatever.
Please build loader with eliminations/debug printouts.