>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 could reproduce this and double check me?
Same here. I think it is missing at least enlargement of the limit
of 0x67.
>Also ... I think I could analyze this better if I could break into the
>debugger and set a break point *before* the panic, and start tracing
>at the i386_set_ioperm() routine and follow what happens from there.
>Is there a function call that I can insert at the appropriate place to
>force dropping into the kernel debugger?
Just set a breakpoint:
Ctrl-SysReq enter ddb
b i386_set_ioperm set breakpoint
c leave ddb
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
