BUG: scheduling while atomic: Xorg/1227/0x00000002

Hi,

Running openSUSE 13.2 and getting this logs in journalctl during every boot :

Mar 19 16:09:06 linux.site kernel: BUG: scheduling while atomic: Xorg/1227/0x00000002
Mar 19 16:09:06 linux.site kernel: Modules linked in: fuse af_packet xt_pkttype xt_LOG xt_limit vboxpci(O) vboxnetadp(O) vboxnetflt(O) ip6t_REJECT xt_tcpudp nf_conntrac
Mar 19 16:09:06 linux.site kernel:  videodev bluetooth 6lowpan_iphc sdhci_pci sdhci mmc_core snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm mei_me mei
Mar 19 16:09:06 linux.site kernel: CPU: 0 PID: 1227 Comm: Xorg Tainted: G        W  O  3.16.7-7-desktop #1
Mar 19 16:09:06 linux.site kernel: Hardware name: LENOVO 20BHS1840T/20BHS1840T, BIOS GNET70WW (2.18 ) 01/12/2015
Mar 19 16:09:06 linux.site kernel:  c0ccbcc0 e8ba9848 c078e13f 00000000 c078a777 c0938248 f6976480 000004cb
Mar 19 16:09:06 linux.site kernel:  00000002 e8ba98c8 c0790c8b 00000080 c02bc350 00000080 c0cb0880 c0cb0f80
Mar 19 16:09:06 linux.site kernel:  00000000 c0cb0880 ed5f5fc4 ed5f5880 f6976090 00000000 e8ba9888 c02bc3fb
Mar 19 16:09:06 linux.site kernel: Call Trace:
Mar 19 16:09:06 linux.site kernel:  <c0205df6>] try_stack_unwind+0x156/0x170
Mar 19 16:09:06 linux.site kernel:  <c020482a>] dump_trace+0x5a/0x1b0
Mar 19 16:09:06 linux.site kernel:  <c0205e56>] show_trace_log_lvl+0x46/0x50
Mar 19 16:09:06 linux.site kernel:  <c02049d1>] show_stack_log_lvl+0x51/0xe0
Mar 19 16:09:06 linux.site kernel:  <c0205eb7>] show_stack+0x27/0x50
Mar 19 16:09:06 linux.site kernel:  <c078e13f>] dump_stack+0x45/0x65
Mar 19 16:09:06 linux.site kernel:  <c078a777>] __schedule_bug+0x54/0x63
Mar 19 16:09:06 linux.site kernel:  <c0790c8b>] __schedule+0x70b/0x790
Mar 19 16:09:06 linux.site kernel:  <c079009b>] schedule_timeout+0x12b/0x260
Mar 19 16:09:06 linux.site kernel:  <f7a2f7e1>] intel_dp_aux_ch+0x441/0x5d0 [i915]
Mar 19 16:09:06 linux.site kernel:  <f7a2fa1e>] intel_dp_aux_transfer+0xae/0x170 [i915]
Mar 19 16:09:06 linux.site kernel:  <f76a4ac8>] drm_dp_dpcd_access+0x48/0xe0 [drm_kms_helper]
Mar 19 16:09:06 linux.site kernel:  <f76a4c72>] drm_dp_dpcd_write+0x22/0x30 [drm_kms_helper]
Mar 19 16:09:06 linux.site kernel:  <f7a315f0>] intel_dp_start_link_train+0x60/0x270 [i915]
Mar 19 16:09:06 linux.site kernel:  <f7a318e0>] intel_dp_complete_link_train+0xe0/0x2f0 [i915]
Mar 19 16:09:06 linux.site kernel:  <f7a2a540>] intel_ddi_pre_enable+0x110/0x190 [i915]
Mar 19 16:09:06 linux.site kernel:  <f7a14b82>] haswell_crtc_enable+0x332/0x930 [i915]
Mar 19 16:09:06 linux.site kernel:  <f7a17bed>] __intel_set_mode+0x6cd/0x940 [i915]
Mar 19 16:09:06 linux.site kernel:  <f7a1ac73>] intel_set_mode+0x23/0x40 [i915]
Mar 19 16:09:06 linux.site kernel:  <f7a1b984>] intel_crtc_set_config+0x7c4/0xba0 [i915]
Mar 19 16:09:06 linux.site kernel:  <f77a26de>] drm_mode_set_config_internal+0x4e/0xb0 [drm]
Mar 19 16:09:06 linux.site kernel:  <f76a667a>] restore_fbdev_mode+0xaa/0xe0 [drm_kms_helper]
Mar 19 16:09:06 linux.site kernel:  <f76a66cd>] drm_fb_helper_restore_fbdev_mode_unlocked+0x1d/0x30 [drm_kms_helper]
Mar 19 16:09:06 linux.site kernel:  <f76a7fc6>] drm_fb_helper_set_par+0x26/0x60 [drm_kms_helper]
Mar 19 16:09:06 linux.site kernel:  <c052856d>] fb_set_var+0x1bd/0x410
Mar 19 16:09:06 linux.site kernel:  <c051fefe>] fbcon_blank+0x1ee/0x2e0
Mar 19 16:09:06 linux.site kernel:  <c0594cb9>] do_unblank_screen+0x99/0x1a0
Mar 19 16:09:06 linux.site kernel:  <c058c839>] vt_ioctl+0x499/0x1020
Mar 19 16:09:06 linux.site kernel:  <c05822e3>] tty_ioctl+0x233/0xa00
Mar 19 16:09:06 linux.site kernel:  <c0396692>] do_vfs_ioctl+0x2f2/0x4f0
Mar 19 16:09:06 linux.site kernel:  <c03968f0>] SyS_ioctl+0x60/0x90
Mar 19 16:09:06 linux.site kernel:  <c0794343>] sysenter_do_call+0x12/0x12
Mar 19 16:09:06 linux.site kernel:  <b7713e4c>] 0xb7713e4b


Where do I report this ?

Is this an upgrade or new install?
Nowadays, typically the xorg config file should be non-existent and might exist mainly because your system was upgraded from when the file was used.

If xorg.conf exists, you might try disabling it (eg moving the file to a different location) and rebooting.

If the problem persists, create a bug at
https://bugzilla.opensuse.org

TSU

It’s a new install but updated to the latest packages. There is no xorg.conf unless it was created during install.

Apart from the messages, is there any impact on performance or usability evident?

Not that I’ve noticed. The PC crashes tough when removing it from or puting back into docking station. I still haven’t cought the kernel crashinfo but as far as I’ve seen it’s a kernel bug at …/arch/x86/mm/highmem_32.c:18!

I don’t know if it’s releated to this scheduling while atomic but I’m guessing it’s not.

Just for reference before reporting this issue I contacted ibm-acpi-develatlists.sourceforge.net because it seemed related to graphics and also I saw this message in logs :

Apr 13 11:03:18 linux kernel: thinkpad_acpi: Lenovo ThinkPad W540, model 20BHS1840T
Apr 13 11:03:18 linux kernel: thinkpad_acpi: Unsupported brightness interface, please contact ibm-acpi-develatlists.sourceforge.net

And this was the response I received :

You can just ignore this, it is likely going to be fixed in Linux 4.1,
and anyway it is to be handled by the GPU drivers, not thinkpad-acpi.

So I went ahead and ugraded the kernel to the latest version from :
http://download.opensuse.org/repositories/Kernel:/stable/standard/

Currently running on :

linux:~ # uname -a
Linux linux.site 3.19.3-3.g0f5134a-desktop #1 SMP PREEMPT Wed Apr 8 13:45:02 UTC 2015 (0f5134a) i686 i686 i386 GNU/Linux

and I’m no longer observing those scheduling as atomic errors. Also what is even better it fixed another issue where only 1 external monitor was recognized when connected to the docking station. Now I can use them both :slight_smile: