LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 06-01-2020, 04:09 PM   #1
shuv1t
LQ Newbie
 
Registered: May 2020
Distribution: Manjaro
Posts: 26

Rep: Reputation: 1
Debian 10.4 crash, syslog.1 inside - need help reading the data


My system froze after being idle for a while. I don't think what apps I had open is important but if it is then I'll add that later. When I tried interacting I could move the mouse around but clicks didn't do anything, nor did my keyboard shortcuts. This is the snippet from syslog.1 that shows the crash (20:35:54) and some afk time until I hard reset (23:05:21)

Code:
May 31 20:35:54 debian kernel: [214213.676750] xhci_hcd 0000:08:00.3: xHCI host not responding to stop endpoint command.
May 31 20:35:54 debian kernel: [214213.692757] xhci_hcd 0000:08:00.3: Host halt failed, -110
May 31 20:35:54 debian kernel: [214213.692758] xhci_hcd 0000:08:00.3: xHCI host controller not responding, assume dead
May 31 20:35:54 debian kernel: [214213.692785] xhci_hcd 0000:08:00.3: HC died; cleaning up
May 31 20:35:54 debian kernel: [214213.692856] usb 5-2: USB disconnect, device number 2
May 31 20:36:00 debian kernel: [214219.480769] rcu: INFO: rcu_sched self-detected stall on CPU
May 31 20:36:00 debian kernel: [214219.480777] rcu:     11-....: (5249 ticks this GP) idle=1ce/1/0x4000000000000002 softirq=5108446/5108446 fqs=2623 
May 31 20:36:00 debian kernel: [214219.480779] rcu:      (t=5250 jiffies g=12668021 q=233)
May 31 20:36:00 debian kernel: [214219.480783] NMI backtrace for cpu 11
May 31 20:36:00 debian kernel: [214219.480786] CPU: 11 PID: 21913 Comm: ThreadPoolForeg Tainted: P           OE     4.19.0-9-amd64 #1 Debian 4.19.118-2
May 31 20:36:00 debian kernel: [214219.480787] Hardware name: System manufacturer System Product Name/TUF B350M-PLUS GAMING, BIOS 4602 03/08/2019
May 31 20:36:00 debian kernel: [214219.480787] Call Trace:
May 31 20:36:00 debian kernel: [214219.480790]  <IRQ>
May 31 20:36:00 debian kernel: [214219.480796]  dump_stack+0x66/0x90
May 31 20:36:00 debian kernel: [214219.480799]  nmi_cpu_backtrace.cold.4+0x13/0x50
May 31 20:36:00 debian kernel: [214219.480803]  ? lapic_can_unplug_cpu.cold.31+0x37/0x37
May 31 20:36:00 debian kernel: [214219.480805]  nmi_trigger_cpumask_backtrace+0xf9/0xfb
May 31 20:36:00 debian kernel: [214219.480808]  rcu_dump_cpu_stacks+0x9b/0xcb
May 31 20:36:00 debian kernel: [214219.480810]  rcu_check_callbacks.cold.81+0x1db/0x335
May 31 20:36:00 debian kernel: [214219.480813]  ? tick_sched_do_timer+0x60/0x60
May 31 20:36:00 debian kernel: [214219.480815]  update_process_times+0x28/0x60
May 31 20:36:00 debian kernel: [214219.480817]  tick_sched_handle+0x22/0x60
May 31 20:36:00 debian kernel: [214219.480818]  tick_sched_timer+0x37/0x70
May 31 20:36:00 debian kernel: [214219.480820]  __hrtimer_run_queues+0x100/0x280
May 31 20:36:00 debian kernel: [214219.480823]  hrtimer_interrupt+0x100/0x220
May 31 20:36:00 debian kernel: [214219.480826]  smp_apic_timer_interrupt+0x6a/0x140
May 31 20:36:00 debian kernel: [214219.480827]  apic_timer_interrupt+0xf/0x20
May 31 20:36:00 debian kernel: [214219.480829]  </IRQ>
May 31 20:36:00 debian kernel: [214219.480831] RIP: 0010:smp_call_function_many+0x1f8/0x250
May 31 20:36:00 debian kernel: [214219.480832] Code: c7 e8 9c 4e 5f 00 3b 05 fa 5c 01 01 0f 83 8c fe ff ff 48 63 d0 48 8b 0b 48 03 0c d5 20 c7 8e ba 8b 51 18 $
May 31 20:36:00 debian kernel: [214219.480834] RSP: 0018:ffffaa14893e7d18 EFLAGS: 00000202 ORIG_RAX: ffffffffffffff13
May 31 20:36:00 debian kernel: [214219.480835] RAX: 0000000000000006 RBX: ffff8a034e8e3080 RCX: ffff8a034e7a7320
May 31 20:36:00 debian kernel: [214219.480836] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff8a034e8e3088
May 31 20:36:00 debian kernel: [214219.480837] RBPMay 31 23:05:21 debian systemd[1]: Starting Flush Journal to Persistent Storage...
May 31 23:05:21 debian systemd-tmpfiles[401]: [/usr/lib/tmpfiles.d/speech-dispatcher.conf:1] Line references path below legacy directory /var/run/ [...]
After googling xhci_hcd failure and seeing usb 5-2: USB disconnect I assume this error is related to one of my USB devices.

My question is; can I gather anything more than just that from these logs?

Last edited by shuv1t; 06-01-2020 at 04:10 PM.
 
Old 06-01-2020, 08:58 PM   #2
JeremyBoden
Senior Member
 
Registered: Nov 2011
Location: London, UK
Distribution: Debian
Posts: 1,730

Rep: Reputation: 377Reputation: 377Reputation: 377Reputation: 377
I'd suggest that the
Code:
rcu: INFO: rcu_sched self-detected stall on CPU
which took place about 6 seconds after the USB event is likely to be the cause (and not necessarily connected with the USB message).

If you can't replicate it, then its very hard to fix.
 
1 members found this post helpful.
Old 06-01-2020, 09:34 PM   #3
cordx
Member
 
Registered: Oct 2018
Location: texas
Distribution: bodhi 5.1.0
Posts: 580

Rep: Reputation: 144Reputation: 144
agreed that if you can't reproduce the error, it will be hard to troubleshoot.

you might get a more rounded picture of what was going on at the time with other log viewers like journalctl or dmesg. dmesg -H --level=err (=warn is also an option. you can use both with =err,warn). journalctl has a similar -p option where you can look at different priority levels like ""emerg" (0), "alert" (1), "crit" (2), "err" (3), "warning" (4), "notice" (5), "info" (6), "debug" (7)" (from the man page) as well as a way to filter for a certain time with --since and --until as shown on the page in the link.
 
Old 06-01-2020, 10:39 PM   #4
shuv1t
LQ Newbie
 
Registered: May 2020
Distribution: Manjaro
Posts: 26

Original Poster
Rep: Reputation: 1
Thank you for the replies. journalctl wouldn't show me anything from before the reset, dmesg returned "Watchdog hardware is disabled" error - also from after reset. I'm fine with the crash as long as it doesn't repeat, and if it does that makes it more likely I'll be able to pinpoint the cause.

Last edited by shuv1t; 06-01-2020 at 11:13 PM.
 
1 members found this post helpful.
Old 06-01-2020, 10:47 PM   #5
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 18,881

Rep: Reputation: 3204Reputation: 3204Reputation: 3204Reputation: 3204Reputation: 3204Reputation: 3204Reputation: 3204Reputation: 3204Reputation: 3204Reputation: 3204Reputation: 3204
Something plugged into USB3 didn't like not being answered. If you're lucky it might just be an unlikely coincidence.
 
  


Reply


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
crash () { crash|crash& }; crash grob115 Linux - Security 6 05-07-2011 03:06 AM
I need help getting syslog to log remotely, this is just the regular syslog. abefroman Linux - Software 2 06-05-2008 11:36 AM
iptables inside client to inside host with outside DNS or IP - Help! linuxhelp2 Linux - Networking 1 10-15-2005 06:19 AM
Crash, Crash, Crash, Crash and You Guessed it Crash! little_penguin SUSE / openSUSE 8 07-04-2005 09:34 AM
xmms crash xine crash mplayer crash paledread Linux - Software 9 03-09-2004 07:09 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 11:31 AM.

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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration