>Number:         18702
>Category:       xsrc
>Synopsis:       f000:a222: 01 ILLEGAL EXTENDED X86 OPCODE
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    xsrc-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Oct 18 12:55:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Joe
>Release:        1.6.0
>Organization:
>Environment:
NetBSD razor 1.6 NetBSD 1.6 (GENERIC_LAPTOP) #0: Sun Sep 8 19:55:58 UTC 2002 autobuild@tgm.daemon.org:/autobuild/i386/OBJ/autobuild/ser/sys/arch/i386/compile/GENERIC_LAPTOP i386
>Description:
When X starts up I get a message in /var/log/XFree86.0.log that says "f000:a222: 01 ILLEGAL EXTENDED X86 OPCODE" .  I have traced the message to the xc/programs/Xserver/hw/xfree86/os-support/vbe/vbe.c program.  

The message before this is "VESA VBE DDC Transfer in appr 1 sec" (this is from the last line in vbeProbeDDC before the return). and then I see the message about f000:a222 etc.  Then the next line is "VESA VBE DDC invalid". Somewhere in the code below it is happening.  I think that the vbeProbeDDC is okay as that does not error. I think it may be something in the xf86ExecX86int10() function call.  Any ideas?

if (!vbeProbeDDC(pVbe)) goto error;
    
	pVbe->pInt10->ax = 0x4F15;
    pVbe->pInt10->bx = 0x01;
	pVbe->pInt10->cx = 0;
	    pVbe->pInt10->es = SEG_ADDR(RealOff);
	pVbe->pInt10->di = SEG_OFF(RealOff);
	    pVbe->pInt10->num = 0x10;

	xf86ExecX86int10(pVbe->pInt10);
				    
	if ((pVbe->pInt10->ax & 0xff) != 0x4f) {
		xf86DrvMsgVerb(screen,X_INFO,3,"VESA VBE DDC invalid\n");
		goto error;
	    }



>How-To-Repeat:
It happens on my laptop all the time I just look at the log.  Not sure if this is a real problem or just a weird message.  X works.  I also tried this with 1.5.3 and X 4.2.0 and 1.6.0 with X 4.2.1 and the same thing happens.  

 
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: