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

Bug#1041191: marked as done (“invalid interface number” on Broadcom Corp. BCM5880 Secure Applications Processor with fingerprint swipe sensor)

Your message dated Tue, 01 Aug 2023 01:09:37 +0200
with message-id <6531216.tM3a2QDmDi@bagend>
and subject line Re: Debian's BTS is not for regular user questions
has caused the Debian Bug report #1041191,
regarding “invalid interface number” on Broadcom Corp. BCM5880 Secure Applications Processor with fingerprint swipe sensor
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1041191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041191
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-6.1.0-10-amd64
Version: 6.1.37-1
The journal shows several warnings (orange texts “usb 3-1.8: config 0 has an invalid interface number: 3 but max is 2”, “config 0 has no interface number 2”, and “usb 3-1.8: config 0 descriptor??”):
Jul 15 15:21:43 AnonymizedMachineName kernel: usb 3-1.8: new full-speed USB device number 4 using ehci-pci Jul 15 15:21:43 AnonymizedMachineName kernel: scsi 0:0:0:0: Direct-Access ATA SAMSUNG SSD PM83 3D1Q PQ: 0 ANSI: 5 Jul 15 15:21:43 AnonymizedMachineName kernel: usb 1-1.5: New USB device found, idVendor=0c45, idProduct=643f, bcdDevice=28.06 Jul 15 15:21:43 AnonymizedMachineName kernel: usb 1-1.5: New USB device strings: Mfr=2, Product=1, SerialNumber=0 Jul 15 15:21:43 AnonymizedMachineName kernel: usb 1-1.5: Product: Laptop_Integrated_Webcam_E4HD Jul 15 15:21:43 AnonymizedMachineName kernel: usb 1-1.5: Manufacturer: CN0Y4TWT72487279AAYJA00 Jul 15 15:21:43 AnonymizedMachineName kernel: usb 3-1.8: config 0 has an invalid interface number: 3 but max is 2 Jul 15 15:21:43 AnonymizedMachineName kernel: usb 3-1.8: config 0 has no interface number 2 Jul 15 15:21:43 AnonymizedMachineName kernel: usb 3-1.8: New USB device found, idVendor=0a5c, idProduct=5801, bcdDevice= 1.01 Jul 15 15:21:43 AnonymizedMachineName kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 15 15:21:43 AnonymizedMachineName kernel: usb 3-1.8: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jul 15 15:21:43 AnonymizedMachineName kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out 
Jul 15 15:21:43 AnonymizedMachineName kernel: usb 3-1.8: Product: 5880
Jul 15 15:21:43 AnonymizedMachineName kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00(DEVICE CONFIGURATION OVERLAY) filtered out Jul 15 15:21:43 AnonymizedMachineName kernel: usb 3-1.8: Manufacturer: Broadcom Corp Jul 15 15:21:43 AnonymizedMachineName kernel: ata2.00: ACPI cmd 00/00:00:00:00:00:a0(NOP) rejected by device (Stat=0x51 Err=0x04) Jul 15 15:21:43 AnonymizedMachineName kernel: usb 3-1.8: SerialNumber: 0123456789ABCD Jul 15 15:21:43 AnonymizedMachineName kernel: usb 3-1.8: config 0 descriptor?? Jul 15 15:21:43 AnonymizedMachineName kernel: ata2.00: supports DRM functions and may not be fully accessible 
…
Jul 15 15:21:44 AnonymizedMachineName systemd[1]: Starting systemd-udevd.service - Rule-based Manager for Device Events and Files... Jul 15 15:21:46 AnonymizedMachineName mtp-probe[408]: checking bus 3, device 4: "/sys/devices/pci0000:00/0000:00:1d.0/usb3/3-1/3-1.8" 


`lsusb -v` shows that they belong to the fingerprint sensor:
Bus 003 Device 004: ID 0a5c:5801 Broadcom Corp. BCM5880 Secure Applications Processor with fingerprint swipe sensor 
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x0a5c Broadcom Corp.
idProduct 0x5801 BCM5880 Secure Applications Processor with fingerprint swipe sensor 
  bcdDevice            1.01
  iManufacturer           1 Broadcom Corp
  iProduct                2 5880
  iSerial                 3 0123456789ABCD
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x00ab
    bNumInterfaces          3
    bConfigurationValue     0
    iConfiguration          0
    bmAttributes         0xe0
      Self Powered
      Remote Wakeup
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass       254 Application Specific Interface
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              4 Broadcom USH w/swipe sensor
      ** UNRECOGNIZED:  10 25 00 00 00 00 00 00 00 00 00 00 00 00 00 00
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x85  EP 5 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval              32
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        1
      bAlternateSetting       0
      bNumEndpoints           3
      bInterfaceClass        11 Chip/SmartCard
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              5 Contacted SmartCard
      ChipCard Interface Descriptor:
        bLength                54
        bDescriptorType        33
        bcdCCID              1.00
        nMaxSlotIndex           0
        bVoltageSupport         7  5.0V 3.0V 1.8V
        dwProtocols             3  T=0 T=1
        dwDefaultClock       4000
        dwMaxiumumClock      4000
        bNumClockSupported      0
        dwDataRate           9600 bps
        dwMaxDataRate      250000 bps
        bNumDataRatesSupp.      0
        dwMaxIFSD             247
        dwSyncProtocols  00000000
        dwMechanical     00000000
        dwFeatures       000102BA
          Auto configuration based on ATR
          Auto voltage selection
          Auto clock change
          Auto baud rate change
          Auto PPS made by CCID
          NAD value other than 0x00 accepted
          TPDU level exchange
        dwMaxCCIDMsgLen       271
        bClassGetResponse      00
        bClassEnvelope         00
        wlcdLayout           none
        bPINSupport             0
        bMaxCCIDBusySlots       1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x86  EP 6 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval              32
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        3
      bAlternateSetting       0
      bNumEndpoints           1
      bInterfaceClass       254 Application Specific Interface
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              7 Broadcom USH
      ** UNRECOGNIZED:  10 26 00 00 00 00 00 00 00 00 00 00 00 00 00 00
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x87  EP 7 IN
        bmAttributes            3
          Transfer Type            Interrupt
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0010  1x 16 bytes
        bInterval              32
Device Status:     0x0000
  (Bus Powered)
The part “an invalid interface number: 3 but max is 2” doesn't sound good. Any problem with the kernel or the driver? Will the fingerprint sensor not work? At the same time, other USB devices (namely, physical USB-A ports) sometimes fail due to physical wear (bad electrical contact); so these problems might hypothetically be related. Moreover, the machine experiences other problems later during boot, so what are the extent and potential consequences of the warnings here? 

Gratefully,
AlMa

--- End Message ---
--- Begin Message --- 
On Sat, 15 Jul 2023 03:13:51 +0200 AlMa <AlMa0@ro.ru> wrote:
> In the journal I see two yellow lines (which, probably, constitute 
> warnings) directly following one another:
> … 
> Later in the journal we see a white line
> … 
> 
> As the machine (Dell Mobile Precision M6700) experiences various 
> high-level issues later in the boot process, I'm unsure about the 
> contribution of the two issues in the log.  Which software or hardware 
> problems do these warnings inform us about?  Any fix or remedy?

You filed various bugs talking about yellow and white lines of which you 
suspect that yellow may be a warning (which you should be able to find out by 
yourself if that's the case).

The Debian BTS is not meant to ask questions like "what could this message 
tell us?". Put it in a search engine or use one of the MANY user support 
options for that. Computers/Linux put various debug/informational/warning msgs 
in various logs, which _could_ be helpful in case there's an actual ERROR.

But the only *potential* error I see here is "various high-level issues", 
which is so vague so that's completely useless and inactionable.

So I'm going to close this and similar vague bug reports, which aren't 
actually bug reports, but just questions.
And all those ACPI errors? Contact the machine vendor as they're the only ones 
who could resolve such issue. Linux is only reporting that there are issues.

"If we believe Jean Delvare" ... and Jean Delvare response in that bug report:
"This is not a support forum, sorry. If you need help, use support forums and 
mailing lists." ...

From 'bug' #1041191: "Will the fingerprint sensor not work?"
I _assume_ you have the device/machine, so why don't you try it out?
*IF* it turns out it doesn't work then you first use a search engine to see if 
you can make it work yourself by trying out various hints you'll undoubtedly 
find and if that doesn't make it work, *THEN* you have something to file a bug 
about.

You filed *8* different 'bugs' which (almost?) all are about a Dell Mobile 
Precision M6700 ... and not once did you say what actual problem you 
experienced?!?

If you file a bug, you're (basically) asking (several) people to read about a 
problem you're having and then subsequently (potentially) spend time to fix 
that/those problem(s).
Please be more considerate with other people's time and only file bugs for 
*actual* problems and then provide enough information/context so that they
can actually (potentially) act upon it and help you fix that problem.

I initially intended to respond to some actual problems you (also) reported, 
but I've already spend way too much time on these non-issues, so I'm done.

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: