Kernel Bug

[marco93]

Mir ist die letzten Woche nun schon zweimal das System kurz nach dem Einloggen eingefroren In beiden Fällen sehe ich das hier:

[drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:42:pipe A] flip_done timed out

Ist das definitiv ein Kernel Bug und sollte man den melden?

Jul 26 20:26:21 marco-MS-7817 kernel: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:42:pipe A] flip_done timed out
Jul 26 20:26:22 marco-MS-7817 systemd[1]: systemd-fsckd.service: Succeeded.
Jul 26 20:26:21 marco-MS-7817 systemd-timesyncd[667]: Initial synchronization to time server 91.189.94.4:123 (ntp.ubuntu.com).
Jul 26 20:26:21 marco-MS-7817 systemd[1]: Starting Daily apt upgrade and clean activities...
Jul 26 20:26:21 marco-MS-7817 systemd[1]: systemd-hostnamed.service: Succeeded.
Jul 26 20:26:22 marco-MS-7817 systemd[1]: blueman-mechanism.service: Succeeded.
Jul 26 20:26:23 marco-MS-7817 systemd[1]: apt-daily-upgrade.service: Succeeded.
Jul 26 20:26:23 marco-MS-7817 systemd[1]: Finished Daily apt upgrade and clean activities.
Jul 26 20:26:27 marco-MS-7817 autojack[2631]: JACK MIDI <-> ALSA sequencer MIDI bridge, version 9 built on Sun Oct 13 18:36:50 2019
Jul 26 20:26:27 marco-MS-7817 autojack[2631]: Copyright 2006,2007 Dmitry S. Baikov
Jul 26 20:26:27 marco-MS-7817 autojack[2631]: Copyright 2007,2008,2009,2011,2012 Nedko Arnaudov
Jul 26 20:26:27 marco-MS-7817 autojack[2631]: Bridge starting...
Jul 26 20:26:27 marco-MS-7817 autojack[2631]: Using JACK server 'default'
Jul 26 20:26:27 marco-MS-7817 autojack[2631]: Hardware ports will be exported.
Jul 26 20:26:32 marco-MS-7817 autojack[2631]: Cannot read socket fd = 6 err = Success
Jul 26 20:26:32 marco-MS-7817 autojack[2631]: CheckRes error
Jul 26 20:26:32 marco-MS-7817 autojack[2631]: JackSocketClientChannel read fail
Jul 26 20:26:32 marco-MS-7817 autojack[2631]: Cannot open a2j client
Jul 26 20:26:32 marco-MS-7817 autojack[2631]: JackShmReadWritePtr1::~JackShmReadWritePtr1 - Init not done for -1, skipping unlock
Jul 26 20:26:32 marco-MS-7817 autojack[2631]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Jul 26 20:26:32 marco-MS-7817 autojack[2631]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
Jul 26 20:26:32 marco-MS-7817 autojack[2631]: ERROR: a2j_jack_client_create: Cannot create jack client
Jul 26 20:26:32 marco-MS-7817 autojack[2631]: ERROR: a2j_start: a2j_new() failed.
Jul 26 20:27:04 marco-MS-7817 kernel: rcu: INFO: rcu_preempt self-detected stall on CPU
Jul 26 20:27:04 marco-MS-7817 kernel: rcu:         0-....: (60004 ticks this GP) idle=7ca/1/0x4000000000000002 softirq=23094/23094 fqs=14881
Jul 26 20:27:04 marco-MS-7817 kernel:         (t=60000 jiffies g=11765 q=87882)
Jul 26 20:27:04 marco-MS-7817 kernel: NMI backtrace for cpu 0
Jul 26 20:27:04 marco-MS-7817 kernel: CPU: 0 PID: 2446 Comm: jackdbus Tainted: G           OE     5.4.0-77-lowlatency #86-Ubuntu
Jul 26 20:27:04 marco-MS-7817 kernel: Hardware name: MSI MS-7817/H81M-E34 (MS-7817), BIOS V17.5 03/30/2015
Jul 26 20:27:04 marco-MS-7817 kernel: Call Trace:
Jul 26 20:27:04 marco-MS-7817 kernel:  <IRQ>
Jul 26 20:27:04 marco-MS-7817 kernel:  dump_stack+0x6d/0x8b
Jul 26 20:27:04 marco-MS-7817 kernel:  ? lapic_can_unplug_cpu+0x80/0x80
Jul 26 20:27:04 marco-MS-7817 kernel:  nmi_cpu_backtrace.cold+0x14/0x53
Jul 26 20:27:04 marco-MS-7817 kernel:  nmi_trigger_cpumask_backtrace+0xfa/0x110
Jul 26 20:27:04 marco-MS-7817 kernel:  arch_trigger_cpumask_backtrace+0x19/0x20
Jul 26 20:27:04 marco-MS-7817 kernel:  rcu_dump_cpu_stacks+0x99/0xcb
Jul 26 20:27:04 marco-MS-7817 kernel:  rcu_sched_clock_irq.cold+0x25e/0x4f0
Jul 26 20:27:04 marco-MS-7817 kernel:  update_process_times+0x2c/0x60
Jul 26 20:27:04 marco-MS-7817 kernel:  tick_sched_handle+0x29/0x60
Jul 26 20:27:04 marco-MS-7817 kernel:  tick_sched_timer+0x3d/0x80
Jul 26 20:27:04 marco-MS-7817 kernel:  __hrtimer_run_queues+0xf7/0x2c0
Jul 26 20:27:04 marco-MS-7817 kernel:  ? tick_sched_do_timer+0x60/0x60
Jul 26 20:27:04 marco-MS-7817 kernel:  hrtimer_interrupt+0x109/0x220
Jul 26 20:27:04 marco-MS-7817 kernel:  smp_apic_timer_interrupt+0x71/0x170
Jul 26 20:27:04 marco-MS-7817 kernel:  apic_timer_interrupt+0xf/0x20
Jul 26 20:27:04 marco-MS-7817 kernel:  </IRQ>
Jul 26 20:27:04 marco-MS-7817 kernel: RIP: 0010:read_tsc+0x3/0x10
Jul 26 20:27:04 marco-MS-7817 kernel: Code: 5d c3 90 90 90 90 90 8b 05 66 e0 80 01 c3 66 0f 1f 84 00 00 00 00 00 c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 0f 01 f9 <66> 90 48 c1 e2 20 48 09 d0 c.3 0f 1f 00 8b 0d ea 83 ae 01 48 89 f8
Jul 26 20:27:04 marco-MS-7817 kernel: RSP: 0018:ffffb32e40e5bea8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
Jul 26 20:27:04 marco-MS-7817 kernel: RAX: 00000000068f6570 RBX: ffffb32e40e5bf00 RCX: 0000000000000000
Jul 26 20:27:04 marco-MS-7817 kernel: RDX: 0000000000000044 RSI: 000000000000001f RDI: ffffffffaf030ca0
Jul 26 20:27:04 marco-MS-7817 kernel: RBP: ffffb32e40e5bec8 R08: 0000000000000000 R09: 0000000000000000
Jul 26 20:27:04 marco-MS-7817 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
Jul 26 20:27:04 marco-MS-7817 kernel: R13: 00000000000248f4 R14: 0000000000000000 R15: 0000000000000000
Jul 26 20:27:04 marco-MS-7817 kernel:  ? recalibrate_cpu_khz+0x10/0x10
Jul 26 20:27:04 marco-MS-7817 kernel:  ? ktime_get_ts64+0x4c/0xe0
Jul 26 20:27:04 marco-MS-7817 kernel:  poll_select_set_timeout+0x50/0x80
Jul 26 20:27:04 marco-MS-7817 kernel:  __x64_sys_poll+0x97/0x150
Jul 26 20:27:04 marco-MS-7817 kernel:  do_syscall_64+0x57/0x190
Jul 26 20:27:04 marco-MS-7817 kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jul 26 20:27:04 marco-MS-7817 kernel: RIP: 0033:0x7f8d053a4aff
Jul 26 20:27:04 marco-MS-7817 kernel: Code: 54 24 1c 48 89 74 24 10 48 89 7c 24 08 e8 79 1c f8 ff 8b 54 24 1c 48 8b 74 24 10 41 89 c0 48 8b 7c 24 08 b8 07 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2b 44 89 c7 89 44 24 08 e8 ad 1c f8 ff 8b 44
Jul 26 20:27:04 marco-MS-7817 kernel: RSP: 002b:00007f8d04626d50 EFLAGS: 00000246 ORIG_RAX: 0000000000000007
Jul 26 20:27:04 marco-MS-7817 kernel: RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007f8d053a4aff
Jul 26 20:27:04 marco-MS-7817 kernel: RDX: 0000000000007cff RSI: 0000000000000002 RDI: 000055a45ca1eec0
Jul 26 20:27:04 marco-MS-7817 kernel: RBP: 000000000484ea79 R08: 0000000000000002 R09: 00007f8d04626d58
Jul 26 20:27:04 marco-MS-7817 kernel: R10: 00007f8d04626d50 R11: 0000000000000246 R12: 0000000000000001
Jul 26 20:27:04 marco-MS-7817 kernel: R13: 0000000000000001 R14: 00000000ffffffff R15: 000055a45ca86070
Jul 26 20:27:56 marco-MS-7817 systemd[1]: Starting Ubuntu Advantage APT and MOTD Messages...
Jul 26 20:27:56 marco-MS-7817 systemd[1]: ua-messaging.service: Succeeded.
Jul 26 20:27:56 marco-MS-7817 systemd[1]: Finished Ubuntu Advantage APT and MOTD Messages.
Jul 26 20:28:00 marco-MS-7817 kernel: usb 5-1.3.4: USB disconnect, device number 8

 

[zenobic]

Das sieht so aus als hängt es mit dem Jack Client oder Daemon zusammen.
Hast du es mal ohne autojack versucht?

 

[recliq]

Melden kann man das, schaden kann es nicht... Im schlimmsten Fall wirds geschlossen oder nicht bearbeitet.
Welche Distro? Welcher Kernel?

PS: seh grad ubuntu im log... Viel erfolg, ich hab leider keine guten erfahrungen mit bugreports bei ubuntu...

 

[haebbmaster]

Wenn jack rumzickt muss es nicht immer gleich der Kernel sein.

Außerdem, 5.4? Bevor ich da was melde würde ich erstmal ein Update probieren.

Edit: die Meldung kommt ja nicht vom Kernel, sondern von autojack

 

[marco93]

Wo seht ihr denn, dass es an Jack liegt?

[drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:42:pipe A] flip_done timed out hat irgendwas mit der Graphik zu tun sagt mir google.

--> hab es schon gemeldet, aber vermutlich im falschen Bereich: https://bugs.launchpad.net/ubuntu/+bug/1938076

 

[zenobic]

Wo seht ihr denn, dass es an Jack liegt?

Sorry, ich habe den Error nicht in der ersten zeile gesehen...

Könnte am drm-kms-helper liegen:

Boot very slow because of drm_kms_helper errors

I just installed 16.04 on my MacBook Air, and everything seems to work well, except booting the system. I've been going through the dmesg-log and found out that drm_kms_helper-errors occur repeated...

askubuntu.com

 

[marco93]

Sorry, ich habe den Error nicht in der ersten zeile gesehen...

Könnte am drm-kms-helper liegen:

Boot very slow because of drm_kms_helper errors

I just installed 16.04 on my MacBook Air, and everything seems to work well, except booting the system. I've been going through the dmesg-log and found out that drm_kms_helper-errors occur repeated...

askubuntu.com

Ja genau, aber die user betraf es nur beim Booten. Ich kann mich ja anmelden. Dann erst friert es nach einigen Sekunden.