https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
Greg Lehey changed:
What|Removed |Added
Assignee|b...@freebsd.org|g...@freebsd.org
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
John Baldwin changed:
What|Removed |Added
CC||i...@freebsd.org
--- Comment #54
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
Sean Bruno changed:
What|Removed |Added
CC||j...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
Kubilay Kocak changed:
What|Removed |Added
Severity|Affects Some People |Affects Many People
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
Kubilay Kocak changed:
What|Removed |Added
Keywords||easy
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #52 from Bob Bishop ---
Just checked, the patch applies OK to STABLE and HEAD as of today.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
Bob Bishop changed:
What|Removed |Added
Flags|mfc-stable9?, mfc-stable10? |mfc-stable12?
--
You are receiving
Trying to install FreeBSD 11.2 on a new HPE Proliant Microserver Gen10.
As described in Bug 221350, I found that trying to boot the generic
installation media hangs on boot.
Found on the internet that adding:
hw.pci.realloc_bars="1"
to /boot/loader.conf on the generic installation media
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #51 from Rajesh ---
(In reply to Bob Bishop from comment #50)
Thanks for your response Bob. But I have couple of questions
1. __OSC returned error 0x10 - What does this message mean? Is it really an
issue?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #50 from Bob Bishop ---
(In reply to Rajesh from comment #48)
Doesn't sound like it's related.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #49 from Rajesh ---
Created attachment 193428
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=193428=edit
Panic trace with xhci driver attach
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
Rajesh changed:
What|Removed |Added
CC||rajf...@gmail.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
c...@curttech.com changed:
What|Removed |Added
CC||c...@curttech.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
robert_we...@comcast.net changed:
What|Removed |Added
CC||robert_we...@comcast.net
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #45 from Bob Bishop ---
(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?
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #43 from Bob Bishop ---
(In reply to mishu from comment #42)
Don't know about FreeNAS, but I think the patch applies to FreeBSD HEAD.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
mi...@mishulica.com changed:
What|Removed |Added
CC||mi...@mishulica.com
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #41 from Thomas Neuber ---
Created attachment 188403
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=188403=edit
Difference Report of dmesg
Same as before - storage and usb configuration changed,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #38 from Thomas Neuber ---
Created attachment 188398
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=188398=edit
verbose kernel messages with applied patch
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
Alexander Motin changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
Andrew Irwin changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #34 from Bob Bishop ---
(In reply to Jan Bramkamp from comment #33)
Of course.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #33 from Jan Bramkamp ---
(In reply to Bob Bishop from comment #30)
The correct syntax is:
set =
instead of:
set
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #32 from Jan Bramkamp ---
I tested the patch against FreeBSD 11.1/amd64 and it solved the problem.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
Mark Linimon changed:
What|Removed |Added
Keywords|needs-qa|patch
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #31 from Bob Bishop ---
Created attachment 187442
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=187442=edit
This patch adds a quirk to address the issue
I've attached a patch that fixes the problem.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #30 from Bob Bishop ---
(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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
Jan Bramkamp changed:
What|Removed |Added
CC|
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #27 from Jörn Lentes ---
(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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #26 from Jan Bramkamp ---
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #25 from Igor Porozov ---
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #24 from Jörn Lentes ---
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?
--
You are receiving this mail because:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
Igor Porozov changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #22 from Mikael D ---
(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.
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #21 from Jan Bramkamp ---
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
Jörn Lentes changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #19 from Jan Bramkamp ---
Disabling ACPI is no longer an acceptable workaround for modern system because
it disables a lot more than just power management for laptops.
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #18 from Mikael D ---
(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"
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
Jure K. changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #16 from Mikael D ---
(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.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #15 from Thomas Neuber ---
(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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #14 from Mikael D ---
(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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #12 from Thomas Neuber ---
Created attachment 186708
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=186708=edit
output of pciconf -lvbce
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #13 from Thomas Neuber ---
Created attachment 186709
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=186709=edit
output of devinfo -vr
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
Thomas Neuber changed:
What|Removed |Added
Attachment #186306|0 |1
is
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #10 from Jan Bramkamp ---
I just ran into the same bug.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #9 from Thomas Neuber ---
Created attachment 186306
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=186306=edit
Kernel Display Messages of the last boot
Compared to this file, the visible console
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #8 from Thomas Neuber ---
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
Jussi Hagman changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
Thomas Neuber changed:
What|Removed |Added
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
Kubilay Kocak changed:
What|Removed |Added
Keywords||crash, needs-qa
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #4 from Rafal Lukawiecki ---
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,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #3 from Rafal Lukawiecki ---
Created attachment 185174
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185174=edit
Panic when booting with ACPI off in boot options menu
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
Rafal Lukawiecki changed:
What|Removed |Added
Attachment #185173|Panic when booting with |Panic when
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #2 from Rafal Lukawiecki ---
Created attachment 185173
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185173=edit
Panic when booting with ACPI off
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #1 from Rafal Lukawiecki ---
Created attachment 185172
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=185172=edit
Non-verbose boot output showing more context before the hang
--
You are receiving
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
Rafal Lukawiecki changed:
What|Removed |Added
Hardware|i386|amd64
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
59 matches
Mail list logo