USB Sound Card

zetrotrack000 · 07-09-2017, 03:38 AM

Hi
One of my laptops (installed with arch linux) has a non-repairable faulty audio jack, so I use USB sound card in order use a headphone. However, sometimes suddenly the system freezes and I have to hard reset it. Journalctl is showing following error:

Code:

Jul 08 23:32:19 laptop1 pulseaudio[635]: W: [alsa-sink-USB Audio] alsa-util.c: Got POLLNVAL from ALSA
Jul 08 23:32:19 laptop1 pulseaudio[635]: W: [alsa-sink-USB Audio] alsa-util.c: Could not recover from POLLERR|POLLNVAL|POLLHUP wi
Jul 08 23:32:19 laptop1 kernel: usb 1-2: reset full-speed USB device number 4 using xhci_hcd
Jul 08 23:32:19 laptop1 kernel: usb 1-2: device descriptor read/64, error -71
Jul 08 23:32:19 laptop1 kernel: usb 1-2: device descriptor read/64, error -71
Jul 08 23:32:20 laptop1 kernel: usb 1-2: reset full-speed USB device number 4 using xhci_hcd
Jul 08 23:32:20 laptop1 kernel: usb 1-2: device descriptor read/64, error -71
Jul 08 23:32:20 laptop1 kernel: usb 1-2: device descriptor read/64, error -71
Jul 08 23:32:20 laptop1 kernel: usb 1-2: reset full-speed USB device number 4 using xhci_hcd

Although I am unfamiliar to these errors but one thing that I am sure about is that the problem is happening due USB. Kindly help me to solve this problem.
Regards

DavidMcCann · 07-09-2017, 10:28 AM

There are some old posts with the same error, which may (or may not) provide a solution
https://www.linuxquestions.org/quest...r-71-a-643022/
https://forums.gentoo.org/viewtopic-p-6825958.html
https://www.linuxquestions.org/quest...r-71-a-756935/
At least they offer some starting points to explore: bad cable, wrong sort of USB port, mysterious command to use, etc.

zetrotrack000 · 07-09-2017, 11:46 AM

These posts are very old and talking about USB 1.1 and USB 2.0. However, my laptop has USB 3.0 and the sound card is also new (bought 4 months ago). Here is the output of lsusb:

Code:

Bus 003 Device 002: ID 0d8c:013c C-Media Electronics, Inc. CM108 Audio Controller

Are these things still applicable to linux? I doubt that!

zetrotrack000 · 07-09-2017, 03:07 PM

During boot, the system gives this error:

Code:

kernel: platform wdat_wdt: failed to claim resource 4: [io  0x0071-0x0072]
kernel: ACPI: watchdog: Device creation failed: -16

and this error:

Code:

kernel: blk_update_request: critical medium error, dev sr1, sector 21488
kernel: Buffer I/O error on dev sr1, logical block 2686, async page read
kernel: blk_update_request: critical medium error, dev sr1, sector 21480
kernel: Buffer I/O error on dev sr1, logical block 2685, async page read
kernel: blk_update_request: critical medium error, dev sr1, sector 21464
kernel: blk_update_request: critical medium error, dev sr1, sector 21464
kernel: Buffer I/O error on dev sr1, logical block 2683, async page read
kernel: blk_update_request: critical medium error, dev sr1, sector 21456
kernel: blk_update_request: critical medium error, dev sr1, sector 21456
kernel: Buffer I/O error on dev sr1, logical block 2682, async page read

Is that a sign that my hard-drive going to fail?
and this error:

Code:

systemd-coredump[747]: Process 677 (csd-keyboard) of user 1000 dumped core.
                                          
                                          Stack trace of thread 677:
                                          #0  0x00007f5287daa411 n/a (libglib-2.0.so.0)
                                          #1  0x00007f5287daca61 g_log_writer_default (libglib-2.0.so.0)
                                          #2  0x00007f5287daafae g_log_structured_array (libglib-2.0.so.0)
#3  0x00007f5287dab2a7 g_log_structured (libglib-2.0.so.0)
                                          #4  0x00007f52888d7651 n/a (libgdk-3.so.0)
                                          #5  0x00007f52888e4b03 n/a (libgdk-3.so.0)
                                          #6  0x00007f5288fd06ed _XError (libX11.so.6)
                                          #7  0x00007f5288fcd617 n/a (libX11.so.6)
                                          #8  0x00007f5288fcd6d5 n/a (libX11.so.6)
                                          #9  0x00007f5288fce5e8 _XReply (libX11.so.6)
                                          #10 0x00007f5288fb479e XGetWindowProperty (libX11.so.6)
                                          #11 0x00007f52888f5333 n/a (libgdk-3.so.0)
                                          #12 0x00007f52888f61a5 n/a (libgdk-3.so.0)
                                          #13 0x00007f52888dedef n/a (libgdk-3.so.0)
                                          #14 0x00007f52888df0f6 n/a (libgdk-3.so.0)
                                          #15 0x00007f52888a90f0 gdk_display_get_event (libgdk-3.so.0)
                                          #16 0x00007f52888dee82 n/a (libgdk-3.so.0)
                                          #17 0x00007f5287da4a57 g_main_context_dispatch (libglib-2.0.so.0)
                                          #18 0x00007f5287da4c88 n/a (libglib-2.0.so.0)
                                          #19 0x00007f5287da4fa2 g_main_loop_run (libglib-2.0.so.0)
                                          #20 0x00007f52894f9b25 gtk_main (libgtk-3.so.0)
                                          #21 0x0000000000403e2b main (csd-keyboard)
                                          #22 0x00007f52877b743a __libc_start_main (libc.so.6)
                                          #23 0x0000000000403f6a _start (csd-keyboard)
                                          
                                          Stack trace of thread 688:
                                          #0  0x00007f528787a24d poll (libc.so.6)
                                          #1  0x00007f5287da4c09 n/a (libglib-2.0.so.0)
                                          #2  0x00007f5287da4fa2 g_main_loop_run (libglib-2.0.so.0)
                                          #3  0x00007f528838c546 n/a (libgio-2.0.so.0)
 #4  0x00007f5287dcbae5 n/a (libglib-2.0.so.0)
                                          #5  0x00007f5287b43297 start_thread (libpthread.so.0)
                                          #6  0x00007f52878841ef __clone (libc.so.6)
                                          
                                          Stack trace of thread 705:
                                          #0  0x00007f528787a24d poll (libc.so.6)
                                          #1  0x00007f5287da4c09 n/a (libglib-2.0.so.0)
                                          #2  0x00007f5287da4d1c g_main_context_iteration (libglib-2.0.so.0)
                                          #3  0x00007f527a25455d n/a (libdconfsettings.so)
                                          #4  0x00007f5287dcbae5 n/a (libglib-2.0.so.0)
                                          #5  0x00007f5287b43297 start_thread (libpthread.so.0)
                                          #6  0x00007f52878841ef __clone (libc.so.6)
                                          
                                          Stack trace of thread 687:
                                          #0  0x00007f528787a24d poll (libc.so.6)
                                          #1  0x00007f5287da4c09 n/a (libglib-2.0.so.0)
                                          #2  0x00007f5287da4d1c g_main_context_iteration (libglib-2.0.so.0)
                                          #3  0x00007f5287da4d61 n/a (libglib-2.0.so.0)
                                          #4  0x00007f5287dcbae5 n/a (libglib-2.0.so.0)
                                          #5  0x00007f5287b43297 start_thread (libpthread.so.0)
                                          #6  0x00007f52878841ef __clone (libc.so.6)

Can you get anything from above info, which can help me?

DavidMcCann · 07-10-2017, 11:00 AM

No, your hard drive is fine! That would be /dev/sda — /dev/sr1 is an optical drive. Do you have a disk in the drive when you boot up?

That error code on the USB device seems to be indicative of a very low-level problem: the computer finds the device unusable. Did you try using different ports, both USB2 and USB3? Have you tried the device on a different computer? I'd expect a fault in the device to show up more often, though, and it's strange that it should cause a lock-up. If the audio jack stopped working, it might be that the USB controller is about to go too.

These sort of occasional failings can be very difficult to track down. This computer crashes about once a month. After making sure the memory wasn't faulty, I decided to live with it.

zetrotrack000 · 07-10-2017, 12:35 PM

Quote:

No, your hard drive is fine! That would be /dev/sda — /dev/sr1 is an optical drive. Do you have a disk in the drive when you boot up?

No, dvdrom is empty.

Quote:

That error code on the USB device seems to be indicative of a very low-level problem: the computer finds the device unusable. Did you try using different ports, both USB2 and USB3? Have you tried the device on a different computer? I'd expect a fault in the device to show up more often, though, and it's strange that it should cause a lock-up. If the audio jack stopped working, it might be that the USB controller is about to go too.

These sort of occasional failings can be very difficult to track down. This computer crashes about once a month. After making sure the memory wasn't faulty, I decided to live with it.

This also happens if I plug/unplug USB device 3-4 times consistently.