https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221050
Kurt Jaeger changed:
What|Removed |Added
CC||p...@freebsd.org
--- Comment #10 fro
On 27.07.2017 23:28, Konstantin Belousov wrote:
>> Trying to mount root from ufs:/dev/ada0s1a [ro]...
>> start_init: trying /sbin/init
>> ppid 21 (sh), uid 0: exited on signal 12
>> id 21 comm sh: nosys 42
>> Jul 27 14:30:23 init: /bin/sh on /etc/rc terminated abnormally, going to
>> single user
On 27.07.2017 23:28, Konstantin Belousov wrote:
> Take your /bin/sh, libraries and rtld to some other machine and try to
> catch where the pipe(2) call come from. I do not see any other way
> forward, assuming your build env is not contaminated somehow.
>
> I did the following on the today stabl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221050
--- Comment #9 from Eugene Grosbein ---
You generally need not rebuild ports/packages after minor OS upgrade.
Unfortunately, this does not apply to packages containing own kernel modules -
you may need to rebuild/reinstall them after minor
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221050
--- Comment #8 from stei...@nognu.de ---
Ok, I can confirm that bridged networking works again when virtualbox-ose is
build from source when it's complete dependency chain is also built from
ports.
It makes sense to me that virtualbox nee
Not sure if this is normal behaviour or not, but on a recent RELENG_11
r321624, I noticed something odd about rand_harvestq.
While doing some disk stress testing of zfs, I was creating a bunch of
random files.
eg
dd if=/dev/urandom > /tmp/junk2 bs=1m count=1
If I create enough of them, rand_h
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221050
Jung-uk Kim changed:
What|Removed |Added
CC||j...@freebsd.org
--- Comment #7 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221050
--- Comment #6 from stei...@nognu.de ---
Created attachment 184774
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=184774&action=edit
Vbox.log from a session where bridged network does not work
--
You are receiving this mail beca
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221050
--- Comment #5 from stei...@nognu.de ---
Some more details.
This is from 2017Q3 packages:
* I have no firewall or whatsoever in place on the host.
* Attached is VBox.log when running an OpenBSD guest where bridged networking
does not work.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221050
--- Comment #4 from stei...@nognu.de ---
Created attachment 184773
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=184773&action=edit
virtualbox-ose build failure from 2017Q3 ports on 11.1-RELEASE
--
You are receiving this mail b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221050
--- Comment #3 from stei...@nognu.de ---
Created attachment 184772
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=184772&action=edit
kBuild build failure from 2017Q3 ports on 11.1-RELEASE
--
You are receiving this mail because:
On Thu, Jul 27, 2017 at 10:06:53PM +0700, Eugene Grosbein wrote:
> Hi!
>
> Very recently stable/11 got a problem somewhere between r321073 and r321459:
> /bin/sh crashes with SIGSYS at boot time:
>
> Trying to mount root from ufs:/dev/ada0s1a [ro]...
> start_init: trying /sbin/init
> ppid 21 (sh)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221050
Vladimir Krstulja changed:
What|Removed |Added
Summary|FreeBSD 11.1-RELEASE: |emulators/virtualbox-ose:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221050
Eugene Grosbein changed:
What|Removed |Added
CC||eu...@freebsd.org
--- Comment #2
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221050
stei...@nognu.de changed:
What|Removed |Added
CC||stei...@nognu.de
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221050
Bug ID: 221050
Summary: FreeBSD 11.1-RELEASE: virtualbox bridged network dont
work
Product: Ports & Packages
Version: Latest
Hardware: amd64
OS: Any
On Thu, Jul 27, 2017 at 04:29:52PM +0300, Alexander Motin wrote:
> Hi Mike,
>
> On 27.07.2017 16:21, Mike Tancsa wrote:
> > I noticed quite a few MFCs to RELENG_11 around zfs yesterday and today.
> > First off, thank you for all these fixes/enhancements! Of the some 60
> > MFCs, are there any
Hi!
Very recently stable/11 got a problem somewhere between r321073 and r321459:
/bin/sh crashes with SIGSYS at boot time:
Trying to mount root from ufs:/dev/ada0s1a [ro]...
start_init: trying /sbin/init
ppid 21 (sh), uid 0: exited on signal 12
id 21 comm sh: nosys 42
Jul 27 14:30:23 init: /bin/s
On Thu, 27 Jul 2017 13:03+0200, Trond Endrestøl wrote:
> On Thu, 27 Jul 2017 11:57+0100, tech-lists wrote:
>
> > On 27/07/2017 10:33, Trond Endrestøl wrote:
> > > r321601 gives me these error messages on stable/11:
> > >
> > > /usr/src/usr.sbin/acpi/acpidump/acpi.c:1089:6: error: use of undeclar
On Thu, Jul 27, 2017 at 08:38:22AM -0400, Ed Maste wrote:
> On 27 July 2017 at 07:02, David Wolfskill wrote:
> > /usr/src/usr.sbin/acpi/acpidump/acpi.c:1089:6: error: use of undeclared
> > identifier 'ACPI_SRAT_TYPE_GIC_ITS_AFFINITY'; did you mean
> > 'ACPI_SRAT_TYPE_GICC_AFFINITY'?
>
> Sorry a
Hi Mike,
On 27.07.2017 16:21, Mike Tancsa wrote:
> I noticed quite a few MFCs to RELENG_11 around zfs yesterday and today.
> First off, thank you for all these fixes/enhancements! Of the some 60
> MFCs, are there any particular ones to be more aware of when updating
> servers ?
The most co
Hi,
I noticed quite a few MFCs to RELENG_11 around zfs yesterday and today.
First off, thank you for all these fixes/enhancements! Of the some 60
MFCs, are there any particular ones to be more aware of when updating
servers ? Are there any more to come, or is now a good time to test
things
On 27 July 2017 at 07:02, David Wolfskill wrote:
> /usr/src/usr.sbin/acpi/acpidump/acpi.c:1089:6: error: use of undeclared
> identifier 'ACPI_SRAT_TYPE_GIC_ITS_AFFINITY'; did you mean
> 'ACPI_SRAT_TYPE_GICC_AFFINITY'?
Sorry about that, reverted in r321617.
__
On Thu, Jul 27, 2017 at 04:02:12AM -0700, David Wolfskill wrote:
> ...
> I will try the substitution clang suggests, then follow up.
>
That failed; following the hint from "Herbert J. Skuhra"
, I tried a cherry-pick merge of r319365. That
seemed to get through src/usr.sbin/acpi/acpidump OK,
freebeast(11.1-S)[1] uname -a
FreeBSD freebeast.catwhisker.org 11.1-STABLE FreeBSD 11.1-STABLE #409
r321515M/321515:1101501: Wed Jul 26 03:46:30 PDT 2017
r...@freebeast.catwhisker.org:/common/S1/obj/usr/src/sys/GENERIC amd64
freebeast(11.1-S)[2]
freebeast(11.1-S)[2] svn info /usr/src
Path
On Thu, 27 Jul 2017, Trond Endrestøl wrote:
r321601 gives me these error messages on stable/11:
/usr/src/usr.sbin/acpi/acpidump/acpi.c:1089:6: error: use of undeclared
identifier 'ACPI_SRAT_TYPE_GIC_ITS_AFFINITY'; did you mean
'ACPI_SRAT_TYPE_GICC_AFFINITY'?
[ACPI_SRAT_TYPE_GIC_ITS_AFFINIT
On Thu, 27 Jul 2017 11:57+0100, tech-lists wrote:
> On 27/07/2017 10:33, Trond Endrestøl wrote:
> > r321601 gives me these error messages on stable/11:
> >
> > /usr/src/usr.sbin/acpi/acpidump/acpi.c:1089:6: error: use of undeclared
> > identifier 'ACPI_SRAT_TYPE_GIC_ITS_AFFINITY'; did you mean
On 27/07/2017 10:33, Trond Endrestøl wrote:
> r321601 gives me these error messages on stable/11:
>
> /usr/src/usr.sbin/acpi/acpidump/acpi.c:1089:6: error: use of undeclared
> identifier 'ACPI_SRAT_TYPE_GIC_ITS_AFFINITY'; did you mean
> 'ACPI_SRAT_TYPE_GICC_AFFINITY'?
> [ACPI_SRAT_TYPE_GIC_I
r321601 gives me these error messages on stable/11:
/usr/src/usr.sbin/acpi/acpidump/acpi.c:1089:6: error: use of undeclared
identifier 'ACPI_SRAT_TYPE_GIC_ITS_AFFINITY'; did you mean
'ACPI_SRAT_TYPE_GICC_AFFINITY'?
[ACPI_SRAT_TYPE_GIC_ITS_AFFINITY] = "GIC ITS",
^
29 matches
Mail list logo
