Re: nvme timeout issues with hardware and bhyve vm's

Thanks. It may be worth checking the temp periodically and warning the user in case it is too high (70ºC+ or something). Even for devices that allow internal throttling, a user might wish to know whether the device neads a (better) heatsink. > On Dec 7, 2023, at 5:02 PM, Maxim Sobolev wrote:

Re: nvme timeout issues with hardware and bhyve vm's

How quickly it heats up depends on lots of factors. Usually those devices burn some 3-7 watts per stick at 100% load, so maybe this would give you some idea. At least some of them support several toggleable performance modes, which use throttling internally to limit power consumption to a certain l

Re: nvme timeout issues with hardware and bhyve vm's

On Thu, Dec 7, 2023 at 2:39 PM Pete Wright wrote: ... > Hi Warner, just resurfacing this thread because I've had a few lockups > on my workstation running 14.0-STABLE. I was able to capture a photo of > the hang and this seems to be the most important line: > > nvme0: Resetting controller due to

Re: nvme timeout issues with hardware and bhyve vm's

On Dec 7, 2023, at 3:59 PM, Warner Losh wrote: > > > *Overheating caused hang of NVMe controller or PCI bridge on SSD, or > > Yes. Most drive's firmware when it overheats resets. There might be something > that the pci code can do when this happens to retrain the link, reprogram the > config r

Re: nvme timeout issues with hardware and bhyve vm's

On Thu, Dec 7, 2023 at 4:09 PM Tomoaki AOKI wrote: > On Thu, 7 Dec 2023 14:38:37 -0800 > Pete Wright wrote: > > > > > > > On 10/13/23 7:34 PM, Warner Losh wrote: > > > > > > > > > > > the messages i posted in the start of the thread are from the VM > itself > > > (13.2-RELEASE). The zpo

Re: nvme timeout issues with hardware and bhyve vm's

On 12/7/23 3:16 PM, Craig Leres wrote: On 12/7/23 15:09, Tomoaki AOKI wrote: If I myself encounter this kind of problem ON BARE METAL HARDWARE, I would usually suspect   *Overheating caused hang of NVMe controller or PCI bridge on SSD, or This would also be my first guess. Five years ago

Re: nvme timeout issues with hardware and bhyve vm's

On 12/7/23 2:49 PM, Warner Losh wrote: On Thu, Dec 7, 2023 at 3:38 PM Pete Wright > wrote: On 10/13/23 7:34 PM, Warner Losh wrote: > > >     the messages i posted in the start of the thread are from the VM itself >     (13.2-RELEAS

Re: nvme timeout issues with hardware and bhyve vm's

On 12/7/23 15:09, Tomoaki AOKI wrote: If I myself encounter this kind of problem ON BARE METAL HARDWARE, I would usually suspect *Overheating caused hang of NVMe controller or PCI bridge on SSD, or This would also be my first guess. Five years ago I had an nmve in an intel nuc that would so

Re: nvme timeout issues with hardware and bhyve vm's

On Thu, 7 Dec 2023 14:38:37 -0800 Pete Wright wrote: > > > On 10/13/23 7:34 PM, Warner Losh wrote: > > > > > > > the messages i posted in the start of the thread are from the VM itself > > (13.2-RELEASE).  The zpool on the hypervisor (13.2-RELEASE) showed no > > such issues. > >

Re: nvme timeout issues with hardware and bhyve vm's

On Thu, Dec 7, 2023 at 3:38 PM Pete Wright wrote: > > > On 10/13/23 7:34 PM, Warner Losh wrote: > > > > > > > the messages i posted in the start of the thread are from the VM > itself > > (13.2-RELEASE). The zpool on the hypervisor (13.2-RELEASE) showed no > > such issues. > > > >

Re: nvme timeout issues with hardware and bhyve vm's

On 10/13/23 7:34 PM, Warner Losh wrote: the messages i posted in the start of the thread are from the VM itself (13.2-RELEASE).  The zpool on the hypervisor (13.2-RELEASE) showed no such issues. Based on your comment about the improvements in 14 I'll focus my efforts

Re: aarch64 and armv6 vs. armv7 support: armv6 is not supported, despite what "man arch" reports

On Dec 7, 2023, at 01:19, Dimitry Andric wrote: > On 7 Dec 2023, at 05:31, Mark Millard wrote: >> >> man arch reports: >> >> QUOTE >>Some machines support more than one FreeBSD ABI. Typically these are >>64-bit machines, where the “native” LP64 execution environment is >>accompani

Re: aarch64 and armv6 vs. armv7 support: armv6 is not supported, despite what "man arch" reports

On Thu, Dec 7, 2023, 2:19 AM Dimitry Andric wrote: > On 7 Dec 2023, at 05:31, Mark Millard wrote: > > > > man arch reports: > > > > QUOTE > > Some machines support more than one FreeBSD ABI. Typically these are > > 64-bit machines, where the “native” LP64 execution environment is > >

Re: aarch64 and armv6 vs. armv7 support: armv6 is not supported, despite what "man arch" reports

Hi; Am Wed, Dec 06, 2023 at 08:31:13PM -0800 schrieb Mark Millard: > man arch reports: > > QUOTE > Some machines support more than one FreeBSD ABI. Typically these are > 64-bit machines, where the “native” LP64 execution environment is > accompanied by the “legacy” ILP32 environme

Re: aarch64 and armv6 vs. armv7 support: armv6 is not supported, despite what "man arch" reports

On 7 Dec 2023, at 05:31, Mark Millard wrote: > > man arch reports: > > QUOTE > Some machines support more than one FreeBSD ABI. Typically these are > 64-bit machines, where the “native” LP64 execution environment is > accompanied by the “legacy” ILP32 environment, which was the hist