> On 4 Jul 2023, at 17:01, Chuck Tuffli wrote:
>
> On Thu, Jun 29, 2023 at 12:47 PM Juraj Lutter wrote:
>>
>> With recent -current, following occured:
>>
>> db> bt
>> Tracing pid 0 tid 100063 td 0xfe00c5c35e40
>> kdb_enter() at kdb_enter+0x32/frame 0xfe00c5e31c90
>> vpanic() at vpan
On Thu, Jun 29, 2023 at 12:47 PM Juraj Lutter wrote:
>
> With recent -current, following occured:
>
> db> bt
> Tracing pid 0 tid 100063 td 0xfe00c5c35e40
> kdb_enter() at kdb_enter+0x32/frame 0xfe00c5e31c90
> vpanic() at vpanic+0x181/frame 0xfe00c5e31ce0
> panic() at panic+0x43/frame 0
>>
>> machine is a bhyve guest.
>
> Did bhyve log any warnings or errors? I'm curious if its NVMe
> emulation did something dumb or itself noticed an issue.
>
No, nothing in bhyve logs, nothing in host’s syslog.
For now, I’ve left `cu’ session to VM’s console running under tmux to see if
th
On Thu, Jun 29, 2023 at 12:47 PM Juraj Lutter wrote:
>
> With recent -current, following occured:
>
> db> bt
> Tracing pid 0 tid 100063 td 0xfe00c5c35e40
> kdb_enter() at kdb_enter+0x32/frame 0xfe00c5e31c90
> vpanic() at vpanic+0x181/frame 0xfe00c5e31ce0
> panic() at panic+0x43/frame 0
> On 29 Jun 2023, at 22:01, Warner Losh wrote:
>
> What's the panic string?
I don’t have any, even savecore did not worked.
I’ve left a “cu” session to the VM’s console running under tmux and should it
reappear, I can grab it.
otis
—
Juraj Lutter
o...@freebsd.org
What's the panic string?
On Thu, Jun 29, 2023, 1:47 PM Juraj Lutter wrote:
> With recent -current, following occured:
>
> db> bt
> Tracing pid 0 tid 100063 td 0xfe00c5c35e40
> kdb_enter() at kdb_enter+0x32/frame 0xfe00c5e31c90
> vpanic() at vpanic+0x181/frame 0xfe00c5e31ce0
> panic()
With recent -current, following occured:
db> bt
Tracing pid 0 tid 100063 td 0xfe00c5c35e40
kdb_enter() at kdb_enter+0x32/frame 0xfe00c5e31c90
vpanic() at vpanic+0x181/frame 0xfe00c5e31ce0
panic() at panic+0x43/frame 0xfe00c5e31d40
nvme_ctrlr_identify() at nvme_ctrlr_identify+0x10e/
