>Number:         4523
>Category:       port-i386
>Synopsis:       pms probe routine uses unusually long time
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    gnats-admin (GNATS administrator)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Nov 17 14:20:01 1997
>Last-Modified:
>Originator:     Havard Eidnes
>Organization:
	SINTEF RUNIT
>Release:        NetBSD-1.3_ALPHA Nov 15 1997
>Environment:
System: NetBSD vader.runit.sintef.no 1.3_ALPHA NetBSD 1.3_ALPHA (VADER) #11: Sat Nov 8 20:20:41 MET 1997 he@vader.runit.sintef.no:/usr/src/sys/arch/i386/compile/VADER i386


>Description:
	On my laptop, a Dell Latitude XPi/CD 150, the PS/2 mouse probe
	routine appears to use unusually long time doing its work.

	More precisely, I inserted a few printf() calls in the pms.c probe
	routine, like this:

		printf("pmsprobe before reset\n"); 
		pms_dev_cmd(PMS_RESET);
		pms_aux_cmd(PMS_AUX_TEST); 
		delay(1000);
		x = inb(PMS_DATA);
		pms_pit_cmd(PMS_INT_DISABLE);
		if (x & 0x04) 
			return 0;
 
		printf("pmsprobe normal return\n");
		return 1;

	and it takes approximately 90 seconds (!) between the driver
	executes the first and the last printf().

>How-To-Repeat:
	Boot a recent snapshot in a Dell XPi/CD with the pms driver in
	the kernel, and watch it "nearly hang" in the pms probe routine.

	I'm not sure how (or if) this affects other laptops.

>Fix:
	Sorry, I've no idea, but at least it's now narrowed down somewhat...
>Audit-Trail:
>Unformatted: