Re: [SOLVED] Re: Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice

[jungle boogie]

On 07/10/2017 10:48 PM, Konstantin Belousov wrote:

On Mon, Jul 10, 2017 at 01:00:05PM -0700, Mark Johnston wrote:

I suspect that this is a result of r320763. That change removed a field
from struct vm_map_entry, which is embedded in struct vm_map. Virtualbox
does not reference the fields of struct vm_map directly, but it does
call vm_map_pmap(), which is an inline accessor.


Thank you for noting.  I do not consider vm_map part of the guaranteed
stable KBI, but in this case it is simpler to add padding than to follow
principles.

Fixed in 320889, will ask re for MFS permissions in a day.


I think this is the commit:
https://svnweb.freebsd.org/base/stable/11/sys/vm/vm_map.h?view=log=320889

Do you think this will get picked up by/for RC3, which will begin on Friday?
https://www.freebsd.org/releases/11.1R/schedule.html

Thanks!
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD as VirtualBox guest panics when starting VBoxService

[jungle Boogie]

Hi All!
On 24 May 2017 at 08:45, Glen Barber  wrote:
>> >
>> > Confirmed, this is resolved after r318743.
>> >
>>
>> Great news! Then it's clearly something on my side. What's your host OS?
>>
>
> FreeBSD 12-CURRENT.  One thing to note about the image I just used to
> test, it is not named 11.0-STABLE anymore.
>
> Try this:
>
>  $ vagrant init freebsd/FreeBSD-11.1-PRERELEASE
>  $ vagrant up

All good now!!

FreeBSD  11.1-PRERELEASE FreeBSD 11.1-PRERELEASE #1 r318789: Wed May
24 14:53:20 UTC 2017
r...@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64

This one and Patrick's are working. I think my fault was in using the
same directory as the previous failed builds. The vagrant
remove/destroy commands don't actually delete the existing Vagrantfile
files.

Thanks to Eric, Patrick and Glen!!


>
> Glen
>



-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD as VirtualBox guest panics when starting VBoxService

[jungle Boogie]

On 24 May 2017 at 08:19, Glen Barber <g...@freebsd.org> wrote:
> On Tue, May 23, 2017 at 01:14:56PM -0700, jungle Boogie wrote:
>> Hi Eric,
>> On 23 May 2017 at 05:47, Eric Badger <bad...@freebsd.org> wrote:
>> > On 04/26/2017 09:01 AM, David Boyd wrote:
>> >>
>> >> Using 11.0-STABLE VM image snapshots, since April 05, 2017, FreeBSD
>> >> panics when VBoxService starts.
>> >>
>> >> using snapshot FreeBSD-11.0-RELEASE-amd64.vmdk no panic occurs.
>> >>
>> >> using snapshot FreeBSD-11.0-STABLE-amd64-20170323-r315855.vmdk no panic
>> >> occurs.
>> >>
>> >> using snapshot FreeBSD-11.0-STABLE-amd64-20170405-r316498.vmdk panic
>> >> occurs (see attachment).
>> >>
>> >> using snapshot FreeBSD-11.0-STABLE-amd64-20170420-r317153.vmdk panic
>> >> occurs (see attachment).
>> >>
>> >> using snapshot FreeBSD-12.0-CURRENT-amd64.vmdk no panic occurs.
>> >>
>> >> I am prepared to submit a PR if that is the thing to do.
>> >>
>> >> Thanks, in advance, for your assistance in this matter.
>> >>
>> >
>> > Please try again after r318743. I believe it fixes this problem.
>> >
>>
>> This sounds like good news! Maybe when the next snapshots are created,
>> this will be fixed.
>>
>> There's a couple PR's opened on this issue, but neither of them have
>> any updates. Was this tracked under a different PR?
>>
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219146
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219227
>>
>
> Confirmed, this is resolved after r318743.
>

Great news! Then it's clearly something on my side. What's your host OS?


> Glen
>



-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD as VirtualBox guest panics when starting VBoxService

[jungle Boogie]

Hi Patrick,
On 23 May 2017 at 05:52, Patrick M. Hausen  wrote:
> Hi, all,
>
> just for the record - today I published our own boxesat Hashicorp Atlas:
>
> https://atlas.hashicorp.com/punktde
>
> If you trust me enough, enjoy ;-)
>
> FreeBSD 11.0p10 - we intend to publish updated ones
> for every FreeBSD update.
>

Thanks for making this.

Using Windows 7 with VirtualBox version 5.1.22, the VM is in a
continuous reboot.
Are you not experiencing this?


> Kind regards,
> Patrick



-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: FreeBSD as VirtualBox guest panics when starting VBoxService

[jungle Boogie]

Hi Eric,
On 23 May 2017 at 05:47, Eric Badger  wrote:
> On 04/26/2017 09:01 AM, David Boyd wrote:
>>
>> Using 11.0-STABLE VM image snapshots, since April 05, 2017, FreeBSD
>> panics when VBoxService starts.
>>
>> using snapshot FreeBSD-11.0-RELEASE-amd64.vmdk no panic occurs.
>>
>> using snapshot FreeBSD-11.0-STABLE-amd64-20170323-r315855.vmdk no panic
>> occurs.
>>
>> using snapshot FreeBSD-11.0-STABLE-amd64-20170405-r316498.vmdk panic
>> occurs (see attachment).
>>
>> using snapshot FreeBSD-11.0-STABLE-amd64-20170420-r317153.vmdk panic
>> occurs (see attachment).
>>
>> using snapshot FreeBSD-12.0-CURRENT-amd64.vmdk no panic occurs.
>>
>> I am prepared to submit a PR if that is the thing to do.
>>
>> Thanks, in advance, for your assistance in this matter.
>>
>
> Please try again after r318743. I believe it fixes this problem.
>

This sounds like good news! Maybe when the next snapshots are created,
this will be fixed.

There's a couple PR's opened on this issue, but neither of them have
any updates. Was this tracked under a different PR?

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219146
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219227

> Eric


-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11 stable vagrant images: page fault

[jungle boogie]

On 05/06/2017 10:11 PM, jungle boogie wrote:

Hi All,

I'm using 11-stable Vagrant image from here:
https://atlas.hashicorp.com/freebsd/boxes/FreeBSD-11.0-STABLE
(tried 20th of April and 5th of April).

Unfortunately, I can only get the VM to stay up for about 9 seconds,
because it's in a constant reboot loop.



This is still happening with the vagrant image from the 11th of May, 2017:
https://atlas.hashicorp.com/freebsd/boxes/FreeBSD-11.0-STABLE/versions/2017.05.11.2

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11 stable vagrant images: page fault

[jungle boogie]

On 05/07/2017 03:21 AM, Stefan Bethke wrote:



Am 07.05.2017 um 07:11 schrieb jungle boogie <jungleboog...@gmail.com>:

I'm using 11-stable Vagrant image from here:
https://atlas.hashicorp.com/freebsd/boxes/FreeBSD-11.0-STABLE
(tried 20th of April and 5th of April).

Unfortunately, I can only get the VM to stay up for about 9 seconds, because 
it's in a constant reboot loop.

This command will stop the reboot:
VBoxManage setextradata stable_default_1494131864056_36337 
"VBoxInternal/PDM/HaltOnReset" 1

And when doing so, I see this failure:
http://imgur.com/a/USHdB

I can download 11-stable and 12-current vdh files and import those into 
virtualbox, resulting in those not crashing.
11-stable is from the 20th of April.


Out of curiosity, can you try: 
https://atlas.hashicorp.com/stblassitude/boxes/freebsd-11



Works!
$ uname -a; freebsd-version -ku
FreeBSD  11.0-RELEASE-p9 FreeBSD 11.0-RELEASE-p9 #0: Tue Apr 11 08:48:40 
UTC 2017 
r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

11.0-RELEASE-p9
11.0-RELEASE-p10

So something is broken with those very specific 11-stable virtual 
machines. I went back to March and found one that works:
FreeBSD  11.0-STABLE FreeBSD 11.0-STABLE #0 r315416: Thu Mar 16 17:20:57 
UTC 2017



Very interesting the official image has been 'revoked':
https://atlas.hashicorp.com/freebsd/boxes/FreeBSD-11.0-RELEASE


I was unhappy with the official images, so I’m building my own.  On my Mac, I 
can run my image (including the latest freebsd-update patches), without 
problems.

The main difference in my image is that the freebsd-update patches are already 
rolled into the image, so there’s no reboot cycle with vagrant up.  I’m 
updating the image every couple of weeks.
The packer config is at https://github.com/stblassitude/packer-freebsd


Thanks, I'll check that out. I think a little more than a year ago there 
was a freeBSD journal article by Steve Willis or Brad Davis (I think!) 
about vagrant and packer.


In addition to that article (if I still have it), do you have any 
reading material about vagrant/packer and making own images?





Stefan



___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

11 stable vagrant images: page fault

[jungle boogie]

Hi All,

I'm using 11-stable Vagrant image from here:
https://atlas.hashicorp.com/freebsd/boxes/FreeBSD-11.0-STABLE
(tried 20th of April and 5th of April).

Unfortunately, I can only get the VM to stay up for about 9 seconds, 
because it's in a constant reboot loop.


This command will stop the reboot:
VBoxManage setextradata stable_default_1494131864056_36337 
"VBoxInternal/PDM/HaltOnReset" 1


And when doing so, I see this failure:
http://imgur.com/a/USHdB

I can download 11-stable and 12-current vdh files and import those into 
virtualbox, resulting in those not crashing.

11-stable is from the 20th of April.


I also have this 12-current vagrant box working:
vagrant@:~ % uname -a
FreeBSD  12.0-CURRENT FreeBSD 12.0-CURRENT #0 r316750: Thu Apr 13 
08:03:28 UTC 2017 
r...@releng3.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64


The host is some Unbuntu version:
4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux


VirtualBox is version 5.1.22 r115126, which is the most current version:
https://www.virtualbox.org/wiki/Changelog

Any thoughts?

Thanks!
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Failing to upgrade from 10.1-RELEASE to 10.3-STABLE

[jungle Boogie]

  If I decide to upgrade from 10.3-RELEASE to 10.3-STABLE
> later on, should I expect that to work?   -- George
> _

No. Freebsd-update is only for binary updates. Stable and head are where
you build from source and therefore, freebsd-update doesn't work.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: 11.0-RELEASE Status Update

[jungle Boogie]

On 6 October 2016 at 13:18, Glen Barber  wrote:
> the final release announcement is planned for Monday, October 10.

suggestion:
update the schedule
https://www.freebsd.org/releases/11.0R/schedule.html



-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: nginx and FreeBSD11

[jungle Boogie]

On 15 September 2016 at 07:41, Slawa Olhovchenkov  wrote:
> Bingo!
> aio read file by process 1055 placed to same memory address as requested but 
> in memory space of process 1060!
>
> This is kernel bug and this bug must be stoped release.

When was it introduced?


-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Error upgrading from 10.1-RELEASE to 10.2-RELEASE

[jungle Boogie]

On 24 August 2015 at 05:14, Bjoern A. Zeeb
bzeeb-li...@lists.zabbadoz.net wrote:
 please see the thread “freebsd-update to 10.2-RELEASE broken ?” on this 
 mailing list from this month;  I think there is no solution yet.

The solution for me was to use a different DNS server on one of my
machines. Others with a sensible DNS resolver fetched the files fine.


-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
xmpp: jungle-boo...@jit.si
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: pkg clean question

[jungle Boogie]

On 3 August 2015 at 09:13, Paul Mather freebsd-li...@gromit.dlib.vt.edu wrote:
 On Aug 3, 2015, at 11:39 AM, Zoran Kolic zko...@sbb.rs wrote:

 Amd64, 9.3. Updated few times, packages also. At first I
 found on laptop that /var directory was at 102%. Using
 pkg clean i removed about 400mb of cache packages from
 /var/cache/pkg. Tried to clean desktop cache and the out-
 put of the command was nothing to do. I see about 400
 mb of files in the cache directory. Is it safe to remove
 them by the hand?


 Use pkg clean -ay to delete all cached packages, not just the ones that are 
 no longer current or provided by the upstream repository.



You may want to autoremove, too:

autoremove
 Delete packages which were automatically installed as dependen-
 cies and are not required any more.

 Cheers,

 Paul.




-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
xmpp: jungle-boo...@jit.si
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

Re: building -stable after FreeBSD-SA-15:10.openssl

[jungle Boogie]

On 17 June 2015 at 11:23, Kimmo Paasiala kpaas...@gmail.com wrote:
 Don't use the patch at all if you're following stable/10, the
 necessary security fixes are already included in updates you pull in
 from SVN.


Oh, so in the future, just svn up and rebuild?

Thanks for the tip on reverting, I'll try that out.

-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
xmpp: jungle-boo...@jit.si
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org

building -stable after FreeBSD-SA-15:10.openssl

[jungle Boogie]

Hello All,

Trying to upgrade from r283863 to 284520 after I applied this patch:
https://www.freebsd.org/security/advisories/FreeBSD-SA-15:10.openssl.asc

In the manner described:

# fetch https://security.FreeBSD.org/patches/SA-15:10/openssl-10.1.patch
# cd /usr/src
# patch  /path/to/patch


I begin the build by doing:
cd /usr/src
svn update
make -j `sysctl -n hw.ncpu` buildworld  -DNO_CLEAN

But then this happened:

Removing stale symlinks.
rm -f /usr/obj/usr/src/tmp/usr/include/des.h
rm -f /usr/obj/usr/src/tmp/usr/lib/libdes.a
rm -f /usr/obj/usr/src/tmp/usr/lib/libdes.so
rm -f /usr/obj/usr/src/tmp/usr/lib/libdes.so.3
rm -f /usr/obj/usr/src/tmp/usr/lib/libdes_p.a
=== lib/libldns (obj,depend,all,install)
sh /usr/src/tools/install.sh -C -o root -g wheel -m 444   libldns.a
/usr/obj/usr/src/tmp/usr/lib/private
sh /usr/src/tools/install.sh -s -o root -g wheel -m 444
libldns.so.5 /usr/obj/usr/src/tmp/usr/lib/private
sh /usr/src/tools/install.sh -l s libldns.so.5
/usr/obj/usr/src/tmp/usr/lib/private/libldns.so
=== secure/lib/libssl (obj,depend,all,install)
cc  -fpic -DPIC  -O2 -pipe   -DTERMIOS -DANSI_SOURCE
-I/usr/src/secure/lib/libssl/../../../crypto/openssl
-I/usr/src/secure/lib/libssl/../../../crypto/openssl/crypto
-I/usr/obj/usr/src/secure/lib/libssl -DOPENSSL_THREADS -DDSO_DLFCN
-DH$
/usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:3371:9:
error: redefinition of 'al'
int al = SSL_AD_HANDSHAKE_FAILURE;
^
/usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:3276:9:
note: previous definition is here
int al = SSL_AD_HANDSHAKE_FAILURE;
^
1 error generated.
*** [s3_clnt.So] Error code 1

make[4]: stopped in /usr/src/secure/lib/libssl
1 error

make[4]: stopped in /usr/src/secure/lib/libssl
A failure has been detected in another branch of the parallel make

make[3]: stopped in /usr/src
*** [libraries] Error code 2

make[2]: stopped in /usr/src
1 error

make[2]: stopped in /usr/src
*** [_libraries] Error code 2

make[1]: stopped in /usr/src
1 error

make[1]: stopped in /usr/src
*** [buildworld] Error code 2

make: stopped in /usr/src
1 error

make: stopped in /usr/src



My patch happened to be in /usr/src when I applied it. Is this what
caused the issue?

Is there a way to revert the patch?


Thanks  Best,
jungle

-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
xmpp: jungle-boo...@jit.si
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org