[Bug 221350] Unable to boot/install on HPE Proliant MicroServer

bugzilla...@freebsd.org

unread,

Aug 8, 2017, 6:23:42 PM8/8/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

Bug ID: 221350
Summary: Unable to boot/install on HPE Proliant MicroServer
Gen10 (AMD Opteron X3000): Hangs/Panics
Product: Base System
Version: 11.1-STABLE
Hardware: i386
OS: Any
Status: New
Severity: Affects Many People
Priority: ---
Component: kern
Assignee: freebs...@FreeBSD.org
Reporter: r...@rafal.net

Created attachment 185171
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185171&action=edit
Verbose boot console output at hang point

I am unable to install/run FreeBSD 11.1 on a brand-new HPE MicroServer Gen10
containing an AMD Opteron X3421 with 16GB RAM. The installer hangs just after
it prints:

pci0: <ACPI PCI bus> on pcib0

Please see attached console screenshot showing verbose output which suggests
that the boot process hangs just as it has collected information about the RAM
on pcib0. This is while booting from a USB (several tried and tested and
integrity validated) or when moving an existing pre-installed elsewhere system.
Same affects FreeNAS 11.0 on this system.

Switching off ACPI during boot causes a kernel panic with a message:

panic: running without device atpic requires a local APIC

Trying to set hint.apic.0.disabled=1 (tried with apic.0 till apic.3 on this
4-core machine) causes a different panic:

Fatal trap 12: page fault while in kernel mode.

I have started a forum discussion about this issue:
https://forums.freebsd.org/threads/61936/

It has also been referred to on FreeNAS forum, as others have been affected:
https://forums.freenas.org/index.php?threads/installation-stop-after-a-few-seconds-on-a-microserver-gen10.56809/#post-399023

I only have a basic understanding of FreeBSD but I am a long-time IT
professional and I would be happy to submit further traces and try suggestions
to help debug it. As-is, it seems like FreeBSD is incompatible with HPE
Proliant MicroServer Gen10.

Thank you for your kind help.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebs...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs...@freebsd.org"

bugzilla...@freebsd.org

unread,

Aug 8, 2017, 6:24:23 PM8/8/17

to

bugzilla...@freebsd.org

unread,

Aug 8, 2017, 6:25:59 PM8/8/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #1 from Rafal Lukawiecki <r...@rafal.net> ---
Created attachment 185172
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185172&action=edit
Non-verbose boot output showing more context before the hang

bugzilla...@freebsd.org

unread,

Aug 8, 2017, 6:26:28 PM8/8/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #2 from Rafal Lukawiecki <r...@rafal.net> ---
Created attachment 185173
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185173&action=edit
Panic when booting with ACPI off

bugzilla...@freebsd.org

unread,

Aug 8, 2017, 6:27:54 PM8/8/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

Rafal Lukawiecki <r...@rafal.net> changed:

What |Removed |Added
----------------------------------------------------------------------------

bugzilla...@freebsd.org

unread,

Aug 8, 2017, 6:28:36 PM8/8/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #3 from Rafal Lukawiecki <r...@rafal.net> ---
Created attachment 185174
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185174&action=edit
Panic when booting with ACPI off in boot options menu

bugzilla...@freebsd.org

unread,

Aug 9, 2017, 1:35:38 PM8/9/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #4 from Rafal Lukawiecki <r...@rafal.net> ---
Following suggestion by Miroslav Lachman I have tested a few other releases of
FreeBSD to see if this issue still persists and if it was a regression.
Unfortunately, in all tests, 9.3-12.0-CURRENT, I get exactly the same error. To
be precise, these are the versions that I have tested:

FreeBSD-9.3-RELEASE-amd64-memstick.img
FreeBSD-11.1-RELEASE-amd64-memstick.img
FreeBSD-11.1-STABLE-amd64-20170807-r322164-memstick.img
FreeBSD-12.0-CURRENT-amd64-20170807-r322167-memstick.img

bugzilla...@freebsd.org

unread,

Aug 11, 2017, 4:20:25 AM8/11/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

Kubilay Kocak <ko...@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Keywords| |crash, needs-qa
Flags| |mfc-stable9?,
| |mfc-stable10?,
| |mfc-stable11?
Status|New |Open

--- Comment #5 from Kubilay Kocak <ko...@FreeBSD.org> ---
Thank you for testing all major version branches Rafal

bugzilla...@freebsd.org

unread,

Aug 31, 2017, 2:44:59 PM8/31/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

Thomas Neuber <th.n...@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |th.n...@gmail.com

--- Comment #6 from Thomas Neuber <th.n...@gmail.com> ---
At first, I can confirm the behavior as described before.

In addition to that: I had a working installation for a HPE Proliant
Microserver Gen8 (Intel Xeon E3 v1220L). The old system did not support UEFI.
The old installation (SD card copied 1:1 to a USB stick + the 4 hard drives)
runs properly on the Gen10 after switching the settings to UEFI with CSM
Enabled + Boot Mode Legacy Only - except the console. I expected the console
menu after certain amount of time.

The console output stops at:
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pcib0: _OSC returned error 0x10

pci0: <ACPI PCI bus> on pcib0

As I said, everything else works fine.

bugzilla...@freebsd.org

unread,

Sep 11, 2017, 2:33:24 PM9/11/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

Jussi Hagman <juha...@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |juha...@gmail.com

--- Comment #7 from Jussi Hagman <juha...@gmail.com> ---
I can confirm this too. Trying to install FreeBSD (and FreeNAS) hang as
described by Rafal.

I would love to provide more information to help debugging and fixing this
problem.

I can run Linux on the box, but would really prefer FreeNAS.

bugzilla...@freebsd.org

unread,

Sep 12, 2017, 1:15:35 PM9/12/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #8 from Thomas Neuber <th.n...@gmail.com> ---
I created an UEFI aware installation on a different PC and repeated the test as
described in comment #6. The overall behavior booting with UEFI is exactly the
same as with legacy boot. All configured (network) services (samba, web, ssh,
several jails, etc.) are up and running but the console hangs. From a remote
location, everything is functional with the expected level of performance. But
locally, it is still unusable.

Let me know, if I should provide any additional information, run any test
cases, etc.

bugzilla...@freebsd.org

unread,

Sep 12, 2017, 2:47:04 PM9/12/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #9 from Thomas Neuber <th.n...@gmail.com> ---
Created attachment 186306
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=186306&action=edit
Kernel Display Messages of the last boot

Compared to this file, the visible console messages stop after line 58. The
next output would be:
vgapci0: <VGA-compatible display> port 0xf000-0xf0ff mem
0xe0000000-0xefffffff,0xf0000000-0xf07fffff at device 1.0 on pci0
vgapci0: Boot video device

bugzilla...@freebsd.org

unread,

Sep 25, 2017, 5:51:45 AM9/25/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #10 from Jan Bramkamp <crest_ma...@rlwinm.de> ---
I just ran into the same bug.

bugzilla...@freebsd.org

unread,

Sep 25, 2017, 12:06:59 PM9/25/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

Thomas Neuber <th.n...@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
Attachment #186306|0 |1
is obsolete| |

--- Comment #11 from Thomas Neuber <th.n...@gmail.com> ---
Created attachment 186707
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=186707&action=edit
verbose kernel display messages

bugzilla...@freebsd.org

unread,

Sep 25, 2017, 12:07:29 PM9/25/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #12 from Thomas Neuber <th.n...@gmail.com> ---
Created attachment 186708
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=186708&action=edit
output of pciconf -lvbce

bugzilla...@freebsd.org

unread,

Sep 25, 2017, 12:07:54 PM9/25/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #13 from Thomas Neuber <th.n...@gmail.com> ---
Created attachment 186709
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=186709&action=edit
output of devinfo -vr

bugzilla...@freebsd.org

unread,

Oct 5, 2017, 6:24:28 AM10/5/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #14 from Mikael D <t.mik...@gmail.com> ---
(In reply to Thomas Neuber from comment #8)

Do you mean that it boots if VGA is not used?(In reply to Thomas Neuber from
comment #8)

Do you mean that it could run headless (Without VGA) ?

bugzilla...@freebsd.org

unread,

Oct 5, 2017, 1:19:43 PM10/5/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #15 from Thomas Neuber <th.n...@gmail.com> ---
(In reply to Mikael D from comment #14)

My system is up and running stable for the last 9 days. Last restart was after
an update from Freenas 11.0 U3 to U4. The headless use is definitely possible.
The challenge was the installation without a working local console (VGA). I am
not aware whether an installation from a remote location is possible and how
does it works. It utilized another PC to set up the system.

The console does not work with any of the two Displayports or the VGA
connector. Is the Carrizo chipset supported by the kernel?

[root@jupiter ~]# uname -a
FreeBSD jupiter.fritz.box 11.0-STABLE FreeBSD 11.0-STABLE #0
r321665+25fe8ba8d06(freenas/11.0-stable): Mon Sep 25 06:24:11 UTC 2017

root@gauntlet:/freenas-11-releng/freenas/_BE/objs/freenas-11-releng/freenas/_BE/os/sys/FreeNAS.amd64
amd64
[root@jupiter ~]# uptime
7:00PM up 9 days, 1:05, 0 users, load averages: 0.14, 0.14, 0.16
[root@jupiter ~]#

bugzilla...@freebsd.org

unread,

Oct 5, 2017, 1:23:44 PM10/5/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #16 from Mikael D <t.mik...@gmail.com> ---
(In reply to Thomas Neuber from comment #15)

This is the first time ever that i encounter any *nix system that does not boot
due to faulty VGA, kind of curious what the issue is.

Anyway, I hope the FreeBSD people here can fix it and I'll try running it
headless once i receive my MicroServer Gen10 next Tuesday. (I've gotten myself
a Gen8 too so i can have one spare and use it to install FreeNAS to the USB).

I'll do some tests and report my findings (though i think all is covered here
already).

Thanks for the quick reply!

bugzilla...@freebsd.org

unread,

Oct 9, 2017, 3:58:11 AM10/9/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

Jure K. <jure.ko...@komna.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |jure.ko...@komna.com

--- Comment #17 from Jure K. <jure.ko...@komna.com> ---
Diffenrent system, but same symptoms: OpenBSD also gets stuck. The trick is to
disable ACPI at boot. Hope this info leads you on the right track.

bugzilla...@freebsd.org

unread,

Oct 9, 2017, 4:00:32 AM10/9/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #18 from Mikael D <t.mik...@gmail.com> ---
(In reply to Jure K. from comment #17)

It was mentioned above that this causes a kernel panic:

"Switching off ACPI during boot causes a kernel panic with a message"

bugzilla...@freebsd.org

unread,

Oct 9, 2017, 7:08:38 AM10/9/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

Jörn Lentes <joern....@web.de> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |joern....@web.de

--- Comment #20 from Jörn Lentes <joern....@web.de> ---
I have the same problem with my HP Gen10 MicroServer with AMD Opteron X3216.

non-BSD based systems boot up fine from USB.

bugzilla...@freebsd.org

unread,

Oct 9, 2017, 7:33:08 AM10/9/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #21 from Jan Bramkamp <crest_ma...@rlwinm.de> ---
The system does boot, but the only console hangs as soon as the kernel takes
over from the UEFI firmware. I installed mine with mfsBSD and once FreeBSD is
installed (including network configuration and SSH server) it works just fine,
but it is annoying to have a headless x86 box around. And a USB<->RS232 adapter
doesn't work as console because the USB stack comes up too late in the boot
process.

bugzilla...@freebsd.org

unread,

Oct 9, 2017, 8:32:49 AM10/9/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #22 from Mikael D <t.mik...@gmail.com> ---
(In reply to Jan Bramkamp from comment #21)

Hopefully it can be fixed before we run into any boot/hardware issues that
require the console before SSH has loaded.

bugzilla...@freebsd.org

unread,

Oct 16, 2017, 5:09:44 AM10/16/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

Igor Porozov <sysa...@eifmanacademy.ru> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |sysa...@eifmanacademy.ru

--- Comment #23 from Igor Porozov <sysa...@eifmanacademy.ru> ---
We succeed in running FreeBSD installed on another computer.
It turns out that the video driver is hanging up, but the system itself is
loaded further.
For the full load, you need to add hard drives to fstab and network adapters in
rc.conf.
Hard drives are called ada, and network interfaces are called bge.
After that, you can connect via SSH.

bugzilla...@freebsd.org

unread,

Oct 16, 2017, 5:32:18 AM10/16/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #24 from Jörn Lentes <joern....@web.de> ---
Is there a possibility to have an unattended install to workaround that
problem?
What information do I need to add to the usb boot image?

bugzilla...@freebsd.org

unread,

Oct 16, 2017, 6:07:51 AM10/16/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #25 from Igor Porozov <sysa...@eifmanacademy.ru> ---
You can not make the installation, because freebsd does not work with the video
installed in this AMD's APU.
It is necessary to install and first configure freebsd on another computer,
then rearrange the hard disk in the microserver and add information about disks
and network controllers using livecd.

bugzilla...@freebsd.org

unread,

Oct 16, 2017, 11:50:17 AM10/16/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #26 from Jan Bramkamp <crest_ma...@rlwinm.de> ---
FreeBSD can be installed on headless systems like the HP Gen 10 Microservers.
The most common tool for the job is mfsBSD. You can put mfsBSD on a USB stick
and boot from the USB stick. MfsBSD includes some scripts to start dhclient on
all ethernet like interfaces and starts the SSH server by default. You can
either use the minimal install er script included in mfsBSD or run bsdinstall
over SSH. Due to a bug in bsdinstall you have to create /usr/freebsd-dist and
load the MANIFEST manually if you want to go that way.

bugzilla...@freebsd.org

unread,

Oct 17, 2017, 1:44:01 PM10/17/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #27 from Jörn Lentes <joern....@web.de> ---
(In reply to Igor Porozov from comment #25)
Thanks a lot! This workaround did it. On another computer I booted from USB and
installed onto another USB stick.
Network was set to DHCP.

I was able to plugin this stick into the MircoServer and boot with it. Figured
out the IP it got assigned from my router and was able to access the web
console.

bugzilla...@freebsd.org

unread,

Oct 24, 2017, 5:27:20 AM10/24/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

r...@gid.co.uk changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |r...@gid.co.uk

--- Comment #28 from r...@gid.co.uk ---
Adding: hw.pci.realloc_bars="1"
to /boot/loader.conf on an installed system will make the VGA console
functional.

You can make the same modification to /boot/loader.conf on an installer
memstick and that will then work to do a normal install. Tested with 11.1-R

bugzilla...@freebsd.org

unread,

Oct 24, 2017, 6:16:21 AM10/24/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

Jan Bramkamp <cr...@bultmann.eu> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |cr...@bultmann.eu

--- Comment #29 from Jan Bramkamp <cr...@bultmann.eu> ---
The same should be possible from the bootloader prompt avoiding the need to
change the install medium at all. Just add it to the /boot/loader.conf when the
installer prompts if you want to enter the fresh installation.

bugzilla...@freebsd.org

unread,

Oct 24, 2017, 7:47:06 AM10/24/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #30 from Bob Bishop <r...@gid.co.uk> ---
(In reply to Jan Bramkamp from comment #29)

Yes. If you break out to the loader prompt and type:

set hw.pci.realloc_bars 1
boot

the installation proceeds as expected, and you can fix loader.conf at the end
of installation.

bugzilla...@freebsd.org

unread,

Oct 24, 2017, 10:57:32 AM10/24/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #31 from Bob Bishop <r...@gid.co.uk> ---
Created attachment 187442
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=187442&action=edit
This patch adds a quirk to address the issue

I've attached a patch that fixes the problem. It's tested against 11.1-R but
should apply to HEAD.

bugzilla...@freebsd.org

unread,

Oct 25, 2017, 1:41:28 AM10/25/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

Mark Linimon <lin...@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Keywords|needs-qa |patch

bugzilla...@freebsd.org

unread,

Oct 25, 2017, 6:31:33 AM10/25/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #32 from Jan Bramkamp <cr...@bultmann.eu> ---
I tested the patch against FreeBSD 11.1/amd64 and it solved the problem.

bugzilla...@freebsd.org

unread,

Oct 25, 2017, 6:33:02 AM10/25/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #33 from Jan Bramkamp <cr...@bultmann.eu> ---
(In reply to Bob Bishop from comment #30)
The correct syntax is:

set <name>=<value>

instead of:
set <name> <value>

bugzilla...@freebsd.org

unread,

Oct 25, 2017, 6:37:50 AM10/25/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #34 from Bob Bishop <r...@gid.co.uk> ---
(In reply to Jan Bramkamp from comment #33)
Of course.

bugzilla...@freebsd.org

unread,

Oct 26, 2017, 6:33:16 AM10/26/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #35 from Rafal Lukawiecki <r...@rafal.net> ---
Thank you, everyone, and Bob Bishop for the patch. I am impressed the community
were able to fix this, but I am sorry I will not be able to test it, as I have
since returned the Gen 10 MicroServer back to HPE. It has been replaced with a
very-well functioning SuperMicro machine, which runs FreeBSD like a charm.

bugzilla...@freebsd.org

unread,

Nov 5, 2017, 8:39:16 AM11/5/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

Andrew Irwin <apirwin...@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |apirwin...@gmail.com

--- Comment #36 from Andrew Irwin <apirwin...@gmail.com> ---

(In reply to Bob Bishop from comment #30)

I have successfully tested the work around with FreeNAS-11.0-U4. The permanent
setting can be set through the web interface under System->Tunables
Variable: hw.pci.realloc_bars
Value: 1
Type: Loader

bugzilla...@freebsd.org

unread,

Nov 29, 2017, 10:46:29 AM11/29/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #38 from Thomas Neuber <th.n...@gmail.com> ---
Created attachment 188398
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=188398&action=edit
verbose kernel messages with applied patch

bugzilla...@freebsd.org

unread,

Nov 29, 2017, 10:47:31 AM11/29/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #39 from Thomas Neuber <th.n...@gmail.com> ---
Created attachment 188399
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=188399&action=edit
output of devinfo -vr with applied patch

bugzilla...@freebsd.org

unread,

Nov 29, 2017, 10:55:06 AM11/29/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #40 from Thomas Neuber <th.n...@gmail.com> ---
Created attachment 188401
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=188401&action=edit
Difference Report of devinfo -vr output

The configuration of storage and usb devices has been changed slightly, but the
onboard configuration is excatly the same as before.

bugzilla...@freebsd.org

unread,

Nov 29, 2017, 11:02:23 AM11/29/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #41 from Thomas Neuber <th.n...@gmail.com> ---
Created attachment 188403
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=188403&action=edit
Difference Report of dmesg

Same as before - storage and usb configuration changed, everything else
unchanged.

bugzilla...@freebsd.org

unread,

Nov 30, 2017, 1:09:41 PM11/30/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

mi...@mishulica.com changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |mi...@mishulica.com

--- Comment #42 from mi...@mishulica.com ---
What is the path the patch has to take to get to master? This way we can gauge
if we should wait or try to figure out how to apply & build the patch to
current code.

bugzilla...@freebsd.org

unread,

Nov 30, 2017, 2:35:53 PM11/30/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #43 from Bob Bishop <r...@gid.co.uk> ---
(In reply to mishu from comment #42)
Don't know about FreeNAS, but I think the patch applies to FreeBSD HEAD.

bugzilla...@freebsd.org

unread,

Nov 30, 2017, 3:32:15 PM11/30/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #44 from Thomas Neuber <th.n...@gmail.com> ---
I realized my yesterdays tests as follows: I built a complete FreeNAS system
from the freenas-master sources. That uses FreeBSD 11.1-STABLE as you can see
in dmesg output. I pulled the all the sources and applied the attached patch. I
tried the resulting ISO installation image to setup the system. Console output
is now ok. Everything works fine.

bugzilla...@freebsd.org

unread,

Dec 7, 2017, 5:30:21 AM12/7/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

--- Comment #45 from Bob Bishop <r...@gid.co.uk> ---
(In reply to Alexander Motin from comment #37)
The patch is in the form of a quirk, so its effect on other hardware should be
precisely zero. Any reason why it shouldn't be committed?

bugzilla...@freebsd.org

unread,

Dec 8, 2017, 1:55:59 PM12/8/17

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

robert...@comcast.net changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |robert...@comcast.net

--- Comment #46 from robert...@comcast.net ---
Comment on attachment 185172
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185172
Non-verbose boot output showing more context before the hang

Have reproduced this same error on HPE Gen10 Microserver when attempting to
boot from USB thumb drive to install FreeNAS11U4.

bugzilla...@freebsd.org

unread,

Mar 15, 2018, 12:20:21 AM3/15/18

to

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350

cu...@curttech.com changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |cu...@curttech.com

--- Comment #47 from cu...@curttech.com ---
I am experiencing the same behavior (locks after pci0: <ACPI PCI bus> on pcib0)
using a USB FreeBSD 11.1 boot media. My system is a HP MicroServer Gen10
(X3421). I used the workaround (hw.pci.realloc_bars=1) to get it booted,
installed and running (put hw.pci.realloc_bars=1 in /boot/loader.conf). Looking
forward to a patch.