Re: ThinkPad: reboots after successful shutdown -p

[Kostya Berger via freebsd-current]

 I had it and filed a bug report. It only happens in UEFI loader and that only 
on one of my machines, but not the other.

With kindest regards,
Kostya Berger



 On Wednesday, 17 March 2021, 19:38:57 GMT+3, Unbound 
 wrote:  
 
 On 2021-03-17 00:01, Xin Li via freebsd-current wrote:
> On 3/16/21 9:45 PM, Warner Losh wrote:
>> 
>> 
>> On Tue, Mar 16, 2021 at 10:18 PM Xin Li > > wrote:
>> 
>>    On 11/17/19 23:14, Xin Li wrote:
>>    > Hi,
>>    >
>>    > I recently noticed that if I do a 'shutdown -p' from -CURRENT, the
>>    > system would shut down and seemingly powered off, then it would
>>    restart
>>    > after about 5-10 seconds.
>>    >
>>    > Is this a known issue?  Arguably this is not necessarily a FreeBSD
>>    > issue, but it seems that the Windows 10 installation doesn't have the
>>    > problem, so I guess there might be some difference between our and
>>    > Windows's shutdown sequence.
>> 
>>    I've found a workaround for this, for the record, setting
>>    hw.efi.poweroff=0 would make the laptop to correctly shutdown.
>> 
>>    However I don't see anything wrong with sys/dev/efidev/efirt.c's
>>    implementation of EFI shutdown; it appears to be essentially the same 
>> as
>>    implemented in command_poweroff() in stand/efi/loader/main.c, but
>>    'poweroff' would work just fine in loader.efi.
>> 
>>    Can someone familiar with the code shed me some light here? :-)
>> 
>>    It looks like what Linux did was to prefer ACPI S5, unless it's not
>>    available or the system have HW_REDUCED flag in FADT, so if we do
>>    something similar it would fix the issue for me, but according to
>>    bugs.freebsd.org/233998  that's not
>>    the case for at least Conor's system
>>    (_S5 appears to be in the ACPI dump), so I think it's something else...
>> 
>> 
>> For me, interrupt storm on shutdown has been the causes of issues like
>> this...
>> 
>> Any chance you can eliminate that as a possibility?
> 
> Hmm, that's a good question -- is there a way to tell after the screen
> was turned off?
> 
> Before the screen was turned off, there doesn't appear to be interrupt
> storm.  The system was performing a typical FreeBSD shutdown procedure:
> All buffers synced, showed uptime, destroyed GELI devices, spin down the
> SATA devices, shutdown the cardreader (rtsx0), detached all USB devices
> (hidraw1, hidbus, usbhid1, ubt0, uhub0), screen turned slightly red for
> a very brief period (maybe side effect of turning off the backlight),
> then goes off.
> 
> I think most of FreeBSD drivers would turn off interrupt from the device
> before detaching, but I haven't looked into all of my devices; but from
> what I have seen on screen (captured a 60fps video and can share if that
> helps), there doesn't appear to be an interrupt storm before that.
> 
> Cheers,
FWIW this also happened to me a few weeks ago after a fresh install.
I've since wiped the disk and repurposed the hardware. So I can't now
reproduce it. But it wasn't a laptop. So it's not isolated to them.
Sorry I can't offer anything more. I just wanted to mention this to
indicate that it's not a _too_ terribly isolated case. It was Intel
CPU/graphics. In case that says anything to anyone. If it matters,
I can get/offer more info on the hardware.

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

Re: ThinkPad: reboots after successful shutdown -p

[Unbound]

On 2021-03-17 00:01, Xin Li via freebsd-current wrote:

On 3/16/21 9:45 PM, Warner Losh wrote:



On Tue, Mar 16, 2021 at 10:18 PM Xin Li mailto:delp...@freebsd.org>> wrote:

On 11/17/19 23:14, Xin Li wrote:
> Hi,
>
> I recently noticed that if I do a 'shutdown -p' from -CURRENT, the
> system would shut down and seemingly powered off, then it would
restart
> after about 5-10 seconds.
>
> Is this a known issue?  Arguably this is not necessarily a FreeBSD
> issue, but it seems that the Windows 10 installation doesn't have the
> problem, so I guess there might be some difference between our and
> Windows's shutdown sequence.

I've found a workaround for this, for the record, setting
hw.efi.poweroff=0 would make the laptop to correctly shutdown.

However I don't see anything wrong with sys/dev/efidev/efirt.c's
implementation of EFI shutdown; it appears to be essentially the same 
as

implemented in command_poweroff() in stand/efi/loader/main.c, but
'poweroff' would work just fine in loader.efi.

Can someone familiar with the code shed me some light here? :-)

It looks like what Linux did was to prefer ACPI S5, unless it's not
available or the system have HW_REDUCED flag in FADT, so if we do
something similar it would fix the issue for me, but according to
bugs.freebsd.org/233998  that's not
the case for at least Conor's system
(_S5 appears to be in the ACPI dump), so I think it's something else...


For me, interrupt storm on shutdown has been the causes of issues like
this...

Any chance you can eliminate that as a possibility?


Hmm, that's a good question -- is there a way to tell after the screen
was turned off?

Before the screen was turned off, there doesn't appear to be interrupt
storm.  The system was performing a typical FreeBSD shutdown procedure:
All buffers synced, showed uptime, destroyed GELI devices, spin down the
SATA devices, shutdown the cardreader (rtsx0), detached all USB devices
(hidraw1, hidbus, usbhid1, ubt0, uhub0), screen turned slightly red for
a very brief period (maybe side effect of turning off the backlight),
then goes off.

I think most of FreeBSD drivers would turn off interrupt from the device
before detaching, but I haven't looked into all of my devices; but from
what I have seen on screen (captured a 60fps video and can share if that
helps), there doesn't appear to be an interrupt storm before that.

Cheers,

FWIW this also happened to me a few weeks ago after a fresh install.
I've since wiped the disk and repurposed the hardware. So I can't now
reproduce it. But it wasn't a laptop. So it's not isolated to them.
Sorry I can't offer anything more. I just wanted to mention this to
indicate that it's not a _too_ terribly isolated case. It was Intel
CPU/graphics. In case that says anything to anyone. If it matters,
I can get/offer more info on the hardware.

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

Re: ThinkPad: reboots after successful shutdown -p

[Chris]

On 2021-03-17 00:01, Xin Li via freebsd-current wrote:

On 3/16/21 9:45 PM, Warner Losh wrote:



On Tue, Mar 16, 2021 at 10:18 PM Xin Li mailto:delp...@freebsd.org>> wrote:

On 11/17/19 23:14, Xin Li wrote:
> Hi,
>
> I recently noticed that if I do a 'shutdown -p' from -CURRENT, the
> system would shut down and seemingly powered off, then it would
restart
> after about 5-10 seconds.
>
> Is this a known issue?  Arguably this is not necessarily a FreeBSD
> issue, but it seems that the Windows 10 installation doesn't have the
> problem, so I guess there might be some difference between our and
> Windows's shutdown sequence.

I've found a workaround for this, for the record, setting
hw.efi.poweroff=0 would make the laptop to correctly shutdown.

However I don't see anything wrong with sys/dev/efidev/efirt.c's
implementation of EFI shutdown; it appears to be essentially the same 
as

implemented in command_poweroff() in stand/efi/loader/main.c, but
'poweroff' would work just fine in loader.efi.

Can someone familiar with the code shed me some light here? :-)

It looks like what Linux did was to prefer ACPI S5, unless it's not
available or the system have HW_REDUCED flag in FADT, so if we do
something similar it would fix the issue for me, but according to
bugs.freebsd.org/233998  that's not
the case for at least Conor's system
(_S5 appears to be in the ACPI dump), so I think it's something else...


For me, interrupt storm on shutdown has been the causes of issues like
this...

Any chance you can eliminate that as a possibility?


Hmm, that's a good question -- is there a way to tell after the screen
was turned off?

Before the screen was turned off, there doesn't appear to be interrupt
storm.  The system was performing a typical FreeBSD shutdown procedure:
All buffers synced, showed uptime, destroyed GELI devices, spin down the
SATA devices, shutdown the cardreader (rtsx0), detached all USB devices
(hidraw1, hidbus, usbhid1, ubt0, uhub0), screen turned slightly red for
a very brief period (maybe side effect of turning off the backlight),
then goes off.

I think most of FreeBSD drivers would turn off interrupt from the device
before detaching, but I haven't looked into all of my devices; but from
what I have seen on screen (captured a 60fps video and can share if that
helps), there doesn't appear to be an interrupt storm before that.

Cheers,

FWIW this also happened to me a few weeks ago after a fresh install.
I've since wiped the disk and repurposed the hardware. So I can't now
reproduce it. But it wasn't a laptop. So it's not isolated to them.
Sorry I can't offer anything more. I just wanted to mention this to
indicate that it's not a _too_ terribly isolated case. It was Intel
CPU/graphics. In case that says anything to anyone. If it matters,
I can get/offer more info on the hardware.

--Chris

P.S. Sorry about my last response. My MUA seems to be acting up this AM. :/
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: ThinkPad: reboots after successful shutdown -p

[Rob Belics]

> Hi,
>
> I recently noticed that if I do a 'shutdown -p' from -CURRENT, the
> system would shut down and seemingly powered off, then it would restart
> after about 5-10 seconds.
>
> Is this a known issue?  Arguably this is not necessarily a FreeBSD
> issue, but it seems that the Windows 10 installation doesn't have the
> problem, so I guess there might be some difference between our and
> Windows's shutdown sequence.

Check to see if your ThinkPad has Wake On Lan set on. This is what happens
to me when I forget to turn that off.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: ThinkPad: reboots after successful shutdown -p

[Tomoaki AOKI]

On Wed, 17 Mar 2021 00:01:49 -0700
Xin Li via freebsd-current  wrote:

> 
> 
> On 3/16/21 9:45 PM, Warner Losh wrote:
> > 
> > 
> > On Tue, Mar 16, 2021 at 10:18 PM Xin Li  > > wrote:
> > 
> > On 11/17/19 23:14, Xin Li wrote:
> > > Hi,
> > >
> > > I recently noticed that if I do a 'shutdown -p' from -CURRENT, the
> > > system would shut down and seemingly powered off, then it would
> > restart
> > > after about 5-10 seconds.
> > >
> > > Is this a known issue?〓 Arguably this is not necessarily a FreeBSD
> > > issue, but it seems that the Windows 10 installation doesn't have the
> > > problem, so I guess there might be some difference between our and
> > > Windows's shutdown sequence.
> > 
> > I've found a workaround for this, for the record, setting
> > hw.efi.poweroff=0 would make the laptop to correctly shutdown.
> > 
> > However I don't see anything wrong with sys/dev/efidev/efirt.c's
> > implementation of EFI shutdown; it appears to be essentially the same as
> > implemented in command_poweroff() in stand/efi/loader/main.c, but
> > 'poweroff' would work just fine in loader.efi.
> > 
> > Can someone familiar with the code shed me some light here? :-)
> > 
> > It looks like what Linux did was to prefer ACPI S5, unless it's not
> > available or the system have HW_REDUCED flag in FADT, so if we do
> > something similar it would fix the issue for me, but according to
> > bugs.freebsd.org/233998  that's not
> > the case for at least Conor's system
> > (_S5 appears to be in the ACPI dump), so I think it's something else...
> > 
> > 
> > For me, interrupt storm on shutdown has been the causes of issues like
> > this...
> > 
> > Any chance you can eliminate that as a possibility?
> 
> Hmm, that's a good question -- is there a way to tell after the screen
> was turned off?
> 
> Before the screen was turned off, there doesn't appear to be interrupt
> storm.  The system was performing a typical FreeBSD shutdown procedure:
> All buffers synced, showed uptime, destroyed GELI devices, spin down the
> SATA devices, shutdown the cardreader (rtsx0), detached all USB devices
> (hidraw1, hidbus, usbhid1, ubt0, uhub0), screen turned slightly red for
> a very brief period (maybe side effect of turning off the backlight),
> then goes off.
> 
> I think most of FreeBSD drivers would turn off interrupt from the device
> before detaching, but I haven't looked into all of my devices; but from
> what I have seen on screen (captured a 60fps video and can share if that
> helps), there doesn't appear to be an interrupt storm before that.
> 
> Cheers,
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> 

Hi.

Unclear if it's related or not, but my ThinkPad P52 often refuses
keyboard input on loader.efi and boot1.efi (boot1.efi as bootx64.efi).

In such cases, I need (typically) one or more power cycle to go into
single user mode with updated kernel (for installword).

Also experienced unintended auto-reboot-after-poweroff on P52, but only
once, currently.

I suspect some hardware with no FreeBSD driver can trigger interrupt
storm because of the lack of proper initialization and detach.

IIRC, my old ThinkPad T420 didn't have the problem.
So possibly UEFI firmware issue.

Regards.

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

Re: ThinkPad: reboots after successful shutdown -p

[Xin Li via freebsd-current]

On 3/16/21 9:45 PM, Warner Losh wrote:
> 
> 
> On Tue, Mar 16, 2021 at 10:18 PM Xin Li  > wrote:
> 
> On 11/17/19 23:14, Xin Li wrote:
> > Hi,
> >
> > I recently noticed that if I do a 'shutdown -p' from -CURRENT, the
> > system would shut down and seemingly powered off, then it would
> restart
> > after about 5-10 seconds.
> >
> > Is this a known issue?  Arguably this is not necessarily a FreeBSD
> > issue, but it seems that the Windows 10 installation doesn't have the
> > problem, so I guess there might be some difference between our and
> > Windows's shutdown sequence.
> 
> I've found a workaround for this, for the record, setting
> hw.efi.poweroff=0 would make the laptop to correctly shutdown.
> 
> However I don't see anything wrong with sys/dev/efidev/efirt.c's
> implementation of EFI shutdown; it appears to be essentially the same as
> implemented in command_poweroff() in stand/efi/loader/main.c, but
> 'poweroff' would work just fine in loader.efi.
> 
> Can someone familiar with the code shed me some light here? :-)
> 
> It looks like what Linux did was to prefer ACPI S5, unless it's not
> available or the system have HW_REDUCED flag in FADT, so if we do
> something similar it would fix the issue for me, but according to
> bugs.freebsd.org/233998  that's not
> the case for at least Conor's system
> (_S5 appears to be in the ACPI dump), so I think it's something else...
> 
> 
> For me, interrupt storm on shutdown has been the causes of issues like
> this...
> 
> Any chance you can eliminate that as a possibility?

Hmm, that's a good question -- is there a way to tell after the screen
was turned off?

Before the screen was turned off, there doesn't appear to be interrupt
storm.  The system was performing a typical FreeBSD shutdown procedure:
All buffers synced, showed uptime, destroyed GELI devices, spin down the
SATA devices, shutdown the cardreader (rtsx0), detached all USB devices
(hidraw1, hidbus, usbhid1, ubt0, uhub0), screen turned slightly red for
a very brief period (maybe side effect of turning off the backlight),
then goes off.

I think most of FreeBSD drivers would turn off interrupt from the device
before detaching, but I haven't looked into all of my devices; but from
what I have seen on screen (captured a 60fps video and can share if that
helps), there doesn't appear to be an interrupt storm before that.

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

Re: ThinkPad: reboots after successful shutdown -p

[Warner Losh]

On Tue, Mar 16, 2021 at 10:18 PM Xin Li  wrote:

> On 11/17/19 23:14, Xin Li wrote:
> > Hi,
> >
> > I recently noticed that if I do a 'shutdown -p' from -CURRENT, the
> > system would shut down and seemingly powered off, then it would restart
> > after about 5-10 seconds.
> >
> > Is this a known issue?  Arguably this is not necessarily a FreeBSD
> > issue, but it seems that the Windows 10 installation doesn't have the
> > problem, so I guess there might be some difference between our and
> > Windows's shutdown sequence.
>
> I've found a workaround for this, for the record, setting
> hw.efi.poweroff=0 would make the laptop to correctly shutdown.
>
> However I don't see anything wrong with sys/dev/efidev/efirt.c's
> implementation of EFI shutdown; it appears to be essentially the same as
> implemented in command_poweroff() in stand/efi/loader/main.c, but
> 'poweroff' would work just fine in loader.efi.
>
> Can someone familiar with the code shed me some light here? :-)
>
> It looks like what Linux did was to prefer ACPI S5, unless it's not
> available or the system have HW_REDUCED flag in FADT, so if we do
> something similar it would fix the issue for me, but according to
> bugs.freebsd.org/233998 that's not the case for at least Conor's system
> (_S5 appears to be in the ACPI dump), so I think it's something else...
>

For me, interrupt storm on shutdown has been the causes of issues like
this...

Any chance you can eliminate that as a possibility?

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

Re: ThinkPad: reboots after successful shutdown -p

[Xin Li]

On 11/17/19 23:14, Xin Li wrote:
> Hi,
> 
> I recently noticed that if I do a 'shutdown -p' from -CURRENT, the
> system would shut down and seemingly powered off, then it would restart
> after about 5-10 seconds.
> 
> Is this a known issue?  Arguably this is not necessarily a FreeBSD
> issue, but it seems that the Windows 10 installation doesn't have the
> problem, so I guess there might be some difference between our and
> Windows's shutdown sequence.

I've found a workaround for this, for the record, setting
hw.efi.poweroff=0 would make the laptop to correctly shutdown.

However I don't see anything wrong with sys/dev/efidev/efirt.c's
implementation of EFI shutdown; it appears to be essentially the same as
implemented in command_poweroff() in stand/efi/loader/main.c, but
'poweroff' would work just fine in loader.efi.

Can someone familiar with the code shed me some light here? :-)

It looks like what Linux did was to prefer ACPI S5, unless it's not
available or the system have HW_REDUCED flag in FADT, so if we do
something similar it would fix the issue for me, but according to
bugs.freebsd.org/233998 that's not the case for at least Conor's system
(_S5 appears to be in the ACPI dump), so I think it's something else...

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

Re: ThinkPad: reboots after successful shutdown -p

[Tom Jones]

On Mon, Nov 18, 2019 at 11:47:18AM -0800, Oleksandr Tymoshenko wrote:
> Bjoern A. Zeeb (bzeeb-li...@lists.zabbadoz.net) wrote:
> > On 18 Nov 2019, at 7:14, Xin Li wrote:
> > 
> > > Hi,
> > >
> > > I recently noticed that if I do a 'shutdown -p' from -CURRENT, the
> > > system would shut down and seemingly powered off, then it would 
> > > restart
> > > after about 5-10 seconds.
> > 
> > Interesting. I have the opposite problem that a reboot does a shutdown 
> > but never resets (also no reset from ddb>).  I’ve seen this on the 
> > X270 and the T480.
> 
> I had this issue on my Thinkpad too. The "solution" was to disable
> bluetooth chip in BIOS. I didn't try to find the root cause of this
> behavior.

There was a related bluetooth update in September after which my x270
was able to reboot. You might want to reenable and try again

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

Re: ThinkPad: reboots after successful shutdown -p

[Oleksandr Tymoshenko]

Bjoern A. Zeeb (bzeeb-li...@lists.zabbadoz.net) wrote:
> On 18 Nov 2019, at 7:14, Xin Li wrote:
> 
> > Hi,
> >
> > I recently noticed that if I do a 'shutdown -p' from -CURRENT, the
> > system would shut down and seemingly powered off, then it would 
> > restart
> > after about 5-10 seconds.
> 
> Interesting. I have the opposite problem that a reboot does a shutdown 
> but never resets (also no reset from ddb>).  I’ve seen this on the 
> X270 and the T480.

I had this issue on my Thinkpad too. The "solution" was to disable
bluetooth chip in BIOS. I didn't try to find the root cause of this
behavior.

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

Re: ThinkPad: reboots after successful shutdown -p

[Gary Jennejohn]

On Mon, 18 Nov 2019 13:04:48 +
"Bjoern A. Zeeb"  wrote:

> On 18 Nov 2019, at 7:14, Xin Li wrote:
> 
> > Hi,
> >
> > I recently noticed that if I do a 'shutdown -p' from -CURRENT, the
> > system would shut down and seemingly powered off, then it would 
> > restart
> > after about 5-10 seconds.  
> 
> Interesting. I have the opposite problem that a reboot does a shutdown 
> but never resets (also no reset from ddb>).  I;ve seen this on the 
> X270 and the T480.
> 

The x270 I have works correctly with both "shutdown -r" and "shutdown
-p."  It's running this version of HEAD:
FreeBSD-13.0-CURRENT-amd64-20191031-r354207-memstick.img

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

Re: ThinkPad: reboots after successful shutdown -p

[David Wolfskill]

On Sun, Nov 17, 2019 at 11:14:02PM -0800, Xin Li wrote:
> Hi,
> 
> I recently noticed that if I do a 'shutdown -p' from -CURRENT, the
> system would shut down and seemingly powered off, then it would restart
> after about 5-10 seconds.
> 
> Is this a known issue?  Arguably this is not necessarily a FreeBSD
> issue, but it seems that the Windows 10 installation doesn't have the
> problem, so I guess there might be some difference between our and
> Windows's shutdown sequence.
> 
> Cheers,

I do not see the above behavior, either with my laptop (a Dell Precision
M4800) or my build machine (a Dell mini-tower, originally purchased at
Costco).

In each case, I have been tracking head daily; I have been powering
the build machine down since I started doing this well over a decade ago
(and prior to the current instantiation of the build machine), and I
started powering the laptop down after smoke-testing head about a year
ago or so (I think).

For this morning, I left the laptop powered off for just over a minute:
it stayed powered off until I pressed the power button.  This morning's
update was from r354785 to r354807 (for both machines -- I keep them in
sync).

Information on update history for both machines may be found at
http://www.catwhisker.org/~david/FreeBSD/history/ -- in case that's of
use or interest.

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
Saying "...the whistleblower because of that should be revealed," (as
did Donald Trump) is encouraging (if not leading) a lynch mob, and
folks who do that should never hold office.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

Re: ThinkPad: reboots after successful shutdown -p

[Bjoern A. Zeeb]

On 18 Nov 2019, at 7:14, Xin Li wrote:


Hi,

I recently noticed that if I do a 'shutdown -p' from -CURRENT, the
system would shut down and seemingly powered off, then it would 
restart

after about 5-10 seconds.


Interesting. I have the opposite problem that a reboot does a shutdown 
but never resets (also no reset from ddb>).  I’ve seen this on the 
X270 and the T480.


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

ThinkPad: reboots after successful shutdown -p

[Xin Li]

Hi,

I recently noticed that if I do a 'shutdown -p' from -CURRENT, the
system would shut down and seemingly powered off, then it would restart
after about 5-10 seconds.

Is this a known issue?  Arguably this is not necessarily a FreeBSD
issue, but it seems that the Windows 10 installation doesn't have the
problem, so I guess there might be some difference between our and
Windows's shutdown sequence.

Cheers,



signature.asc
Description: OpenPGP digital signature