Sorry for the long silence. Going has been slow: it takes a while to do a tweak/test/reboot/hang cycle. Especially since the disk controller gets munged upon the bug happening, even persisting across a power cycle (!) about 50% of the time (I have no idea how such a thing is even possible). And, this device is my "get work done" laptop, using the 4.14 kernel which is perfectly happy.
Anyway: tried a different approach. Threw in a spare disk, and tried a clean install of F29 and Kubuntu 18.04.1, in case cruft was to blame. F29 installed from dvd... but the kernel installed to disk didn't boot once the first install pass finished. Kubuntu's install dvd wouldn't even boot past the spinny "it's starting to boot" graphics screen. In both cases, since things are "graphical boot" and "quiet", there's no feedback as to exactly what went wrong, and the system hangs too hard to switch to a different vtty, but it felt the same as the hangs described above. Trying with the latest/last F27 kernel (yes, it's EOL now) 4.18.19-100, tried all permutations of integrated, discrete, and optimus bios settings, excluding nouveau drivers, and the nvidia proprietary blob. Sometimes it can get a clean boot - but then the sata controller goes out to lunch as soon as a write cache flush happens. Which makes me think the kms problem which started this thread is a symptom rather than the problem, just the one which usually triggers first. This is consistent with the problems getting log traces of the problems described above, because a lunched sata controller can't log errors. Went back to drm-tip. See that it's kernel 5.0 now, cool. This minimally configured kernel continues to work. I've enabled the extra features needed to run the laptop, no problems. So: the bug is at the very least triggered by one of the (myriad) of enabled kernel options in the distro stock kernels. It feels to me like the old days of unprotected flat memory space where you could POKE random values into random addresses and watch the system fall apart: with the initial kms call being the most sensitive to it, and things unravel into thrashing the disk controller. Parameter space is too vast for me to find the culprit with intermittent effort and a logging system that's often the first victim of the bug. So, I'm ready to punt, documenting this here in case someone else with more clues googles it is the only remaining thing I can do. Time to just return to the 1990's and compile my own kernel :( At least git now makes tracking updates easier than it used to be in the Bad Old Days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751268 Title: bionic desktop does not boot with external monitor attached - [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stuck / vblank wait timed out on crtc 1 Status in Linux: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Ubuntu Desktop Bionic up to date System doesn't boot with an external monitor attached. There is this message in the journal (full journal attached for this boot) fbcon: inteldrmfb (fb0) is primary device [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stuck vblank wait timed out on crtc 1 ------------[ cut here ]------------ WARNING: CPU: 3 PID: 201 at /build/linux-UKCsxy/linux-4.13.0/drivers/gpu/drm/drm_vblank.c:1090 drm_wait_one_vblank+0x19b/0x1b0 [drm] Modules linked in: hid_lenovo uas usb_storage rtsx_usb_sdmmc rtsx_usb hid_generic usbhid hid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse ahci libahci drm wmi video CPU: 3 PID: 201 Comm: kworker/u8:6 Tainted: G U 4.13.0-32-generic #35-Ubuntu Hardware name: ASUSTeK COMPUTER INC. UX32VD/UX32VD, BIOS UX32VD.214 01/29/2013 Workqueue: events_unbound async_run_entry_fn task: ffff9760d81cae80 task.stack: ffffb01dc1fb8000 RIP: 0010:drm_wait_one_vblank+0x19b/0x1b0 [drm] RSP: 0018:ffffb01dc1fbb7c8 EFLAGS: 00010282 RAX: 000000000000001f RBX: ffff9760d7080000 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000246 RBP: ffffb01dc1fbb828 R08: 000000000000001f R09: 000000000002af84 R10: ffffb01dc1fbb7c8 R11: 000000000000041b R12: 0000000000000001 R13: 0000000000000170 R14: 0000000000000001 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff9760eef80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f156d6d68f0 CR3: 000000024660a002 CR4: 00000000001606e0 Call Trace: ? wait_woken+0x80/0x80 ironlake_crtc_enable+0x477/0xc00 [i915] ? gen6_write8+0x190/0x190 [i915] intel_update_crtc+0x4b/0xe0 [i915] intel_update_crtcs+0x5b/0x80 [i915] intel_atomic_commit_tail+0x254/0xf90 [i915] ? __schedule+0x293/0x880 intel_atomic_commit+0x3d5/0x490 [i915] ? drm_atomic_check_only+0x37b/0x540 [drm] drm_atomic_commit+0x4b/0x50 [drm] restore_fbdev_mode+0x15e/0x270 [drm_kms_helper] drm_fb_helper_restore_fbdev_mode_unlocked+0x2e/0x80 [drm_kms_helper] drm_fb_helper_set_par+0x2d/0x60 [drm_kms_helper] intel_fbdev_set_par+0x1a/0x70 [i915] fbcon_init+0x484/0x650 visual_init+0xd6/0x130 do_bind_con_driver+0x1fc/0x410 do_take_over_console+0x82/0x1a0 do_fbcon_takeover+0x5c/0xb0 fbcon_event_notify+0x587/0x780 notifier_call_chain+0x4a/0x70 blocking_notifier_call_chain+0x43/0x60 fb_notifier_call_chain+0x1b/0x20 register_framebuffer+0x24d/0x360 drm_fb_helper_initial_config+0x249/0x400 [drm_kms_helper] intel_fbdev_initial_config+0x18/0x30 [i915] async_run_entry_fn+0x36/0x150 process_one_work+0x1e7/0x410 worker_thread+0x4b/0x420 kthread+0x125/0x140 ? process_one_work+0x410/0x410 ? kthread_create_on_node+0x70/0x70 ret_from_fork+0x1f/0x30 Code: ff e8 da 3b 4c d6 48 8b 7d a0 48 8d 75 a8 e8 dd 93 50 d6 45 85 ff 0f 85 0c ff ff ff 44 89 e6 48 c7 c7 d8 eb 3d c0 e8 b6 46 52 d6 <0f> ff e9 f6 fe ff ff 0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 ---[ end trace a1db7ccd0b5e4dfc ]--- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: j-lallement 3671 F.... pulseaudio /dev/snd/controlC0: j-lallement 3671 F.... pulseaudio /dev/snd/controlC1: j-lallement 3671 F.... pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Feb 23 13:58:39 2018 InstallationDate: Installed on 2013-09-03 (1633 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) MachineType: ASUSTeK COMPUTER INC. UX32VD ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.171 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-01-26 (27 days ago) dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX32VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1751268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
