Greg Lehey wrote:
[snip]
> >>> Using a recent (few days) -current I had a process lock up on me
> >>> last night, so I did a 'ktrace -p whateverthepidwas' and let it run for a
> >>> while. When I issued a 'ktrace -C' in another screen, everything froze and
> >>> the kernel panic'ed. I dropped
On Wednesday, 23 June 1999 at 18:11:21 -0700, Doug wrote:
> On Thu, 24 Jun 1999, Greg Lehey wrote:
>
>> On Wednesday, 23 June 1999 at 11:45:12 -0700, Doug wrote:
>>> Using a recent (few days) -current I had a process lock up on me
>>> last night, so I did a 'ktrace -p whateverthepidwas' and le
On Thu, 24 Jun 1999, Greg Lehey wrote:
> On Wednesday, 23 June 1999 at 11:45:12 -0700, Doug wrote:
> > Using a recent (few days) -current I had a process lock up on me
> > last night, so I did a 'ktrace -p whateverthepidwas' and let it run for a
> > while. When I issued a 'ktrace -C' in anoth
On Wednesday, 23 June 1999 at 11:45:12 -0700, Doug wrote:
> Using a recent (few days) -current I had a process lock up on me
> last night, so I did a 'ktrace -p whateverthepidwas' and let it run for a
> while. When I issued a 'ktrace -C' in another screen, everything froze and
> the kernel p
On Wed, 23 Jun 1999, Doug wrote:
> Using a recent (few days) -current I had a process lock up on me
> last night, so I did a 'ktrace -p whateverthepidwas' and let it run for a
> while. When I issued a 'ktrace -C' in another screen, everything froze and
> the kernel panic'ed. I dropped to th
