From: Takashi Iwai <tiwai@suse.de>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Warning! Unlikely big volume range (=9234), cval->res is probably wrong. (Dell XPS 13 9360 and Plantronics Blackwire 315.1
Date: Wed, 14 Feb 2024 16:12:33 +0100 [thread overview]
Message-ID: <87jzn7gjvi.wl-tiwai@suse.de> (raw)
In-Reply-To: <a18994c5-6584-403f-8754-b9db43c1f6fa@molgen.mpg.de>
On Wed, 14 Feb 2024 15:53:03 +0100,
Paul Menzel wrote:
>
> Dear Linux folks,
>
>
> On the Dell XPS 13 9360, plugging in a USB headset, I saw the warning
> below the first time since using the devices since December 2023.
>
> ```
> $ sudo dmesg | grep -e "DMI:" -e "Linux version" -e microcode
> [ 0.000000] Linux version 6.8.0-rc4
> (build@bohemianrhapsody.molgen.mpg.de) (gcc (Debian 13.2.0-13) 13.2.0,
> GNU ld (GNU Binutils for Debian) 2.42) #20 SMP PREEMPT_DYNAMIC Mon Feb
> 12 09:40:49 CET 2024
> [ 0.000000] DMI: Dell Inc. XPS 13 9360/0596KF, BIOS 2.21.0 06/02/2022
> [ 0.386024] microcode: Current revision: 0x000000f4
> [ 0.386026] microcode: Updated early from: 0x000000f0
> […]
> [88628.500854] usb 1-2: new full-speed USB device number 11 using xhci_hcd
> [88628.723620] usb 1-2: New USB device found, idVendor=047f,
> idProduct=c037, bcdDevice= 1.45
> [88628.723627] usb 1-2: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [88628.723629] usb 1-2: Product: Plantronics Blackwire 315.1
> [88628.723631] usb 1-2: Manufacturer: Plantronics
> [88628.723633] usb 1-2: SerialNumber: F3D422B734B3EC4CAF12EA236AFCB5EA
> [88628.794126] input: Plantronics Plantronics Blackwire 315.1 Consumer
> Control as
> /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.3/0003:047F:C037.000F/input/input67
> [88628.853158] input: Plantronics Plantronics Blackwire 315.1 as
> /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.3/0003:047F:C037.000F/input/input68
> [88628.853253] input: Plantronics Plantronics Blackwire 315.1 as
> /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.3/0003:047F:C037.000F/input/input69
> [88628.853428] hid-generic 0003:047F:C037.000F: input,hiddev1,hidraw2:
> USB HID v1.11 Device [Plantronics Plantronics Blackwire 315.1] on
> usb-0000:00:14.0-2/input3
> [88628.853447] probe of 0003:047F:C037.000F returned 0 after 59756 usecs
> [88628.853463] probe of 1-2:1.3 returned 0 after 127842 usecs
> [88628.853491] probe of 1-2 returned 0 after 129625 usecs
> [88628.892691] calling alsa_rawmidi_init+0x0/0xff0 [snd_rawmidi] @ 117168
> [88628.892707] initcall alsa_rawmidi_init+0x0/0xff0 [snd_rawmidi]
> returned 0 after 1 usecs
> [88628.964882] calling usb_audio_driver_init+0x0/0xff0
> [snd_usb_audio] @ 117168
> [88629.840845] usb 1-2: Warning! Unlikely big volume range (=9234),
> cval->res is probably wrong.
> [88629.840850] usb 1-2: [11] FU [Sidetone Playback Volume] ch = 1, val
> = 0/9234/1
> [88630.401192] probe of 1-2:1.0 returned 0 after 1436245 usecs
> [88630.401216] usbcore: registered new interface driver snd-usb-audio
> [88630.401219] initcall usb_audio_driver_init+0x0/0xff0
> [snd_usb_audio] returned 0 after 1436302 usecs
> [89546.685992] usb 1-2: USB disconnect, device number 11
> ```
>
> (`/sbin/alsa-info` [1])
>
> I am unable to reproduce this. Is that a problem with the headset, the
> laptop or something else?
>
> Looking at the archive of Linux messages archive of *Hardware for
> Linux* [1], the message shows up quite often.
You can ignore it as long as the device appears working.
It mere informs a firmware bug of the device. The driver detected it
and avoids the strange volume setup.
I have such a Plantronics USB headset, too ;)
thanks,
Takashi
>
>
> Kind regards,
>
> Paul
>
>
> [1]: https://alsa-project.org/db/?f=3dc36e15c0cd57e299a119fb0b5b1ad6ed78e898
> [2]: https://github.com/linuxhw/Dmesg
prev parent reply other threads:[~2024-02-14 15:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 14:53 Paul Menzel
2024-02-14 15:12 ` Takashi Iwai [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87jzn7gjvi.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pmenzel@molgen.mpg.de \
--cc=tiwai@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®