Re: ktrace-ing a command that locks up the machine

[Paul Goyette <paul%whooppee.com@localhost>]

Hmmm, this was usb, right?

Maybe turn on options USBHIST (and/or EHCIHIST, OHCIHIST, UHCIHIST,
XHCIHIST).  None of these seem to be described in options(4) man
page, but you can dump the debug data using ``vmstat -u histname''.
And get a listof the actual histname's with ``vmstat -l''

If you have a crash dump, you can use crash(8) to show the history
data (see ``show kernhist'' command in ddb(4) man page).


On Wed, 18 Nov 2020, Paul Goyette wrote:

> On Wed, 18 Nov 2020, Edgar Fuß wrote:
>
> > > Suggestion: put the ktrace file on a filesystem mounted -o sync.
> > That (with ktrace -s) gave me an empty file.
>
> If you've got a spare disk (or space partition) try
>
> 	ktrace -f /dev/rwdxx ...
>
>
> Maybe that will help.
>
>
> +--------------------+--------------------------+-----------------------+
> | Paul Goyette       | PGP Key fingerprint:     | E-mail addresses:     |
> | (Retired)          | FA29 0E3B 35AF E8AE 6651 | paul%whooppee.com@localhost     |
> | Software Developer | 0786 F758 55DE 53BA 7731 | pgoyette%netbsd.org@localhost   |
> +--------------------+--------------------------+-----------------------+

+--------------------+--------------------------+-----------------------+
| Paul Goyette       | PGP Key fingerprint:     | E-mail addresses:     |
| (Retired)          | FA29 0E3B 35AF E8AE 6651 | paul%whooppee.com@localhost     |
| Software Developer | 0786 F758 55DE 53BA 7731 | pgoyette%netbsd.org@localhost   |
+--------------------+--------------------------+-----------------------+