Re: Updated to 13-STABLE in VirtualBox; on shutdown stuck after uhub[01] being detached

2021-04-29 Thread Antony Uspensky

On Wed, 28 Apr 2021, parv/freebsd wrote:


Solved the issue via ...

 % sysctl hw.efi.poweroff=0
... after that shudown went on as expected. Got that from  ...

https://forums.freebsd.org/threads/freebsd-13-does-not-shut-down-my-laptop.79853/


Well, this also solved my problem described in a message to this list:

Date: Thu, 1 Apr 2021 18:58:01 +0300 (MSK)
From: Antony Uspensky 
To: freebsd-stable@freebsd.org
Subject: ACPI poweroff is not working on 13.0
Message-ID: 

I was wrong: it was EFI poweroff that did not work, not ACPI one.
I was too lazy to do a bisection, now I am OK.
Thank you for the tip!

Seems, this problem (non-working shutdown in EFI environment) is a POLA 
violation in 13.0. 
A.

___
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: Updated to 13-STABLE in VirtualBox; on shutdown stuck after uhub[01] being detached

2021-04-28 Thread parv/freebsd
(Changed my email address to the one I used to subscribe to the mailing
list.)

On Wed, Apr 28, 2021 at 10:05 AM Guido Falsi wrote:

Hi,


On 28/04/21 00:12, parv wrote:
> > I had updated FreeBSD, in VirtualBox 5.22 on Windows with EFI, from
> > 12-STABLE
> > to 13-STABLE; upgraded the ZFS pools & the EFI boot loader. Currently
> > testing with 13 GENERIC kernel.
>
> You mean you enabled EFI inside virtualbox? Why do you need that?


For testing if FreeBSD can boot with EFI (with ZFS-on-root) ... one day I
may just install the thing directly on a disk, outside of a virtual machine
... one day!



> EFI
> support in VirtualBox is experimental and is available for OSes unable
> to boot without EFI. FreeBSD is perfectly able to boot in virtualbox
> without EFI so no need for it.
>

I am aware.



> > Now on shutdown, "shutdown -p now" (in single user mode, after manually
> > unmounting
> > ZFS datasets [...] the shutting down process gets stuck,
> > and CPU use jumps to 80%
>
...

> > In the end I chose "Power Off" from VirutalBox menu. "Reset" reboots the
> > machine.
> > None of these have any effect ...
> >- Send the shutdown signal
> >- ACPI Shutdown
> >
> > Help please.
>

Solved the issue via ...

  % sysctl hw.efi.poweroff=0
... after that shudown went on as expected. Got that from  ...


https://forums.freebsd.org/threads/freebsd-13-does-not-shut-down-my-laptop.79853/


NOt sure even which further information to ask about this, but to be
> sure I understand correctly, FreeBSD is the guest here, correct?


Yes, FreeBSD is the guest on Windows 10 host.

- parv
___
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: Updated to 13-STABLE in VirtualBox; on shutdown stuck after uhub[01] being detached

2021-04-28 Thread Guido Falsi via freebsd-stable

On 28/04/21 00:12, parv wrote:

Hi there,

I had updated FreeBSD, in VirtualBox 5.22 on Windows with EFI, from
12-STABLE
to 13-STABLE; upgraded the ZFS pools & the EFI boot loader. Currently
testing with 13 GENERIC kernel.


You mean you enabled EFI inside virtualbox? Why do you need that? EFI 
support in VirtualBox is experimental and is available for OSes unable 
to boot without EFI. FreeBSD is perfectly able to boot in virtualbox 
without EFI so no need for it.


Now I understand reconfiguring the VM to not use EFI can be annoying, 
but you should really verify if the problem goes away without EFI.


Also can you try installing another FreeBSD VM and verify the problem 
happens for that one too? This could help understand if the problem is 
with virtualization or specific to the VM.




Now on shutdown, "shutdown -p now" (in single user mode, after manually
unmounting
ZFS datasets via "zfs unmount -a"), the shutting down process gets stuck,
and
CPU use jumps to 80% (Intel i5 6300U, 3 CPUs given to VM, of Thinkpad
X260). Last
few lines are ...

...
All buffers synced.
Uptime: 
uhub0: detached
uhub1: detached


In the end I chose "Power Off" from VirutalBox menu. "Reset" reboots the
machine.
None of these have any effect ...
   - Send the shutdown signal
   - ACPI Shutdown

Help please.


NOt sure even which further information to ask about this, but to be 
sure I understand correctly, FreeBSD is the guest here, correct?


--
Guido Falsi 
___
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"


Updated to 13-STABLE in VirtualBox; on shutdown stuck after uhub[01] being detached

2021-04-28 Thread parv
Hi there,

I had updated FreeBSD, in VirtualBox 5.22 on Windows with EFI, from
12-STABLE
to 13-STABLE; upgraded the ZFS pools & the EFI boot loader. Currently
testing with 13 GENERIC kernel.

Now on shutdown, "shutdown -p now" (in single user mode, after manually
unmounting
ZFS datasets via "zfs unmount -a"), the shutting down process gets stuck,
and
CPU use jumps to 80% (Intel i5 6300U, 3 CPUs given to VM, of Thinkpad
X260). Last
few lines are ...

...
All buffers synced.
Uptime: 
uhub0: detached
uhub1: detached


In the end I chose "Power Off" from VirutalBox menu. "Reset" reboots the
machine.
None of these have any effect ...
  - Send the shutdown signal
  - ACPI Shutdown

Help please.


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