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

To: tech-kern%NetBSD.org@localhost
Subject: Re: ktrace-ing a command that locks up the machine
From: Mouse <mouse%Rodents-Montreal.ORG@localhost>
Date: Wed, 18 Nov 2020 08:10:21 -0500 (EST)

> I would like to ktrace/ktruss the command to see which USB transfer
> exactly is the one that hangs.  However, even with ktrace -s, there
> is no trace file after the re-boot (on FFS/WAPBL); I can't tell
> whether it exists before the reboot.  Using ktruss, the last trace
> output to the console is way behind the execution.

Suggestion: put the ktrace file on a filesystem mounted -o sync.

/~\ The ASCII				  Mouse
\ / Ribbon Campaign
 X  Against HTML		mouse%rodents-montreal.org@localhost
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

Follow-Ups:
- Re: ktrace-ing a command that locks up the machine
  - From: Edgar Fuß

References:
- ktrace-ing a command that locks up the machine
  - From: Edgar Fuß

Prev by Date: ktrace-ing a command that locks up the machine
Next by Date: Re: ktrace-ing a command that locks up the machine
Previous by Thread: ktrace-ing a command that locks up the machine
Next by Thread: Re: ktrace-ing a command that locks up the machine
Indexes:

Home | Main Index | Thread Index | Old Index