> >>The panic occurs at 'swtch_com+0x6e: ltr %si'. At the time, %si is
> >>0x20, which indexes to what appears to be a busy tss (type=01011b)
> >>with a limit of 0x67. That instruction generates a general protection
> >>fault with an error code of 0. The current process was Idle.
>
> The busy
>>The panic occurs at 'swtch_com+0x6e: ltr %si'. At the time, %si is
>>0x20, which indexes to what appears to be a busy tss (type=01011b)
>>with a limit of 0x67. That instruction generates a general protection
>>fault with an error code of 0. The current process was Idle.
The busy tss seems to
>The panic occurs at 'swtch_com+0x6e: ltr %si'. At the time, %si is
>0x20, which indexes to what appears to be a busy tss (type=01011b)
>with a limit of 0x67. That instruction generates a general protection
>fault with an error code of 0. The current process was Idle.
>...
>Perhaps someone coul
Hi,
I'm chasing down a panic that occurs when you call 'i386_set_ioperm()'
in -current (19990625-SNAP). This call worked correctly in the
19990426-SNAP. I first noticed the problem with the 6/10 snap and
it's still with us as of the 6/25 snap.
The panic occurs at 'swtch_com+0x6e: ltr %si'. At
