* De: Maxime Henrion <[EMAIL PROTECTED]> [ Data: 2002-11-22 ]
[ Subjecte: Re: VM locking problem... And doscmd(8) ]
> John Baldwin wrote:
> >
> > On 22-Nov-2002 Juli Mallett wrote:
> > > * De: Robert Watson <[EMAIL PROTECTED]> [ Data: 2002-11-21 ]
&g
John Baldwin wrote:
>
> On 22-Nov-2002 Juli Mallett wrote:
> > * De: Robert Watson <[EMAIL PROTECTED]> [ Data: 2002-11-21 ]
> > [ Subjecte: Re: VM locking problem... And doscmd(8) ]
> >> On Thu, 21 Nov 2002, Juli Mallett wrote:
> >>
> >> &
On 22-Nov-2002 Juli Mallett wrote:
> * De: Robert Watson <[EMAIL PROTECTED]> [ Data: 2002-11-21 ]
> [ Subjecte: Re: VM locking problem... And doscmd(8) ]
>> On Thu, 21 Nov 2002, Juli Mallett wrote:
>>
>> > I'm getting a giant owned assertion fail
* De: Robert Watson <[EMAIL PROTECTED]> [ Data: 2002-11-21 ]
[ Subjecte: Re: VM locking problem... And doscmd(8) ]
> On Thu, 21 Nov 2002, Juli Mallett wrote:
>
> > I'm getting a giant owned assertion failure in the vm_map code, simply
> > by running
On Thu, 21 Nov 2002, Juli Mallett wrote:
> I'm getting a giant owned assertion failure in the vm_map code, simply
> by running "doscmd something.exe" where something.exe is a
> self-extracting ZIP file (of BIOS upgrade stuff, FWIW), which leads
> trivially to tripping over it. I still don't have
I'm getting a giant owned assertion failure in the vm_map code,
simply by running "doscmd something.exe" where something.exe is
a self-extracting ZIP file (of BIOS upgrade stuff, FWIW), which
leads trivially to tripping over it. I still don't have a good
way to get the trace output from the box in
