Re: user unable to log in xenodm / Xorg session | XIO fatal io error 35
> I suspect the problem may have had to do ... Why the hell did you contact the list then? To confirm your suspicion(s)?
Re: user unable to log in xenodm / Xorg session | XIO fatal io error 35
I have now been running with OpenBSD 6.5 for a couple of weeks without meeting this problem again, on a fresh install. I am very careful not to crash or halt the system abruptly ! I suspect the problem may have had to do with the inteldrm driver and the EFI, as suggested by dmesg(8) : ... acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: LCD0 cpu0: Enhanced SpeedStep 2594 MHz: speeds: 2600, 2500, 2400, 2300, 2200, 2100, 2000, 1900, 1800, 1700, 1600, 1500, 1400, 1300, 1200 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09 inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 4000" rev 0x09 drm0 at inteldrm0 inteldrm0: msi inteldrm0: 1366x768, 32bpp wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation) wsdisplay0: screen 1-5 added (std, vt100 emulation) xhci0 at pci0 dev 20 function 0 "Intel 7 Series xHCI" rev 0x04: msi, xHCI 1.0 ... vmm0 at mainbus0: VMX/EPT efifb at mainbus0 not configured error: [drm:pid0:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder B error: [drm:pid0:intel_pch_fifo_underrun_irq_handler] *ERROR* PCH transcoder B FIFO underrun ... error: [drm:pid81698:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder B error: [drm:pid81698:intel_pch_fifo_underrun_irq_handler] *ERROR* PCH transcoder B FIFO underrun error: [drm:pid54999:cpt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder B error: [drm:pid54999:intel_pch_fifo_underrun_irq_handler] *ERROR* PCH transcoder B FIFO underrun > On Thu, May 2, 2019 at 7:53 PM wrote: > > > > SYMPTOM: Soon after a fresh OpenBSD install intended to use as a > > laptop / work engine, and consequently a few uses of a graphical > > session, suddenly the X session cannot start anymore : logging > > in with a correct user/passwd pair provokes a crash and restart of > > the > > X Display Manager, displaying the xdm login screen anew. > > But I can still log in xdm as root. > > > > Xorg.0.log https://pastebin.com/pZDf90TE > > xenodm.log https://pastebin.com/abjyLCyU > > dmesg.boot https://pastebin.com/T3UGucB1 (also attached) > > Hi, > > What is the contents of your ~/.xsession & ~/.xsession-errors files? > > I had this same issue, and was able to solve it by removing .xsession > or replacing it with an empty file. > > Ian > > Hi Ian, thanks for your concern. I had saved the files from my system before re-installing : sylvain:531$ cat .xsession export ENV=$HOME/.profile export LC_CTYPE=fr_FR.UTF-8 sylvain:532$ cat .xsession-errors sylvain:533$ The .xsession on my present system/home is indeed absent. Sylvain S
Re: user unable to log in xenodm / Xorg session | XIO fatal io error 35
On Thu, May 2, 2019 at 7:53 PM wrote: > > SYMPTOM: Soon after a fresh OpenBSD install intended to use as a > laptop / work engine, and consequently a few uses of a graphical > session, suddenly the X session cannot start anymore : logging > in with a correct user/passwd pair provokes a crash and restart of the > X Display Manager, displaying the xdm login screen anew. > But I can still log in xdm as root. > > Xorg.0.log https://pastebin.com/pZDf90TE > xenodm.log https://pastebin.com/abjyLCyU > dmesg.boot https://pastebin.com/T3UGucB1 (also attached) Hi, What is the contents of your ~/.xsession & ~/.xsession-errors files? I had this same issue, and was able to solve it by removing .xsession or replacing it with an empty file. Ian
user unable to log in xenodm / Xorg session | XIO fatal io error 35
SYMPTOM: Soon after a fresh OpenBSD install intended to use as a laptop / work engine, and consequently a few uses of a graphical session, suddenly the X session cannot start anymore : logging in with a correct user/passwd pair provokes a crash and restart of the X Display Manager, displaying the xdm login screen anew. But I can still log in xdm as root. Xorg.0.log https://pastebin.com/pZDf90TE xenodm.log https://pastebin.com/abjyLCyU dmesg.boot https://pastebin.com/T3UGucB1 (also attached) DIAGNOSTIC: A main relevant error seems to be (from xenodm.log) : 26 xenodm info (pid 30531): sourcing /etc/X11/xenodm/TakeConsole 27 XIO: fatal IO error 35 (Resource temporarily unavailable) on X server ":0" 28 after 128 requests (121 known processed) with 0 events remaining. TakeConsole file executes the sessreg(1) command. There is also a minor error listed in the Xorg.0.log file 345 [14.897] (EE) PreInit returned 2 for "/dev/wsmouse" I use a laptop that was assembled with Linux by an OEM in 2013. === This (being unable to log in a graphic session) has happened on all three OpenBSD installs I performed : ⋅ First on OpenBSD 6.4 run in a standard qemu x86_64 virtual machine. ⋅ Then on my recent installation of OpenBSD 6.4, which unrelatedly I also upgraded to the 6.5 version of the operating system. ⋅ Finally, on the subsequent fresh install of the latest OpenBSD 6.5 release (which the log files are from). It is quite frustrating. I suspect this might be triggered by an improper powering off of the system. (overall system as well as xenodm and the X session) Amusingly enough, a quick web search for the error returns three relevant results, two of which refer other operating systems : ⋅ The first is a thread, blank of replies, from Apple forums circa 2015 https://discussions.apple.com/thread/7356352 ⋅ Another is a guide to a tool designed to fix this error for Windows http://wiki-157727.usedtech.org/xio-fatal-io-error-35.html ⋅ Somebody on these very lists as far back as in 2011, on x11-devel =x11=201103/1 >From beasley Subject X11 crashes with fatal IO error 35 on old pentium I laptop DateThu, 03 Mar 2011 01:55:56 -0600 https://marc.info/?t=12991390632=1=2 OR http://openbsd-archive.7691.n7.nabble.com/X11-crashes-with-fatal-IO-error-35-on-old-pentium-I-laptop-td211423.html ⋅ Also a thread on stackexchange closed for vagueness https://unix.stackexchange.com/questions/250215/fatal-io-error-35-x-problem I'm hoping to fix this problem which makes the situation very impractical. Thank you, Sylvain S dmesg.boot Description: Binary data
