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

[Konstantin Belousov]

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.
___
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"

[Bug 213903] Kernel crashes from turnstile_broadcast (/usr/src/sys/kern/subr_turnstile.c:837)

[bugzilla-noreply]

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

Kubilay Kocak  changed:

   What|Removed |Added

  Flags|mfc-stable10-,  |mfc-stable10+,
   |mfc-stable11-   |mfc-stable11+

--- Comment #52 from Kubilay Kocak  ---
Correctly (+, not -) document merge completion

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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"

[Bug 213903] Kernel crashes from turnstile_broadcast (/usr/src/sys/kern/subr_turnstile.c:837)

[bugzilla-noreply]

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

Mateusz Guzik  changed:

   What|Removed |Added

  Flags|mfc-stable10?,  |mfc-stable10-,
   |mfc-stable11?   |mfc-stable11-
 Status|Open|In Progress

--- Comment #51 from Mateusz Guzik  ---
The change was committed to stable/10. To the best of my knowledge all branches
with the original patch (head, stable/11, 11.1 and stable/10) have the issue
resolved.

Thanks everyone for reporting and testing.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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"

[Bug 213903] Kernel crashes from turnstile_broadcast (/usr/src/sys/kern/subr_turnstile.c:837)

[bugzilla-noreply]

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

--- Comment #50 from commit-h...@freebsd.org ---
A commit references this bug:

Author: mjg
Date: Tue Jul 11 03:45:48 UTC 2017
New revision: 320885
URL: https://svnweb.freebsd.org/changeset/base/320885

Log:
  Remove waiters check from the inline rw wunlock routine.

  This is a direct commit to stable/10.

  r310979 is a merge of depessimisation of locking primitives.
  The important part was getting rid of an attempt to grab the lock in the
  slow path immediately after the fast path failed. In addition to that
  temporary checks were added before all atomic ops. They have no impact on
  semantic nor correctness, they only avoid an atomic operation which is
  likely to fail.

  After the addition of atomic_fcmpset and further changes said checks
  became pessimal and got removed. This may get merged to stable/10.

  Reports started showing up about a crash in all branches having extra
  checks. The codepath is:
  .. -> vm_map_delete -> __rw_wunlock_hard -> turnstile_broadcast

  The kernel crashed trying to wake up nonexistent waiters. The lock value
  as found in the vmcore matches the panicking thread, so in particular
  there was no waiters bit set. The bit can only be cleared by the current
  owner.

  A debug patch was provided, which reportedly had a side effect of getting
  rid of the issue.

  Also one of the reporters said that reverting the patch which adds the
  extra checks makes the crash go away.

  It was also reported that head with the fcmpset changes (explicit checks
  removed) also stops crashing.

  Finally, one user tested crashing stable/10 variant with just the rw
  wunlock check removed.

  The common case in all but one reports was an Intel Atom cpu. Claiming
  a cpu bug at this point is bold and I'm going to refrain from it, but
  right now apart from cpu-specific optimisation made by the compiler on
  custom kernel compiles I don't see how this can be a software bug.

  This will have to be investigated more.

  Meanwhile, restore rw wunlock to pre-r310979 state.

  PR:   213903

Changes:
  stable/10/sys/sys/rwlock.h

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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"

[Bug 213903] Kernel crashes from turnstile_broadcast (/usr/src/sys/kern/subr_turnstile.c:837)

[bugzilla-noreply]

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

--- Comment #49 from Ben Woods  ---
I am running FreeBSD 12-CURRENT r319025 without any patches and can confirm the
crashes do not occur for me anymore on my FreeNAS mini. Thanks for your help
with this!

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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: [SOLVED] Re: Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice

[Mark Johnston]

On Mon, Jul 10, 2017 at 09:47:50PM +0200, José G. Juanino wrote:
> El Monday 10 de July a las 21:24:41 CEST, José G. Juanino escribió:
> >El Sunday 09 de July a las 23:48:29 CEST, David Boyd escribió:
> >>With latest VM-IMAGE (vmdk) for 11.1-RC2 system panics.  I haven't 
> >>been able to process the panic completely, but the backtrace looks 
> >>mysteriously similar to those provided with PR219146.
> >>
> >>
> >>Initially, the VM-IMAGE booted just fine.  The VM-IMAGE is then 
> >>configured as a VirtualBox client.  The panic occurs on subsequent 
> >>reboots when attempting to start vboxservice.
> >>
> >>
> >>Additionally, during the custom configuration process, lsof hangs 
> >>for more than 2 minutes each time that it is invoked.
> >>
> >>
> >>Please let me know exactly what information is needed to correct 
> >>this problem.  I will be able to provide that information no later 
> >>than Tuesday morning.
> >>
> >
> >Hi, I am also suffering this panic.
> >
> >I use everyday my Windows 7 host Virtualbox with a FreeBSD guest. I 
> >upgraded from 11.0 -> 11.1-BETA1 -> 11.1-BETA2 -> 11.1-RC1 with no 
> >issues.
> >
> >But after to upgrade to 11.1-RC2, the system panics just after to 
> >start vboxservice. I have disabled the service at boot in 
> >/etc/rc.conf, but it does not help: the system crashes just after 
> >"service vboxservice start" command.
> >
> >You can get a full crash dump here:
> >
> >https://pastebin.com/MkxS9GZn
> >
> >At this moment, I am going to rebuild the virtualbox-ose-additions 
> >port (running 11.1-RC2) and I will let you know if there is some 
> >difference.
> 
> I confirm that after rebuild virtualbox-ose-additions port, the panic 
> goes away. Regards.

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.
___
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"

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

[José G . Juanino]

El Monday 10 de July a las 21:24:41 CEST, José G. Juanino escribió:

El Sunday 09 de July a las 23:48:29 CEST, David Boyd escribió:
With latest VM-IMAGE (vmdk) for 11.1-RC2 system panics.  I haven't 
been able to process the panic completely, but the backtrace looks 
mysteriously similar to those provided with PR219146.



Initially, the VM-IMAGE booted just fine.  The VM-IMAGE is then 
configured as a VirtualBox client.  The panic occurs on subsequent 
reboots when attempting to start vboxservice.



Additionally, during the custom configuration process, lsof hangs 
for more than 2 minutes each time that it is invoked.



Please let me know exactly what information is needed to correct 
this problem.  I will be able to provide that information no later 
than Tuesday morning.




Hi, I am also suffering this panic.

I use everyday my Windows 7 host Virtualbox with a FreeBSD guest. I 
upgraded from 11.0 -> 11.1-BETA1 -> 11.1-BETA2 -> 11.1-RC1 with no 
issues.


But after to upgrade to 11.1-RC2, the system panics just after to 
start vboxservice. I have disabled the service at boot in 
/etc/rc.conf, but it does not help: the system crashes just after 
"service vboxservice start" command.


You can get a full crash dump here:

https://pastebin.com/MkxS9GZn

At this moment, I am going to rebuild the virtualbox-ose-additions 
port (running 11.1-RC2) and I will let you know if there is some 
difference.


I confirm that after rebuild virtualbox-ose-additions port, the panic 
goes away. Regards.



--
José G. Juanino
___
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: Panic with FreeBSD 11.0-RC2 VM-IMAGE when starting vboxservice

[José G . Juanino]

El Sunday 09 de July a las 23:48:29 CEST, David Boyd escribió:
With latest VM-IMAGE (vmdk) for 11.1-RC2 system panics.  I haven't been 
able to process the panic completely, but the backtrace looks 
mysteriously similar to those provided with PR219146.



Initially, the VM-IMAGE booted just fine.  The VM-IMAGE is then 
configured as a VirtualBox client.  The panic occurs on subsequent 
reboots when attempting to start vboxservice.



Additionally, during the custom configuration process, lsof hangs for 
more than 2 minutes each time that it is invoked.



Please let me know exactly what information is needed to correct this 
problem.  I will be able to provide that information no later than 
Tuesday morning.




Hi, I am also suffering this panic.

I use everyday my Windows 7 host Virtualbox with a FreeBSD guest. I 
upgraded from 11.0 -> 11.1-BETA1 -> 11.1-BETA2 -> 11.1-RC1 with no 
issues.


But after to upgrade to 11.1-RC2, the system panics just after to start 
vboxservice. I have disabled the service at boot in /etc/rc.conf, but it 
does not help: the system crashes just after "service vboxservice start" 
command.


You can get a full crash dump here:

https://pastebin.com/MkxS9GZn

At this moment, I am going to rebuild the virtualbox-ose-additions port 
(running 11.1-RC2) and I will let you know if there is some difference. 


Regards


--
José G. Juanino
___
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"

[Bug 213903] Kernel crashes from turnstile_broadcast (/usr/src/sys/kern/subr_turnstile.c:837)

[bugzilla-noreply]

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

--- Comment #48 from Mateusz Guzik  ---
Thanks for testing. I'll commit the patch later today with few other
modifications.

That said, I expect the problem to be gone on head starting with r313270 and on
stable/11 starting with r315377, which also means it is included in all 11.1
builds.

That said, if someone running into the crash on one of the above could confirm
the newest version of their relevant branch makes the problem go away, that
would be nice.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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"

[Bug 213903] Kernel crashes from turnstile_broadcast (/usr/src/sys/kern/subr_turnstile.c:837)

[bugzilla-noreply]

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

--- Comment #47 from Cassiano Peixoto  ---
(In reply to Mateusz Guzik from comment #43)
Dear Mateusz,

I'm quite sure this patch has fixed the issue on 10-STABLE. My server is
running 6 days without reboot. Please go ahead and commit it. Thank you for
your support.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
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"