https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
Mark Linimon changed:
What|Removed |Added
Resolution|--- |Feedback Timeout
Status
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
Oleksandr Tymoshenko changed:
What|Removed |Added
CC||go...@freebsd.org
--- Comme
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #36 from Joseph King ---
(In reply to John Baldwin from comment #32)
According to what I have found this is the BCM5780(HT2000) + BCM5785(HT1000)
chipset per the spec sheet for the server. If this helps any. See
http://www.tyan
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #35 from Joseph King ---
(In reply to John Baldwin from comment #34)
Looks the same to me... tossed in the uname just to keep track.
root@netsys9:/ufs/home/storm # uname -a
FreeBSD netsys9.isolan.itsmine.com 10.2-STABLE FreeBS
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #34 from John Baldwin ---
Can you get the same output from the patched 10.x kernel?
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #33 from Joseph King ---
(In reply to John Baldwin from comment #32)
>From the 9.3-stable...
root@netsys9:/ufs/home/storm # pciconf -r pci0:0:8:0 0xb0:0xff
00410010 0982 01026c81
00810008 0008 000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #32 from John Baldwin ---
No, the dmesg output isn't needed. I'm curious how pciconf isn't breaking.
These devices (pcib5) certainly look odd.
Can you paste the output of this:
pciconf -r pci0:0:8:0 0xb0:0xff
--
You are re
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #31 from Joseph King ---
(In reply to John Baldwin from comment #29)
Hacky workaround looks like it's working. Want me to post the boot capture?
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #30 from Joseph King ---
No worries I figured you got busy IRL. I'll try the hack and let you know...
here's the pciconf from the 9.3-stable boot.
root@netsys9:/ufs/home/storm # pciconf -lc
pcib1@pci0:0:1:0: class=0x06040
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #29 from John Baldwin ---
Sorry, I forgot to reply earlier. This is really odd. Can you get 'pciconf
-lc' output under a working kernel? What's really odd is that the bit of code
that checks for capabilities (that is looping
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #28 from Joseph King ---
OK
OK boot -v
/boot/test/kernel text=0xfd2528 data=0x128030+0x207c00
syms=[0x8+0x145f20+0x8+0x160160]
Booting...
Table 'FACP' at 0xbfff0290
Table 'APIC' at 0xbfff0390
APIC: Found table at 0xbfff0390
APIC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #27 from John Baldwin ---
Ok, I've added some more tracing. Please do a 'git pull' and rebuild the
kernel and test again. This is still narrowing down where it is hanging and
doesn't have a fix yet.
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #26 from Joseph King ---
Okay... installed bmake... did a make -D ALWAYS_CHECK_MAKE kernel-toolchain
which went smoothly... did a make -D ALWAYS_CHECK_MAKE buildkernel which
resulted in
-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #22 from Bryan Drewery ---
... Actually it is supposed to bootstrap bmake and use that so it should have
been fine.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
John Baldwin changed:
What|Removed |Added
CC||bdrew...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #19 from Joseph King ---
(In reply to John Baldwin from comment #18)
Using FreeBSD netsys9.isolan.itsmine.com 9.3-RELEASE-p30 FreeBSD
9.3-RELEASE-p30 #0: Mon Nov 2 10:11:50 UTC 2015
r...@amd64-builder.daemonology.net:/usr/
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #18 from John Baldwin ---
(In reply to Joseph King from comment #16)
Install a version that works. Then build a test kernel with the patch and boot
it. One method of building a test kernel:
# Checkout a tree
% mkdir pr_19806
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
NGie Cooper changed:
What|Removed |Added
CC||n...@freebsd.org
--- Comment #17 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #16 from Joseph King ---
(In reply to John Baldwin from comment #15)
I'm using the install ISO images of FreeBSD 10.x-64 bit line... now if the
system refuses to boot the install disc completely... How exactly do you
recommend
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #15 from John Baldwin ---
Please try the patch (relative to stable/10) from
https://github.com/bsdjhb/freebsd/compare/stable/10...bsdjhb:pr_198062.diff .
It doesn't fix anything, just adds more tracing to try to narrow down whe
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #14 from Joseph King ---
No problem John, I understand. I've just given up trying to figure it out.
Here's the results.
FreeBSD 10.2 64bit w/hw.pci.clear_buses=1 boot -v captured from com1
OK
OK set hw.pci.clear_buses=1
OK boo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #13 from John Baldwin ---
So one thing to try is setting hw.pci.clear_buses=1 at the loader prompt. It
is hanging in between the PCI bus scan of bus 0 finding pcib4 and pcib5.
That isn't a real fix, just a test to try to narro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #12 from g...@metro.cx ---
Hi,
I do have a serial console hooked up to the machine. However, after 6 months i
stopped expecting a reply to this bug and decided to move the machine to
production with FreeBSD 9.3. I can obtain tra
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #11 from Joseph King ---
Gavin,
Here's the 10.2-64 bit
FreeBSD 10.2 64bit boot -v captured from com1
OK
OK boot -v
/boot/kernel/kernel text=0xfc8de8 data=0x1283b0+0x207880
syms=[0x8+0x145350+0x8+0x15fe20]
Booting...
SMAP type
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #10 from Joseph King ---
Gavin,
Here ya go as requested. Hopefully this helps. Due to the size of the capture
log... I'm going to have to post these seperately... this is the 9.3-64 bit
FreeBSD 9.3 64bit boot -v captured from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
Gavin Atkinson changed:
What|Removed |Added
Status|New |Open
--- Comment #9 from Gavin At
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #8 from Joseph King ---
As request by John Baldwin... comconsole captures of 9.3-64bit and 10.2-64bit.
-- is the break between the captures.
FreeBSD 9.3-64bit boot captured from com1
OK boot
/boot/kernel/kernel text=0x
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
John Baldwin changed:
What|Removed |Added
CC||j...@freebsd.org
--- Comment #7 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #6 from Joseph King ---
9.3-Release 64bit works fine.
10.0-Release 64bit fails at same place at 10.1-Release 64bit.
10.1-Release 64bit fails the same as noted by g...@metro.cx
10.1-Release 32bit works however need 64 bit due to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #3 from g...@metro.cx ---
Created attachment 153561
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=153561&action=edit
bios startup screen
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #4 from g...@metro.cx ---
Created attachment 153562
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=153562&action=edit
bios summary screen
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #5 from g...@metro.cx ---
dmesg from the 9.3 install:
Copyright (c) 1992-2014 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rig
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #2 from g...@metro.cx ---
Created attachment 153560
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=153560&action=edit
normal boot output
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
--- Comment #1 from g...@metro.cx ---
Created attachment 153559
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=153559&action=edit
verbose boot output
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198062
Bug ID: 198062
Summary: FreeBSD 10.1-RELEASE kernel freezes on 'pci0: on pcib0'
Product: Base System
Version: 10.1-RELEASE
Hardware: amd64
OS: Any
Status: Ne
35 matches
Mail list logo
