LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 01-19-2020, 05:27 PM   #1
Mikech
Member
 
Registered: Jan 2006
Location: USA
Distribution: Mint
Posts: 90

Rep: Reputation: 24
How do I interpret dmesg errors?


Problem: I ran dmesg to see if the driver for my Hauupage Live 2 was loading (I am trying to get that to work with Linux but I do not want any help with that at this stage - or I won't learn anything). Too my surprise the thing is riddled with error messages in red on the terminal. What Iam asking is given examples of some of these errors, do they matter and if so how to fix them.

Results of LSPCI

Code:
00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 0d)
00:02.0 VGA compatible controller: Intel Corporation Device 3e98 (rev 02)
00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10)
00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10)
00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10)
00:14.3 Network controller: Intel Corporation Wireless-AC 9560 [Jefferson Peak] (rev 10)
00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10)
00:17.0 RAID bus controller: Intel Corporation SATA Controller [RAID mode] (rev 10)
00:1b.0 PCI bridge: Intel Corporation Device a340 (rev f0)
00:1b.4 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port 21 (rev f0)
00:1c.0 PCI bridge: Intel Corporation Device a338 (rev f0)
00:1c.6 PCI bridge: Intel Corporation Device a33e (rev f0)
00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port 9 (rev f0)
00:1f.0 ISA bridge: Intel Corporation Device a305 (rev 10)
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (7) I219-V (rev 10)
01:00.0 Non-Volatile memory controller: Device 1cc1:8201 (rev 03)
02:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller
 04:00.0 SATA controller: Marvell Technology Group Ltd. Device 9215 (rev 11)
Here are some selected errors of the many:




Code:
11348.109427] usb 1-11.1: SerialNumber: 0014107874
[11348.139398] mc: Linux media interface: v0.10
[11348.143246] videodev: Linux video capture interface: v2.00
[11348.152500] cx231xx 1-11.1:1.1: New device Hauppauge Hauppauge Device @ 480 Mbps (2040:c200) with 6 interfaces
[11348.152544] cx231xx 1-11.1:1.1: can't change interface 3 alt no. to 3: Max. Pkt size = 0
[11348.152546] cx231xx 1-11.1:1.1: Identified as Hauppauge USB Live 2 (card=9)
[11348.152747] i2c i2c-5: Added multiplexed i2c bus 7
[11348.152785] i2c i2c-5: Added multiplexed i2c bus 8cx25840 4-0044: cx23102 A/V decoder found @ 0x88 (cx231xx #0-0)
[11350.245775] cx25840 4-0044: loaded v4l-cx231xx-avcore-01.fw firmware (16382 bytes)
[11350.280225] cx231xx 1-11.1:1.1: v4l2 driver version 0.0.3
[11350.379061] cx231xx 1-11.1:1.1: Registered video device video0 [v4l2]
[11350.379279] cx231xx 1-11.1:1.1: Registered VBI device vbi0
[11350.379285] cx231xx 1-11.1:1.1: video EndPoint Addr 0x84, Alternate settings: 5
[11350.379289] cx231xx 1-11.1:1.1: VBI EndPoint Addr 0x85, Alternate settings: 2
[11350.379292] cx231xx 1-11.1:1.1: sliced CC EndPoint Addr 0x86, Alternate settings: 2
[11350.379660] usbcore: registered new interface driver cx231xx
[11350.386038] cx231xx 1-11.1:1.1: audio EndPoint Addr 0x83, Alternate settings: 3
[11350.386039] cx231xx 1-11.1:1.1: Cx231xx Audio Extension initialized
[11350.828304] usb 1-11.1: USB disconnect, device number 14
[11360.184170] [UFW BLOCK] IN=eno2 OUT= MAC=01:00:5e:00:00:01:5c:e2:8c:e0:af:40:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 
[11398.602110] [UFW BLOCK] IN=eno2 OUT= MAC=b4:2e:99:c6:53:f2:5c:e2:8c:e0:af:40:08:00 SRC=192.168.0.1 DST=192.168.0.36 LEN=71 TOS=0x00 PREC=0x00 TTL=64 ID=0 PROTO=UDP SPT=48186 DPT=5353 LEN=51 
[11480.282483] INFO: task kworker/2:1:151 blocked for more than 120 seconds.
[11480.282492]       Tainted: G           OE     5.3.0-26-generic #28~18.04.1-Ubuntu
[11480.282494] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[11480.282498] kworker/2:1     D    0   151      2 0x80004000
[11480.282510] Workqueue: usb_hub_wq hub_event
[11480.282513] Call Trace:
[11480.282522]  __schedule+0x2a8/0x670
[11480.282527]  schedule+0x33/0xa0
[11480.282532]  schedule_timeout+0x1d3/0x2f0
[11480.282537]  ? __wake_up_common_lock+0x8c/0xc0
[11480.282542]  wait_for_completion+0xba/0x140
[11480.282548]  ? wake_up_q+0x80/0x80
[11480.282562]  snd_card_free+0x6f/0x90 [snd]
[11480.282570]  cx231xx_audio_fini+0x2f/0x50 [cx231xx_alsa]
[11480.282585]  cx231xx_close_extension+0x4b/0x70 [cx231xx]
[11480.282596]  cx231xx_usb_disconnect+0x76/0x120 [cx231xx]
[11480.282603]  usb_unbind_interface+0x7f/0x260
[11480.282609]  device_release_driver_internal+0xe0/0x1b0
[11480.282612]  device_release_driver+0x12/0x20
[11480.282618]  bus_remove_device+0xe1/0x150
[11480.282623]  device_del+0x16a/0x3a0
[11480.282627]  ? usb_remove_ep_devs+0x1f/0x30
[11480.282632]  usb_disable_device+0x9f/0x250
[11480.282636]  usb_disconnect+0xc6/0x270
[11480.282640]  hub_port_connect+0x81/0x9f0
[11480.282644]  port_event+0x67a/0x7e0
[11480.282649]  ? __switch_to_asm+0x40/0x70
[11480.282654]  hub_event+0x21e/0x3b0
[11480.282661]  process_one_work+0x1fd/0x3f0
[11480.282667]  worker_thread+0x34/0x410
[11480.282671]  kthread+0x121/0x140
[11480.282676]  ? process_one_work+0x3f0/0x3f0
[11480.282679]  ? kthread_park+0xb0/0xb0
[11480.282683]  ret_from_fork+0x1f/0x40
[11480.282730] INFO: task alsa-source-Cx2:4766 blocked for more than 120 seconds.
[11480.282734]       Tainted: G           OE     5.3.0-26-generic #28~18.04.1-Ubuntu
[11480.282737] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[11480.282740] alsa-source-Cx2 D    0  4766      1 0x00004000
[11480.282744] Call Trace:
[11480.282748]  __schedule+0x2a8/0x670
[11480.282753]  ? __switch_to_asm+0x34/0x70
[11480.282756]  schedule+0x33/0xa0
[11480.282760]  schedule_preempt_disabled+0xe/0x10
[11480.282764]  __mutex_lock.isra.9+0x26d/0x4e0
[11480.282770]  ? radix_tree_lookup+0xd/0x10
[11480.282774]  __mutex_lock_slowpath+0x13/0x20
[11480.282777]  ? __mutex_lock_slowpath+0x13/0x20
[11480.282780]  mutex_lock+0x2f/0x40
[11480.282786]  snd_cx231xx_pcm_close+0x2d/0x1c0 [cx231xx_alsa]
[11480.282798]  snd_pcm_release_substream.part.46+0x5c/0xb0 [snd_pcm]
[11480.282808]  snd_pcm_release+0xa7/0xb0 [snd_pcm]
[11480.282817]  snd_disconnect_release+0xa6/0xe0 [snd]
[11480.282823]  __fput+0xc6/0x260
[11480.282828]  ____fput+0xe/0x10
[11480.282833]  task_work_run+0x9d/0xc0
[11480.282840]  exit_to_usermode_loop+0x109/0x130
[11480.282845]  do_syscall_64+0x115/0x130
[11480.282851]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[11480.282855] RIP: 0033:0x7f4ae4848ab7
[11480.282863] Code: Bad RIP value.
[11480.282865] RSP: 002b:00007f4a9f5cbc28 EFLAGS: 00000202 ORIG_RAX: 000000000000000b
[11480.282869] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f4ae4848ab7
[11480.282872] RDX: 0000000000000010 RSI: 0000000000001000 RDI: 00007f4ae6749000
[11480.282873] RBP: 000055f648ad48d0 R08: 00007f4ad7390018 R09: 00007f4a9f5cbb40
[11480.282876] R10: 00000000fffffff8 R11: 0000000000000202 R12: 000055f648ad48d0
[11480.282878] R13: 000055f648ad48d0 R14: 0000000000000000 R15: 000055f648ab6d20
[11485.195483] [UFW BLOCK] IN=eno2 OUT= MAC=01:00:5e:00:00:01:5c:e2:8c:e0:af:40:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 
[11491.386758] [UFW BLOCK] IN=eno2 OUT= MAC=b4:2e:99:c6:53:f2:5c:e2:8c:e0:af:40:08:00 SRC=192.168.0.1 DST=192.168.0.36 LEN=71 TOS=0x00 PREC=0x00 TTL=64 ID=0 PROTO=UDP SPT=58940 DPT=5353 LEN=51 
[11552.106917] [UFW BLOCK] IN=eno2 OUT= MAC=b4:2e:99:c6:53:f2:5c:e2:8c:e0:af:40:08:00 SRC=192.168.0.1 DST=192.168.0.36 LEN=71 TOS=0x00 PREC=0x00 TTL=64 ID=0 PROTO=UDP SPT=36649 DPT=5353 LEN=51 
[11601.118158] INFO: task kworker/2:1:151 blocked for more than 241 seconds.
[11601.118166]       Tainted: G           OE     5.3.0-26-generic #28~18.04.1-Ubuntu
[11601.118168] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[11601.118172] kworker/2:1     D    0   151      2 0x80004000
[11601.118184] Workqueue: usb_hub_wq hub_event
[11601.118186] Call Trace:
[11601.118196]  __schedule+0x2a8/0x670
[11601.118200]  schedule+0x33/0xa0
[11601.118205]  schedule_timeout+0x1d3/0x2f0
[11601.118211]  ? __wake_up_common_lock+0x8c/0xc0
[11601.118215]  wait_for_completion+0xba/0x140
[11601.118222]  ? wake_up_q+0x80/0x80
[11601.118236]  snd_card_free+0x6f/0x90 [snd]
[11601.118244]  cx231xx_audio_fini+0x2f/0x50 [cx231xx_alsa]
[11601.118259]  cx231xx_close_extension+0x4b/0x70 [cx231xx]
[11601.118271]  cx231xx_usb_disconnect+0x76/0x120 [cx231xx]
[11601.118277]  usb_unbind_interface+0x7f/0x260
[11601.118283]  device_release_driver_internal+0xe0/0x1b0
[11601.118287]  device_release_driver+0x12/0x20
[11601.118293]  bus_remove_device+0xe1/0x150
[11601.118298]  device_del+0x16a/0x3a0
[11601.118302]  ? usb_remove_ep_devs+0x1f/0x30
[11601.118307]  usb_disable_device+0x9f/0x250
[11601.118310]  usb_disconnect+0xc6/0x270
[11601.118315]  hub_port_connect+0x81/0x9f0
[11601.118319]  port_event+0x67a/0x7e0
[11601.118324]  ? __switch_to_asm+0x40/0x70
[11601.118328]  hub_event+0x21e/0x3b0
[11601.118336]  process_one_work+0x1fd/0x3f0
[11601.118341]  worker_thread+0x34/0x410
[11601.118345]  kthread+0x121/0x140
[11601.118350]  ? process_one_work+0x3f0/0x3f0
[11601.118353]  ? kthread_park+0xb0/0xb0
[11601.118358]  ret_from_fork+0x1f/0x40
[11601.118404] INFO: task alsa-source-Cx2:4766 blocked for more than 241 seconds.
[11601.118408]       Tainted: G           OE     5.3.0-26-generic #28~18.04.1-Ubuntu
[11601.118410] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[11601.118413] alsa-source-Cx2 D    0  4766      1 0x00004000
[11601.118417] Call Trace:
[11601.118421]  __schedule+0x2a8/0x670
[11601.118426]  ? __switch_to_asm+0x34/0x70
[11601.118430]  schedule+0x33/0xa0
[11601.118433]  schedule_preempt_disabled+0xe/0x10
[11601.118437]  __mutex_lock.isra.9+0x26d/0x4e0
[11601.118443]  ? radix_tree_lookup+0xd/0x10
[11601.118447]  __mutex_lock_slowpath+0x13/0x20
[11601.118450]  ? __mutex_lock_slowpath+0x13/0x20
[11601.118454]  mutex_lock+0x2f/0x40
[11601.118459]  snd_cx231xx_pcm_close+0x2d/0x1c0 [cx231xx_alsa]
[11601.118472]  snd_pcm_release_substream.part.46+0x5c/0xb0 [snd_pcm]
[11601.118482]  snd_pcm_release+0xa7/0xb0 [snd_pcm]
[11601.118491]  snd_disconnect_release+0xa6/0xe0 [snd]
[11601.118497]  __fput+0xc6/0x260
[11601.118501]  ____fput+0xe/0x10
[11601.118507]  task_work_run+0x9d/0xc0
[11601.118514]  exit_to_usermode_loop+0x109/0x130
[11601.118519]  do_syscall_64+0x115/0x130
[11601.118524]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[11601.118528] RIP: 0033:0x7f4ae4848ab7
[11601.118537] Code: Bad RIP value.
[11601.118539] RSP: 002b:00007f4a9f5cbc28 EFLAGS: 00000202 ORIG_RAX: 000000000000000b
[11601.118543] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f4ae4848ab7
[11601.118545] RDX: 0000000000000010 RSI: 0000000000001000 RDI: 00007f4ae6749000
[11601.118547] RBP: 000055f648ad48d0 R08: 00007f4ad7390018 R09: 00007f4a9f5cbb40
[11601.118549] R10: 00000000fffffff8 R11: 0000000000000202 R12: 000055f648ad48d0
[11601.118551] R13: 000055f648ad48d0 R14: 0000000000000000 R15: 000055f648ab6d20
[11610.206734] [UFW BLOCK] IN=eno2 OUT= MAC=01:00:5e:00:00:01:5c:e2:8c:e0:af:40:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 
[11647.037781] [UFW BLOCK] IN=eno2 OUT= MAC=b4:2e:99:c6:53:f2:5c:e2:8c:e0:af:40:08:00 SRC=192.168.0.1 DST=192.168.0.36 LEN=71 TOS=0x00 PREC=0x00 TTL=64 ID=0 PROTO=UDP SPT=46636 DPT=5353 LEN=51 
[11721.948327] INFO: task kworker/2:1:151 blocked for more than 362 seconds.
[11721.948336]       Tainted: G           OE     5.3.0-26-generic #28~18.04.1-Ubuntu
[11721.948338] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[11721.948342] kworker/2:1     D    0   151      2 0x80004000
[11721.948355] Workqueue: usb_hub_wq hub_event
[11721.948357] Call Trace:
[11721.948368]  __schedule+0x2a8/0x670
[11721.948372]  schedule+0x33/0xa0
[11721.948377]  schedule_timeout+0x1d3/0x2f0
[11721.948382]  ? __wake_up_common_lock+0x8c/0xc0
[11721.948387]  wait_for_completion+0xba/0x140
[11721.948393]  ? wake_up_q+0x80/0x80
[11721.948408]  snd_card_free+0x6f/0x90 [snd]
[11721.948416]  cx231xx_audio_fini+0x2f/0x50 [cx231xx_alsa]
[11721.948432]  cx231xx_close_extension+0x4b/0x70 [cx231xx]
[11721.948443]  cx231xx_usb_disconnect+0x76/0x120 [cx231xx]
[11721.948450]  usb_unbind_interface+0x7f/0x260
[11721.948456]  device_release_driver_internal+0xe0/0x1b0
[11721.948460]  device_release_driver+0x12/0x20
[11721.948465]  bus_remove_device+0xe1/0x150
[11721.948470]  device_del+0x16a/0x3a0
[11721.948474]  ? usb_remove_ep_devs+0x1f/0x30
[11721.948479]  usb_disable_device+0x9f/0x250
[11721.948483]  usb_disconnect+0xc6/0x270
[11721.948487]  hub_port_connect+0x81/0x9f0
[11721.948492]  port_event+0x67a/0x7e0
[11721.948497]  ? __switch_to_asm+0x40/0x70
[11721.948501]  hub_event+0x21e/0x3b0
[11721.948509]  process_one_work+0x1fd/0x3f0
[11721.948514]  worker_thread+0x34/0x410
[11721.948518]  kthread+0x121/0x140
[11721.948523]  ? process_one_work+0x3f0/0x3f0
[11721.948526]  ? kthread_park+0xb0/0xb0
[11721.948531]  ret_from_fork+0x1f/0x40
[11721.948579] INFO: task alsa-source-Cx2:4766 blocked for more than 362 seconds.
[11721.948583]       Tainted: G           OE     5.3.0-26-generic #28~18.04.1-Ubuntu
[11721.948586] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[11721.948588] alsa-source-Cx2 D    0  4766      1 0x00004000
[11721.948592] Call Trace:
[11721.948596]  __schedule+0x2a8/0x670
[11721.948601]  ? __switch_to_asm+0x34/0x70
[11721.948604]  schedule+0x33/0xa0
[11721.948608]  schedule_preempt_disabled+0xe/0x10
[11721.948612]  __mutex_lock.isra.9+0x26d/0x4e0
[11721.948618]  ? radix_tree_lookup+0xd/0x10
[11721.948622]  __mutex_lock_slowpath+0x13/0x20
[11721.948625]  ? __mutex_lock_slowpath+0x13/0x20
[11721.948628]  mutex_lock+0x2f/0x40
[11721.948634]  snd_cx231xx_pcm_close+0x2d/0x1c0 [cx231xx_alsa]
[11721.948646]  snd_pcm_release_substream.part.46+0x5c/0xb0 [snd_pcm]
[11721.948656]  snd_pcm_release+0xa7/0xb0 [snd_pcm]
[11721.948665]  snd_disconnect_release+0xa6/0xe0 [snd]
[11721.948671]  __fput+0xc6/0x260
[11721.948675]  ____fput+0xe/0x10
[11721.948681]  task_work_run+0x9d/0xc0
[11721.948688]  exit_to_usermode_loop+0x109/0x130
[11721.948693]  do_syscall_64+0x115/0x130
[11721.948699]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[11721.948703] RIP: 0033:0x7f4ae4848ab7
[11721.948711] Code: Bad RIP value.
[11721.948714] RSP: 002b:00007f4a9f5cbc28 EFLAGS: 00000202 ORIG_RAX: 000000000000000b
[11721.948718] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f4ae4848ab7
[11721.948720] RDX: 0000000000000010 RSI: 0000000000001000 RDI: 00007f4ae6749000
[11721.948722] RBP: 000055f648ad48d0 R08: 00007f4ad7390018 R09: 00007f4a9f5cbb40
[11721.948724] R10: 00000000fffffff8 R11: 0000000000000202 R12: 000055f648ad48d0
[11721.948726] R13: 000055f648ad48d0 R14: 0000000000000000 R15: 000055f648ab6d20
[11726.173141] [UFW BLOCK] IN=eno2 OUT= MAC=b4:2e:99:c6:53:f2:5c:e2:8c:e0:af:40:08:00 SRC=192.168.0.1 DST=192.168.0.36 LEN=71 TOS=0x00 PREC=0x00 TTL=64 ID=0 PROTO=UDP SPT=44451 DPT=5353 LEN=51 
[11735.218054] [UFW BLOCK] IN=eno2 OUT= MAC=01:00:5e:00:00:01:5c:e2:8c:e0:af:40:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 
[11842.787981] INFO: task kworker/2:1:151 blocked for more than 483 seconds.
[11842.787989]       Tainted: G           OE     5.3.0-26-generic #28~18.04.1-Ubuntu
[11842.787992] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[11842.787996] kworker/2:1     D    0   151      2 0x80004000
[11842.788007] Workqueue: usb_hub_wq hub_event
[11842.788010] Call Trace:
[11842.788020]  __schedule+0x2a8/0x670
[11842.788024]  schedule+0x33/0xa0
[11842.788029]  schedule_timeout+0x1d3/0x2f0
[11842.788035]  ? __wake_up_common_lock+0x8c/0xc0
[11842.788040]  wait_for_completion+0xba/0x140
[11842.788046]  ? wake_up_q+0x80/0x80
[11842.788059]  snd_card_free+0x6f/0x90 [snd]
[11842.788068]  cx231xx_audio_fini+0x2f/0x50 [cx231xx_alsa]
[11842.788083]  cx231xx_close_extension+0x4b/0x70 [cx231xx]
[11842.788095]  cx231xx_usb_disconnect+0x76/0x120 [cx231xx]
[11842.788101]  usb_unbind_interface+0x7f/0x260
[11842.788107]  device_release_driver_internal+0xe0/0x1b0
[11842.788110]  device_release_driver+0x12/0x20
[11842.788116]  bus_remove_device+0xe1/0x150
[11842.788121]  device_del+0x16a/0x3a0
[11842.788125]  ? usb_remove_ep_devs+0x1f/0x30
[11842.788130]  usb_disable_device+0x9f/0x250
[11842.788134]  usb_disconnect+0xc6/0x270
[11842.788138]  hub_port_connect+0x81/0x9f0
[11842.788143]  port_event+0x67a/0x7e0
[11842.788148]  ? __switch_to_asm+0x40/0x70
[11842.788152]  hub_event+0x21e/0x3b0
[11842.788159]  process_one_work+0x1fd/0x3f0
[11842.788165]  worker_thread+0x34/0x410
[11842.788169]  kthread+0x121/0x140
[11842.788173]  ? process_one_work+0x3f0/0x3f0
[11842.788176]  ? kthread_park+0xb0/0xb0
[11842.788181]  ret_from_fork+0x1f/0x40
[11842.788228] INFO: task alsa-source-Cx2:4766 blocked for more than 483 seconds.
[11842.788233]       Tainted: G           OE     5.3.0-26-generic #28~18.04.1-Ubuntu
[11842.788235] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[11842.788238] alsa-source-Cx2 D    0  4766      1 0x00004000
[11842.788242] Call Trace:
[11842.788246]  __schedule+0x2a8/0x670
[11842.788251]  ? __switch_to_asm+0x34/0x70
[11842.788254]  schedule+0x33/0xa0
[11842.788258]  schedule_preempt_disabled+0xe/0x10
[11842.788262]  __mutex_lock.isra.9+0x26d/0x4e0
[11842.788268]  ? radix_tree_lookup+0xd/0x10
[11842.788273]  __mutex_lock_slowpath+0x13/0x20
[11842.788276]  ? __mutex_lock_slowpath+0x13/0x20
[11842.788279]  mutex_lock+0x2f/0x40
[11842.788285]  snd_cx231xx_pcm_close+0x2d/0x1c0 [cx231xx_alsa]
[11842.788297]  snd_pcm_release_substream.part.46+0x5c/0xb0 [snd_pcm]
[11842.788306]  snd_pcm_release+0xa7/0xb0 [snd_pcm]
[11842.788316]  snd_disconnect_release+0xa6/0xe0 [snd]
[11842.788322]  __fput+0xc6/0x260
[11842.788327]  ____fput+0xe/0x10
[11842.788333]  task_work_run+0x9d/0xc0
[11842.788339]  exit_to_usermode_loop+0x109/0x130
[11842.788345]  do_syscall_64+0x115/0x130
[11842.788350]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[11842.788354] RIP: 0033:0x7f4ae4848ab7
[11842.788363] Code: Bad RIP value.
[11842.788365] RSP: 002b:00007f4a9f5cbc28 EFLAGS: 00000202 ORIG_RAX: 000000000000000b
[11842.788369] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f4ae4848ab7
[11842.788371] RDX: 0000000000000010 RSI: 0000000000001000 RDI: 00007f4ae6749000
[11842.788373] RBP: 000055f648ad48d0 R08: 00007f4ad7390018 R09: 00007f4a9f5cbb40
[11842.788375] R10: 00000000fffffff8 R11: 0000000000000202 R12: 000055f648ad48d0
[11842.788377] R13: 000055f648ad48d0 R14: 0000000000000000 R15: 000055f648ab6d20
[11860.229328] [UFW BLOCK] IN=eno2 OUT= MAC=01:00:5e:00:00:01:5c:e2:8c:e0:af:40:08:00 SRC=192.168.0.1 DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0x00 TTL=1 ID=0 DF PROTO=2 
[11928.725915] [UFW BLOCK] IN=eno2 OUT= MAC=b4:2e:99:c6:53:f2:5c:e2:8c:e0:af:40:08:00 SRC=192.168.0.1 DST=192.168.0.36 LEN=71 TOS=0x00 PREC=0x00 TTL=64 ID=0 PROTO=UDP SPT=59738 DPT=5353 LEN=51 
[11963.626242] INFO: task kworker/2:1:151 blocked for more than 604 seconds.
[11963.626250]       Tainted: G           OE     5.3.0-26-generic #28~18.04.1-Ubuntu
[11963.626253] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[11963.626257] kworker/2:1     D    0   151      2 0x80004000
 [
So are these bad? Will the world come to and end? Do I need to fix something?



The computer and everything in it except the Hauppage USB video capture card (because I don't have software for it yet) works fine and the machine is the fastest I ever built. So I don't get it.
 
Old 01-19-2020, 06:32 PM   #2
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,383

Rep: Reputation: 4190Reputation: 4190Reputation: 4190Reputation: 4190Reputation: 4190Reputation: 4190Reputation: 4190Reputation: 4190Reputation: 4190Reputation: 4190Reputation: 4190
The card is trying its best to bring on Armageddon. Where you see "Call Trace:" followed by a bunch of indented messages, you are looking at a kernel oops (yes, seriously; search it). They are never good.
However the kernel does its best to look after itself, and recovers till the next piece of poorly designed code causes another one. Will cause the machine to run slower, and may eventually crash, but you can continue to use the machine to get the card properly set up. After that the oops' shouldn't recur.
 
1 members found this post helpful.
Old 01-19-2020, 07:18 PM   #3
Mikech
Member
 
Registered: Jan 2006
Location: USA
Distribution: Mint
Posts: 90

Original Poster
Rep: Reputation: 24
Hee, hee, hee,,, I thought those Hauppage guys were up to no good!

You were correct. I unplugged the card, rebooted and walla! Happy little kernel again without red lines in the dmesg output. The world is saved! I guess I will just use it with my windows machine since it does not need the internet and getting it working correctly in Linux is not the best use of my time. I just have a drawer full of yoga and woodworking VHS tapes to digitize. I don't care if it breaks my Windows machine. I keep that thing for the Tv card ()because I have never been able to get one to work in Linux), games and because my document scanner needs it. The document scanner is old and the next one will be compatible with Linux.
 
Old 01-20-2020, 05:44 AM   #4
hazel
LQ Guru
 
Registered: Mar 2016
Location: Harrow, UK
Distribution: LFS, AntiX, Slackware
Posts: 8,261
Blog Entries: 21

Rep: Reputation: 4787Reputation: 4787Reputation: 4787Reputation: 4787Reputation: 4787Reputation: 4787Reputation: 4787Reputation: 4787Reputation: 4787Reputation: 4787Reputation: 4787
You could also try doing what the error messages suggest and "echo 0 > /proc/sys/kernel/hung_task_timeout_secs". It won't solve the underlying problem, whatever that is, but it will stop those pesky messages while you do the job you bought the card for.

I don't see how even a kernel crash, if it happens, is going to break your system. You already know that all will be well if you just reboot without the card.
 
1 members found this post helpful.
Old 01-20-2020, 01:29 PM   #5
Mikech
Member
 
Registered: Jan 2006
Location: USA
Distribution: Mint
Posts: 90

Original Poster
Rep: Reputation: 24
HAZEL:

Thank you for the suggestion but you have underestimated my level of anal-ness, which is world class. :-)) Having worked my entire life in nuclear reactor physics (where any mistake could be catastrophic) it would be physically impossible for me to do that. I can get rid of the error message but I will know they are there. And they could manifest themselves as problems elsewhere where the kernel errors are not the obvious cause.

When I build furniture if I have made a mistake, I do it over, even if the mistake is inside and will never be seen. Believe me I have tried. But I always know it is there and it gnaws at me until I redo it.

In this case we do not know what the cause of the error is and I will not be able to use the card until I solve the problem. Its just the way I am wired. I know it works alright in Windows 7 so I am not going to spend time trying to fix it Linux. I found many sites where people had similar types of errors from dmesg (but for different hardware). No one actually knew how to fix the errors, most posts were of the "me too" variety and one guy on stack exchange said he reverted his kernel and that solved the problem for him (not a viable solution in my opinion). If all these smart people couldn't fix it I know it would be a waste of time for me to try.

Maybe we can get Linus to give us all a tutorial on it!!

Last edited by Mikech; 01-20-2020 at 01:31 PM.
 
Old 01-22-2020, 11:28 AM   #6
Mikech
Member
 
Registered: Jan 2006
Location: USA
Distribution: Mint
Posts: 90

Original Poster
Rep: Reputation: 24
Of interest to people wanting to learn about dmesg

By coincidence I received an email from a tech site I use about dmesg. Its written by Dave McKay who knows how to explain things to newbies in an understandable fashion without dumbing down the details.

https://www.howtogeek.com/449335/how...mand-on-linux/

I like Dave McKay's articles. Most articles on the internet that are written for beginners assume you are computer illiterate and are written so simplisticly as to be useless or the ones with the necessary level of technical details are written so full of linux or unix specific jargon as to be incomprehensible. After all, being a newbie doesn't mean you are computer illiterate. It just means that you are new to the intricacies and terminology of Linux and Unix.

The above article dives deep into how to read and manipulate the data from dmesg but does not go so far as to explain what the entries mean or include instructions about errors and warning. Still its a very good and possibly essential place to start. I will be using dmesg a lot more now.


One problem is that the dmesg output is huge so it is helpful to pipe to "less" or a text file. But you lose the colours and without that the files is very hard to use. Here are some websites that tell you how to keep the colour.


https://superuser.com/questions/9400...e-highlighting
https://unix.stackexchange.com/quest...colored-output

Last edited by Mikech; 01-22-2020 at 11:33 AM.
 
  


Reply

Tags
dmesg


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
How to interpret dmesg, kernel.log, etc. ? dbuehler Linux - Hardware 10 03-20-2015 07:19 AM
Difference between ouput of dmesg and content of /var/log/dmesg Sayan Acharjee Linux - General 1 09-21-2011 10:42 AM
dmesg vs /var/log/dmesg drManhattan Linux - Newbie 2 08-07-2011 05:28 AM
dmesg (command) and /var/log/dmesg are different? Oxagast Linux - Software 2 07-10-2006 05:50 AM
/bin/dmesg > /dmesg-boot not Working in Knoppix 3.4 suguru Debian 2 07-04-2004 05:21 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 06:59 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration