NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

kern/57947: autoconfig errors probing card reader



>Number:         57947
>Category:       kern
>Synopsis:       autoconfig errors probing card reader
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Feb 19 04:30:00 +0000 2024
>Originator:     David A. Holland
>Release:        NetBSD 10.99.10 (20240218)
>Organization:
>Environment:
System: NetBSD valkyrie 10.99.10 NetBSD 10.99.10 (VALKYRIE2) #0: Sun Feb 18 22:10:52 EST 2024  dholland@valkyrie:/usr/obj/sys/arch/amd64/compile/VALKYRIE2 amd64
Architecture: x86_64
Machine: amd64
>Description:

I have a random card reader in this machine (I think it's part of the
case) and I noticed today while looking at other things that it probes
like this:

umass0 at uhub1 port 5 configuration 1 interface 0
umass0: Generic (0x058f) Mass Storage Device (0x6362), rev 2.00/1.29, addr 2
umass0: using SCSI over Bulk-Only
scsibus0 at umass0: 2 targets, 4 luns per target
sd0 at scsibus0 target 0 lun 0: <Generic, USB SD Reader, 1.00> disk removable
sd0: drive offline
autoconfiguration error: sd0: unable to open device, error = 19
sd1 at scsibus0 target 0 lun 1: <Generic, USB CF Reader, 1.01> disk removable
sd1: drive offline
autoconfiguration error: sd1: unable to open device, error = 19
sd2 at scsibus0 target 0 lun 2: <Generic, USB SM Reader, 1.02> disk removable
sd2: drive offline
autoconfiguration error: sd2: unable to open device, error = 19
sd3 at scsibus0 target 0 lun 3: <Generic, USB MS Reader, 1.03> disk removable
sd3: drive offline
autoconfiguration error: sd3: unable to open device, error = 19

which seems not entirely optimal. It has no cards in it so being
offline is reasonable, but it also seems like that shouldn't be an
error.

Haven't _used_ the thing in ages (possibly never) so I'm not sure if
this is new behavior, or if so how new.

>How-To-Repeat:

boot, read dmesg carefully

>Fix:

dunno



Home | Main Index | Thread Index | Old Index