kern/59999: umass(4): disklabel takes minutes to fail on nonresponsive device

["campbell+netbsd%mumble.net@localhost via gnats" <gnats-admin%NetBSD.org@localhost>]

>Number:         59999
>Category:       kern
>Synopsis:       umass(4): disklabel takes minutes to fail on nonresponsive device
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Feb 13 05:10:00 +0000 2026
>Originator:     Taylor R Campbell
>Release:        current, 11, 10, 9, ..
>Organization:
The NotBSDisklabel Foundation, USB
>Environment:
>Description:

	My laptop has an sd(4) device that is normally nonresponsive --
	it times out on every query.  It's probably the SD card reader
	(and might be responsive if I put an SD card in it) but I
	haven't investigated.

	When I run `disklabel sd1', which /etc/security does every day,
	it takes several minutes to give up and really time out,
	printing messages like the following to dmesg every 5-10sec as
	it goes:

[ 935841.875979] umass1: BBB bulk-in clear stall failed, TIMEOUT
[ 935846.876044] umass1: BBB bulk-out clear stall failed, TIMEOUT
[ 935866.876304] umass1: BBB reset failed, TIMEOUT
[ 935871.876369] umass1: BBB bulk-in clear stall failed, TIMEOUT
[ 935876.876434] umass1: BBB bulk-out clear stall failed, TIMEOUT
[ 935896.876695] umass1: BBB reset failed, TIMEOUT
[ 935901.876760] umass1: BBB bulk-in clear stall failed, TIMEOUT
[ 935906.876825] umass1: BBB bulk-out clear stall failed, TIMEOUT
[ 935976.877736] umass1: BBB reset failed, TIMEOUT

>How-To-Repeat:

	1. find an sd(4) device that is not responsive, say sd1
	2. run `disklabel sd1' on it
	3. put a kettle on and get out the cheese and crackers to pass
	   the time while you wait

>Fix:

	Yes, please!