Changing console renders my system unresponsive

DoneSubmitted by Petter.
Details
3 participants
  • Ludovic Courtès
  • Petter
  • zimoun
Owner
unassigned
Severity
normal
P
P
Petter wrote on 25 Oct 2016 13:22
(address . bug-guix@gnu.org)
73ddf40b77af55bb11861bb3d68e024f@mykolab.ch
Hi,
I'm having a pretty dramatic experience changing console, f.ex. Ctrl+Alt+F4. My system becomes completely unresponsive. Even Alt+SysRq+reisub is unable to persuade my system to perform a gentlemans reboot. To recover I must do a hard reboot.
Bringing this up in #guix suggests it's not a common issue.
My setup is:Libreboot X200Docking stationExternal monitor connected to the docking station with DisplayPort.XFCEGuixSD (from git, last commit in my repo c11933c920dd7b7cdf68e13e6b3718602129210a)
Using DisplayPort I sometimes get the attached output. Other times I get a white underscore in the top left corner on a black background.
Now, if I change video output to Laptop monitor and unplug the DisplayPort cable I can change consoles. (Only setting video output to Laptop is not enough, the cable must go.)
If I use VGA instead, changing consoles seems to work fine. However running command "dmesg" tells of a Call Trace that looks much like the Call Trace I sometimes see when my system becomes unresponsive (attached), though a bit shorter.
---This is dmesg after changing consoles with VGA:---[18562.847011] WARNING: CPU: 0 PID: 358 at drivers/gpu/drm/i915/intel_display.c:13094 intel_atomic_commit_tail+0xec9/0x11b0 [i915][18562.847013] pipe state doesn't match![18562.847014] Modules linked in: appletalk ax25 ipx p8023 p8022 psnap llc iTCO_wdt iTCO_vendor_support snd_hda_codec_conexant snd_hda_codec_generic arc4 coretemp kvm_intel kvm irqbypass ath9k i915 psmouse drm_kms_helper ath9k_common serio_raw ath9k_hw ath mac80211 i2c_i801 uvcvideo drm i2c_smbus snd_hda_intel videobuf2_vmalloc videobuf2_memops snd_hda_codec videobuf2_v4l2 joydev lpc_ich thinkpad_acpi snd_hda_core i2c_algo_bit fb_sys_fops syscopyarea videobuf2_core sysfillrect input_leds snd_hwdep cfg80211 sysimgblt videodev snd_pcm usbkbd media nvram usbmouse snd_timer e1000e snd soundcore ptp shpchp fjes video pps_core mac_hid virtio_console virtio_net virtio_blk virtio_balloon virtio_pcivirtio virtio_ring isci libsas scsi_transport_sas pata_atiixp pata_acpi nvme nvme_core wp512 serpent_generic xts[18562.847065] gf128mul dm_crypt hid_apple hid_generic usbhid hid uas usb_storage ahci libahci [last unloaded: pcspkr][18562.847076] CPU: 0 PID: 358 Comm: X Tainted: G W I 4.8.2-gnu #1[18562.847078] Hardware name: LENOVO 7458WLD/7458WLD, BIOS CBET4000 4.0 05/18/2015[18562.847080] 0000000000000286 000000003943eb96 ffff995f6d297a70 ffffffffa53ede43[18562.847084] ffff995f6d297ac0 0000000000000000 ffff995f6d297ab0 ffffffffa50831e1[18562.847087] 00003326c089ec22 ffff995f6cd11800 ffff995f6d0d4000 ffff995f6cd10800[18562.847090] Call Trace:[18562.847097] [<ffffffffa53ede43>] dump_stack+0x63/0x90[18562.847101] [<ffffffffa50831e1>] __warn+0xd1/0xf0[18562.847103] [<ffffffffa508325f>] warn_slowpath_fmt+0x5f/0x80[18562.847130] [<ffffffffc08ab7d9>] intel_atomic_commit_tail+0xec9/0x11b0 [i915][18562.847133] [<ffffffffa50c7840>] ? wait_woken+0x80/0x80[18562.847159] [<ffffffffc08abec7>] intel_atomic_commit+0x407/0x570 [i915][18562.847191] [<ffffffffc060f161>] ? drm_atomic_check_only+0x141/0x640 [drm][18562.847206] [<ffffffffc060fcf7>] ? drm_atomic_set_crtc_for_connector+0x97/0x100 [drm][18562.847221] [<ffffffffc060f697>] drm_atomic_commit+0x37/0x60 [drm][18562.847234] [<ffffffffc07fbc22>] drm_atomic_helper_set_config+0x82/0xc0 [drm_kms_helper][18562.847248] [<ffffffffc05fdfc5>] drm_mode_set_config_internal+0x65/0x110 [drm][18562.847262] [<ffffffffc060279c>] drm_mode_setcrtc+0x1ec/0x580 [drm][18562.847274] [<ffffffffc05f5132>] drm_ioctl+0x202/0x510 [drm][18562.847288] [<ffffffffc06025b0>] ? drm_mode_setplane+0x1c0/0x1c0 [drm][18562.847292] [<ffffffffa522bb27>] ? __vfs_read+0x37/0x150[18562.847295] [<ffffffffa5240cef>] do_vfs_ioctl+0x9f/0x5e0[18562.847299] [<ffffffffa5091211>] ? __set_task_blocked+0x41/0xa0[18562.847301] [<ffffffffa5093b66>] ? __set_current_blocked+0x36/0x60[18562.847304] [<ffffffffa52412a9>] SyS_ioctl+0x79/0x90[18562.847307] [<ffffffffa5847d36>] entry_SYSCALL_64_fastpath+0x1e/0xa8[18562.847309] ---[ end trace f68728a0d3053b57 ]---

I have no idea if this is really a Guix issue or not, maybe it's Linux-libre?
Let me know if I can be of any assistance.
--Petter#guix Petter
Attachment: IMG_1126-small.JPG
L
L
Ludovic Courtès wrote on 26 Oct 2016 14:30
(name . Petter)(address . petter@mykolab.ch)(address . 24789@debbugs.gnu.org)
874m3zthrm.fsf@gnu.org
Petter <petter@mykolab.ch> skribis:
Toggle quote (15 lines)> I'm having a pretty dramatic experience changing console,> f.ex. Ctrl+Alt+F4. My system becomes completely unresponsive. Even> Alt+SysRq+reisub is unable to persuade my system to perform a> gentlemans reboot. To recover I must do a hard reboot.>> Bringing this up in #guix suggests it's not a common issue.>> My setup is:> Libreboot X200> Docking station> External monitor connected to the docking station with DisplayPort.> XFCE> GuixSD (from git, last commit in my repo> c11933c920dd7b7cdf68e13e6b3718602129210a)
[...]
Toggle quote (3 lines)> I have no idea if this is really a Guix issue or not, maybe it's> Linux-libre?
I definitely don’t experience that on my laptop (not an X200). Perhapsthe KMS module and Xorg driver is at fault? Which ones are in use?
(My laptop has an Intel graphics card, so i915.ko, though for somereason Xorg uses xf86-video-intel instead of “modesetting”.)
Ludo’.
P
P
Petter wrote on 27 Oct 2016 10:59
(address . ludo@gnu.org)(address . 24789@debbugs.gnu.org)
453ef86fc4e8957fa7ed12b6fb4215dc@mykolab.ch
Did you try using an external monitor connected with DisplayPort?
KMS Module in use (from /var/log/Xorg.0.log):[ 18.862] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20160711
As for Xorg driver in use, I'm not sure where or how to find this out.
Grepping /var/log/Xorg.0.log for LoadModule in case that's helpful. If not, let me know how I can find it.58:[ 18.637] (II) LoadModule: "glx"70:[ 18.725] (II) LoadModule: "intel"76:[ 18.747] (II) LoadModule: "modesetting"82:[ 18.762] (II) LoadModule: "fbdev"88:[ 18.771] (II) LoadModule: "vesa"109:[ 18.864] (II) LoadModule: "fbdevhw"145:[ 18.885] (II) LoadModule: "dri2"148:[ 18.885] (II) LoadModule: "present"190:[ 19.050] (II) LoadModule: "libinput"
--Petter
On 2016-10-26 14:30, ludo@gnu.org wrote:
Toggle quote (29 lines)> Petter <petter@mykolab.ch> skribis:> >> I'm having a pretty dramatic experience changing console,>> f.ex. Ctrl+Alt+F4. My system becomes completely unresponsive. Even>> Alt+SysRq+reisub is unable to persuade my system to perform a>> gentlemans reboot. To recover I must do a hard reboot.>> >> Bringing this up in #guix suggests it's not a common issue.>> >> My setup is:>> Libreboot X200>> Docking station>> External monitor connected to the docking station with DisplayPort.>> XFCE>> GuixSD (from git, last commit in my repo>> c11933c920dd7b7cdf68e13e6b3718602129210a)> > [...]> >> I have no idea if this is really a Guix issue or not, maybe it's>> Linux-libre?> > I definitely don’t experience that on my laptop (not an X200). Perhaps> the KMS module and Xorg driver is at fault? Which ones are in use?> > (My laptop has an Intel graphics card, so i915.ko, though for some> reason Xorg uses xf86-video-intel instead of “modesetting”.)> > Ludo’.
L
L
Ludovic Courtès wrote on 27 Oct 2016 13:55
(name . Petter)(address . petter@mykolab.ch)(address . 24789@debbugs.gnu.org)
87shrim2ex.fsf@gnu.org
Petter <petter@mykolab.ch> skribis:
Toggle quote (2 lines)> Did you try using an external monitor connected with DisplayPort?
No, I only tried VGA and HDMI outputs, which work fine.
Toggle quote (18 lines)> KMS Module in use (from /var/log/Xorg.0.log):> [ 18.862] (II) intel(0): Using Kernel Mode Setting driver: i915,> version 1.6.0 20160711>> As for Xorg driver in use, I'm not sure where or how to find this out.>> Grepping /var/log/Xorg.0.log for LoadModule in case that's helpful. If> not, let me know how I can find it.> 58:[ 18.637] (II) LoadModule: "glx"> 70:[ 18.725] (II) LoadModule: "intel"> 76:[ 18.747] (II) LoadModule: "modesetting"> 82:[ 18.762] (II) LoadModule: "fbdev"> 88:[ 18.771] (II) LoadModule: "vesa"> 109:[ 18.864] (II) LoadModule: "fbdevhw"> 145:[ 18.885] (II) LoadModule: "dri2"> 148:[ 18.885] (II) LoadModule: "present"> 190:[ 19.050] (II) LoadModule: "libinput"
OK.
Could you check maybe whether other X200 users have that problem? Itdoesn’t seem to be GuixSD-specific.
Did you have success with another distro on this laptop? If so, itwould be good to see the difference in terms of drivers and versions.
Ludo’.
L
L
Ludovic Courtès wrote on 1 Nov 2016 22:12
control message for bug #24789
(address . control@debbugs.gnu.org)
87oa1ynbur.fsf@gnu.org
tags 24789 moreinfo
Z
Z
zimoun wrote on 18 Feb 2020 15:14
Hunting#24789: Changing console renders my system unresponsive
CAJ3okZ2DHzaKA+eu5VkYfB8ZXc_FiMtLZ3b++JKeLpHg5vX4JQ@mail.gmail.com
Dear,
The bug #24789 [1] is a bit old.What is the status? Do you still have this unexpected behaviour?


[1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=24789
All the best,simon
Z
Z
zimoun wrote on 13 May 2020 01:38
closing #24789
CAJ3okZ0YCAjrz8WU0BEjZVgcdKGRKZ7UWGxHdeoqWgq=5tBU8w@mail.gmail.com
Dear,
Because this bug is more than 3 years old, tagged moreinfo and withoutany answer by the submitter since 12 weeks, I am closing.
Best regards,simon
Closed
?