[Bug 236838] Commit r340224 prevents loading the kernel for some Intel Xeon hardware

2019-08-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236838 longw...@incore.de changed: What|Removed |Added Status|New |Closed Resolution|---

[Bug 236838] Commit r340224 prevents loading the kernel for some Intel Xeon hardware

2019-04-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236838 --- Comment #12 from commit-h...@freebsd.org --- A commit references this bug: Author: kib Date: Tue Apr 16 17:16:19 UTC 2019 New revision: 346284 URL: https://svnweb.freebsd.org/changeset/base/346284 Log: MFC r346062: pci_cfgreg.c: Us

[Bug 236838] Commit r340224 prevents loading the kernel for some Intel Xeon hardware

2019-04-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236838 --- Comment #11 from commit-h...@freebsd.org --- A commit references this bug: Author: kib Date: Tue Apr 9 18:07:18 UTC 2019 New revision: 346062 URL: https://svnweb.freebsd.org/changeset/base/346062 Log: pci_cfgreg.c: Use io port confi

[Bug 236838] Commit r340224 prevents loading the kernel for some Intel Xeon hardware

2019-04-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236838 --- Comment #10 from Konstantin Belousov --- I put a review to allow some more eyes on this patch. https://reviews.freebsd.org/D19833 -- You are receiving this mail because: You are the assignee for the bug. _

[Bug 236838] Commit r340224 prevents loading the kernel for some Intel Xeon hardware

2019-04-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236838 --- Comment #9 from longw...@incore.de --- I can confirm the patch based on the variable pmap_initialized works for my older hardware with vid=0x8086 and did=0x3590. The hang without the patch was in the function pcie_cfgregopen(). For my o

Re: [Bug 236838] Commit r340224 prevents loading the kernel for some Intel Xeon hardware

2019-04-04 Thread Bruce Evans
On Thu, 4 Apr 2019 a bug that dpesnt want repl...@freebsd.org wrote: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236838 --- Comment #5 from longw...@incore.de --- Created attachment 203384 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203384&action=edit Output serial console of

[Bug 236838] Commit r340224 prevents loading the kernel for some Intel Xeon hardware

2019-04-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236838 --- Comment #8 from Konstantin Belousov --- Created attachment 203388 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203388&action=edit Do not use memory-mapped config space access for PCIe on older chipsets until pmap is ready t

[Bug 236838] Commit r340224 prevents loading the kernel for some Intel Xeon hardware

2019-04-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236838 --- Comment #7 from Konstantin Belousov --- Created attachment 203387 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203387&action=edit Do not use memory-mapped config space access for PCIe on older chipsets until pmap is ready t

[Bug 236838] Commit r340224 prevents loading the kernel for some Intel Xeon hardware

2019-04-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236838 --- Comment #6 from Konstantin Belousov --- (In reply to longwitz from comment #5) I think it is not the 0xce register read which causes the hang, but the need to map very large (255MB) region by chomping from virtual_avail which causes the

[Bug 236838] Commit r340224 prevents loading the kernel for some Intel Xeon hardware

2019-04-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236838 --- Comment #5 from longw...@incore.de --- Created attachment 203384 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203384&action=edit Output serial console of full verbose boot I use amd64, the commit r340224 (r339979) does only

[Bug 236838] Commit r340224 prevents loading the kernel for some Intel Xeon hardware

2019-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236838 --- Comment #4 from Konstantin Belousov --- Are you running i386 or amd64 ? Select right file sys/i386/pci/pci_cfgreg.c or sys/amd64/pci/pci_cfgreg.c, find the pci_cfgregopen() function and remove the 'case 0x3590:' line. Does it help ? A

[Bug 236838] Commit r340224 prevents loading the kernel for some Intel Xeon hardware

2019-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236838 longw...@incore.de changed: What|Removed |Added CC||longw...@incore.de --- Comment

[Bug 236838] Commit r340224 prevents loading the kernel for some Intel Xeon hardware

2019-04-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236838 --- Comment #2 from Konstantin Belousov --- Can you show the output of 'pciconf -lvcb' ? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org ma

[Bug 236838] Commit r340224 prevents loading the kernel for some Intel Xeon hardware

2019-04-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236838 Ed Maste changed: What|Removed |Added CC||ema...@freebsd.org, |

[Bug 236838] Commit r340224 prevents loading the kernel for some Intel Xeon hardware

2019-03-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236838 Bug ID: 236838 Summary: Commit r340224 prevents loading the kernel for some Intel Xeon hardware Product: Base System Version: 12.0-STABLE Hardware: amd64