Boot hang on Xen after r318347/(310418)

2017-05-24 Thread Adam McDougall 
Hello,

Recently I made a new build of 11-STABLE but encountered a boot hang
at this state:
http://www.egr.msu.edu/~mcdouga9/pics/r318347-smp-hang.png

It is easy to reproduce, I can just boot from any 11 or 12 ISO that 
contains the commit.

I compiled various svn revisions to confirm that r318347 caused the 
issue and r318346 is fine. With r318347 or later including the latest 
11-STABLE, the system will only boot with one virtual CPU in XenServer. 
Any more cpus and it hangs. I also tried a 12 kernel from head this 
afternoon and I have the same hang. I had this issue on XenServer 7 
(Xen 4.7) and XenServer 6.5 (Xen 4.4). I did most of my testing on 7. I 
also did much of my testing with a GENERIC kernel to try to rule out 
kernel configuration mistakes. When it hangs, the performance 
monitoring in Xen tells me at least one CPU is pegged. r318674 boots 
fine on physical hardware without Xen involved.

Looking at r318347 which mentions EARLY_AP_STARTUP and later seeing 
r318763 which enables EARLY_AP_STARTUP in GENERIC, I tried adding it to 
my kernel but it turned the hang into a panic but with any number of 
CPUs: 
http://www.egr.msu.edu/~mcdouga9/pics/r318347-early-ap-startup-panic.png

I think I verified that this happens with EARLY_AP_STARTUP before
r318347 too so I'll assume it is a different problem.

I may need to do some experimentation to figure out how to get the 
console to pass through hotkeys to drop into a kernel debugger. I could 
also try modifying the kernel config if I can make it print information 
about the hang.

Is there anything else I can provide that might help? Would you prefer 
this be entered in a bugzilla report? 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: Update netmap for 11.1-RELEASE

2017-05-24 Thread Mark Saad 
+1

On Wed, May 24, 2017 at 1:09 PM, George Amanakis via freebsd-stable
 wrote:
> Regarding the upcoming 11.1-RELEASE:
> Could somebody update netmap from CURRENT to STABLE, so that it would make it 
> into 11.1-RELEASE?
> I would really like to see ptnet and ptnetmap in 11.1-RELEASE.
>
> Thank you!
> George
> ___
> 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"



-- 
mark saad | nones...@longcount.org
___
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"

Update netmap for 11.1-RELEASE

2017-05-24 Thread George Amanakis via freebsd-stable 
Regarding the upcoming 11.1-RELEASE:
Could somebody update netmap from CURRENT to STABLE, so that it would make it 
into 11.1-RELEASE? 
I would really like to see ptnet and ptnetmap in 11.1-RELEASE.

Thank you!
George
___
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: No TCP-MD5 in 11.1-PRERELEASE.

2017-05-24 Thread Marek Zarychta 
On Mon, May 22, 2017 at 10:15:03PM +0200, Kurt Jaeger wrote:
> Hi!
> 
> > After upgrading to 11.1-PRERELEASE, none of my MD5 BGP connections are
> > coming up.  They were fine in 11.0-RELEASE.
> 
> Please submit a PR via bugs.freebsd.org and send the PR number.
> 
> We should bring this to the attention of re@.
> 
This bug has been already submitted:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219453
-- 
Marek Zarychta


signature.asc
Description: PGP signature

Re: FreeBSD as VirtualBox guest panics when starting VBoxService

2017-05-24 Thread 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: No TCP-MD5 in 11.1-PRERELEASE.

2017-05-24 Thread Marek Zarychta 
On Mon, May 22, 2017 at 10:15:03PM +0200, Kurt Jaeger wrote:
> Hi!
> 
> > After upgrading to 11.1-PRERELEASE, none of my MD5 BGP connections are
> > coming up.  They were fine in 11.0-RELEASE.
> 
> Please submit a PR via bugs.freebsd.org and send the PR number.
> 
> We should bring this to the attention of re@.
> 
This bug has been already submitted:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219453
-- 
Marek Zarychta


signature.asc
Description: PGP signature

Re: FreeBSD as VirtualBox guest panics when starting VBoxService

2017-05-24 Thread Glen Barber 
On Wed, May 24, 2017 at 08:28:37AM -0700, jungle Boogie wrote:
> On 24 May 2017 at 08:19, Glen Barber  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  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?
> 

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

Glen



signature.asc
Description: PGP signature

Re: FreeBSD as VirtualBox guest panics when starting VBoxService

2017-05-24 Thread jungle Boogie 
On 24 May 2017 at 08:19, Glen Barber  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  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

2017-05-24 Thread Glen Barber 
On Tue, May 23, 2017 at 01:14:56PM -0700, jungle Boogie wrote:
> 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
> 

Confirmed, this is resolved after r318743.

Glen



signature.asc
Description: PGP signature

Re: FreeBSD as VirtualBox guest panics when starting VBoxService

2017-05-24 Thread Patrick M. Hausen 
Hello,

> Am 23.05.2017 um 23:10 schrieb 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.

My box?

> Are you not experiencing this?

Of course not. Vagrant 1.9.5, Virtualbox 5.1.22, Mac OS.
We are using this box daily ...

Patrick


signature.asc
Description: Message signed with OpenPGP

Re: No TCP-MD5 in 11.1-PRERELEASE.

2017-05-24 Thread Andrey V. Elsukov 
On 23.05.2017 23:12, Zaphod Beeblebrox wrote:
> I just added a setkey for the reverse, and connections still do not happen.

Look at the `netstat -sp tcp | grep sign' output.
Also there are some debug messages can be generated by TCP syncache
code, you can see them in the syslog's logs under LOG_DEBUG level.
Also you can use tcpdump with -M flag to validate MD5 signatures.

-- 
WBR, Andrey V. Elsukov



signature.asc
Description: OpenPGP digital signature