[Bug 206326] mandoc -r294113's parse assertion fd > 0 is failing: main's STDIN_FILENO use does not meet that criteria

2016-01-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206326 Bug ID: 206326 Summary: mandoc -r294113's parse assertion fd > 0 is failing: main's STDIN_FILENO use does not meet that criteria Product: Base System Version: 11.0-CURRENT

[Bug 198062] FreeBSD 10.1-RELEASE kernel freezes on 'pci0: on pcib0'

2016-01-16 Thread bugzilla-noreply
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

[Bug 206224] bv_cnt is sometimes examined without holding the bufobj lock

2016-01-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206224 --- Comment #2 from commit-h...@freebsd.org --- A commit references this bug: Author: rpokala Date: Sun Jan 17 01:04:20 UTC 2016 New revision: 294200 URL: https://svnweb.freebsd.org/changeset/base/294200 Log: [PR 206224] bv_cnt is someti

[Bug 198062] FreeBSD 10.1-RELEASE kernel freezes on 'pci0: on pcib0'

2016-01-16 Thread bugzilla-noreply
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

[Bug 198062] FreeBSD 10.1-RELEASE kernel freezes on 'pci0: on pcib0'

2016-01-16 Thread bugzilla-noreply
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

[Bug 198062] FreeBSD 10.1-RELEASE kernel freezes on 'pci0: on pcib0'

2016-01-16 Thread bugzilla-noreply
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

[Bug 205926] jail(8): fails to parse ifconfig parameters in ip4.addr and ip6.addr after /netmask

2016-01-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205926 Jamie Gritton changed: What|Removed |Added CC||ja...@freebsd.org Assign

[Bug 204264] arm64 kldxref produces Bad address warning for each ko

2016-01-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204264 Andrew Turner changed: What|Removed |Added Status|New |Closed Resolution|---

[Bug 203349] [META] FreeBSD Foundation sponsored project dependencies for FreeBSD 11.0

2016-01-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203349 Bug 203349 depends on bug 204264, which changed state. Bug 204264 Summary: arm64 kldxref produces Bad address warning for each ko https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204264 What|Removed |Adde

[Bug 206310] The vnic driver may lock an uninitialised mutex

2016-01-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206310 Andrew Turner changed: What|Removed |Added CC||ema...@freebsd.org Assig

[Bug 206310] The vnic driver may lock an uninitialised mutex

2016-01-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206310 Bug ID: 206310 Summary: The vnic driver may lock an uninitialised mutex Product: Base System Version: 11.0-CURRENT Hardware: arm64 OS: Any Status: New