Re: X exiting after update (inteldrm error)
I am running the June 5th snapshot with no problems: OpenBSD 4.7-current (GENERIC) #19: Sat Jun 5 20:15:56 MDT 2010 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC [...] vga1 at pci0 dev 2 function 0 Intel 82945GM Video rev 0x03 [...] drm0 at inteldrm0 Intel 82945GM Video rev 0x03 at pci0 dev 2 function 1 not configured Looks like the commit referenced below worked for me. But the Log message states: Disable Framebuffer Compression on 915GM and 945GM. Since your not using 915GM or 945GM: vga1 at pci0 dev 2 function 0 Intel 82865G Video rev 0x02 you may need to wait for it to be fixed, or with time and aptitude you could try to fix it yourself.) On Mon, Jun 14, 2010 at 12:42 AM, Anthony Bentley anthonyjbent...@gmail.com wrote: I am having the same problem on a Lenovo R60e running snapshots from May12th and May 22nd. Looks like it may be fixed: http://marc.info/?l=openbsd-cvsm=127457255931742w=2 , will try the next snapshot. I get the error on a new snapshot. (Last used 4.6, no idea if this occurred in snapshots in between.) Jun 13 13:20:48 pinetree /bsd: inteldrm0: gpu hung! Jun 13 13:20:48 pinetree /bsd: no reset function for chipset.
Re: X exiting after update (inteldrm error)
I am having the same problem on a Lenovo R60e running snapshots from May12th and May 22nd. Looks like it may be fixed: http://marc.info/?l=openbsd-cvsm=127457255931742w=2 , will try the next snapshot. I get the error on a new snapshot. (Last used 4.6, no idea if this occurred in snapshots in between.) Jun 13 13:20:48 pinetree /bsd: inteldrm0: gpu hung! Jun 13 13:20:48 pinetree /bsd: no reset function for chipset. Xorg.0.log, dmesg: (--) checkDevMem: using aperture driver /dev/xf86 (--) Using wscons driver on /dev/ttyC4 in pcvt compatibility mode (version 3.32 ) X.Org X Server 1.6.5 Release Date: 2009-10-11 X Protocol Version 11, Revision 0 Build Operating System: OpenBSD 4.7 i386 Current Operating System: OpenBSD pinetree.gateway.2wire.net 4.7 GENERIC.MP#36 i386 Build Date: 02 June 2010 01:40:17AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sun Jun 13 13:20:06 2010 (II) Loader magic: 0x7ec0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 5.0 X.Org XInput driver : 4.0 X.Org Server Extension : 2.0 (II) Loader running on openbsd (--) PCI:*(0:0:2:0) 8086:2572:1028:0151 Intel 82865G Video rev 2, Mem @ 0xe8000 000/134217728, 0xfeb8/524288, I/O @ 0xed98/8 (==) Using default built-in configuration (21 lines) (==) --- Start of built-in configuration --- Section Device Identifier Builtin Default intel Device 0 Driver intel EndSection Section Screen Identifier Builtin Default intel Screen 0 Device Builtin Default intel Device 0 EndSection Section Device Identifier Builtin Default vesa Device 0 Driver vesa EndSection Section Screen Identifier Builtin Default vesa Screen 0 Device Builtin Default vesa Device 0 EndSection Section ServerLayout Identifier Builtin Default Layout Screen Builtin Default intel Screen 0 Screen Builtin Default vesa Screen 0 EndSection (==) --- End of built-in configuration --- (==) ServerLayout Builtin Default Layout (**) |--Screen Builtin Default intel Screen 0 (0) (**) | |--Monitor default monitor (**) | |--Device Builtin Default intel Device 0 (==) No monitor specified for screen Builtin Default intel Screen 0. Using a default monitor configuration. (**) |--Screen Builtin Default vesa Screen 0 (1) (**) | |--Monitor default monitor (**) | |--Device Builtin Default vesa Device 0 (==) No monitor specified for screen Builtin Default vesa Screen 0. Using a default monitor configuration. (==) Not automatically adding devices (==) Not automatically enabling devices (==) FontPath set to: /usr/X11R6/lib/X11/fonts/misc/, /usr/X11R6/lib/X11/fonts/TTF/, /usr/X11R6/lib/X11/fonts/OTF, /usr/X11R6/lib/X11/fonts/Type1/, /usr/X11R6/lib/X11/fonts/100dpi/, /usr/X11R6/lib/X11/fonts/75dpi/ (==) ModulePath set to /usr/X11R6/lib/modules (==) |--Input Device default pointer (==) |--Input Device default keyboard (==) The core pointer device wasn't specified explicitly in the layout. Using the default mouse configuration. (==) The core keyboard device wasn't specified explicitly in the layout. Using the default keyboard configuration. (II) System resource ranges: [0] -1 0 0x000f - 0x000f (0x1) MX[B] [1] -1 0 0x000c - 0x000e (0x3) MX[B] [2] -1 0 0x - 0x0009 (0xa) MX[B] [3] -1 0 0x - 0x (0x1) IX[B] [4] -1 0 0x - 0x00ff (0x100) IX[B] (II) LoadModule: extmod (II) Loading /usr/X11R6/lib/modules/extensions//libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.6.5, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: dbe (II) Loading /usr/X11R6/lib/modules/extensions//libdbe.so (II) Module dbe: vendor=X.Org Foundation compiled for 1.6.5, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: glx (II) Loading
Re: X exiting after update (inteldrm error)
I am having the same problem on a Lenovo R60e running snapshots from May12th and May 22nd. Looks like it may be fixed: http://marc.info/?l=openbsd-cvsm=127457255931742w=2 , will try the next snapshot. Thanks. From /var/log/messages: May 17 14:11:42 CN212314 /bsd: render error detected, EIR: 0x0010 May 17 14:11:42 CN212314 /bsd: page table error May 17 14:11:42 CN212314 /bsd: PGTBL_ER: 0x0002 May 17 14:11:42 CN212314 /bsd: render error detected, EIR: 0x0010 May 17 14:11:42 CN212314 /bsd: page table error May 17 14:11:42 CN212314 /bsd: PGTBL_ER: 0x0002 May 17 14:11:42 CN212314 /bsd: no reset function for chipset. May 17 14:11:42 CN212314 /bsd: no reset function for chipset. May 17 14:19:39 CN212314 /bsd: error: [drm:pid3286:inteldrm_lastclose] *ERROR* failed to idle hardware: 5 May 18 14:24:04 CN212314 /bsd: render error detected, EIR: 0x0010 May 18 14:24:04 CN212314 /bsd: page table error May 18 14:24:04 CN212314 /bsd: PGTBL_ER: 0x0002 May 18 14:24:04 CN212314 /bsd: render error detected, EIR: 0x0010 May 18 14:24:04 CN212314 /bsd: page table error May 18 14:24:04 CN212314 /bsd: PGTBL_ER: 0x0002 May 18 14:24:04 CN212314 /bsd: no reset function for chipset. May 18 14:24:04 CN212314 /bsd: no reset function for chipset. May 18 14:24:21 CN212314 /bsd: error: [drm:pid31257:inteldrm_lastclose] *ERROR* failed to idle hardware: 5 May 18 14:28:14 CN212314 /bsd: error: [drm:pid2116:inteldrm_lastclose] *ERROR* failed to idle hardware: 5 May 18 14:28:16 CN212314 /bsd: error: [drm:pid2116:i915_gem_entervt_ioctl] *ERROR* Reenabling wedged hardware, good luck May 18 14:28:16 CN212314 /bsd: render error detected, EIR: 0x0010 May 18 14:28:16 CN212314 /bsd: page table error May 18 14:28:16 CN212314 /bsd: PGTBL_ER: 0x0002 May 18 14:28:16 CN212314 /bsd: render error detected, EIR: 0x0010 May 18 14:28:16 CN212314 /bsd: page table error May 18 14:28:16 CN212314 /bsd: PGTBL_ER: 0x0002 May 18 14:28:16 CN212314 /bsd: no reset function for chipset. May 18 14:28:16 CN212314 /bsd: error: [drm:pid6:i915_gem_evict_inactive] *ERROR* Pinned object in unbind list May 18 14:28:16 CN212314 /bsd: no reset function for chipset. May 18 14:28:16 CN212314 /bsd: error: [drm:pid6:i915_gem_evict_inactive] *ERROR* Pinned object in unbind list May 19 09:37:46 CN212314 /bsd: render error detected, EIR: 0x0010 May 19 09:37:47 CN212314 /bsd: page table error May 19 09:37:47 CN212314 /bsd: PGTBL_ER: 0x0002 May 19 09:37:47 CN212314 /bsd: render error detected, EIR: 0x0010 May 19 09:37:47 CN212314 /bsd: page table error May 19 09:37:47 CN212314 /bsd: PGTBL_ER: 0x0002 May 19 09:37:47 CN212314 /bsd: no reset function for chipset. May 19 09:37:47 CN212314 /bsd: no reset function for chipset. May 23 12:56:48 CN212314 /bsd: render error detected, EIR: 0x0010 May 23 12:56:48 CN212314 /bsd: page table error May 23 12:56:48 CN212314 /bsd: PGTBL_ER: 0x0002 May 23 12:56:48 CN212314 /bsd: render error detected, EIR: 0x0010 May 23 12:56:48 CN212314 /bsd: page table error May 23 12:56:48 CN212314 /bsd: PGTBL_ER: 0x0002 May 23 12:56:48 CN212314 /bsd: no reset function for chipset. May 23 12:56:48 CN212314 /bsd: no reset function for chipset. May 23 14:15:31 CN212314 /bsd: error: [drm:pid20034:inteldrm_lastclose] *ERROR* failed to idle hardware: 5 May 22th dmesg and Xorg.0.log: === OpenBSD 4.7-current (GENERIC) #652: Sat May 22 13:08:53 MDT 2010 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC cpu0: Intel(R) Celeron(R) M CPU 410 @ 1.46GHz (GenuineIntel 686-class) 1.47 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,SBF,SSE3,MWAIT,TM2,xTPR,PDCM real mem = 526872576 (502MB) avail mem = 500920320 (477MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 10/16/06, BIOS32 rev. 0 @ 0xfd690, SMBIOS rev. 2.4 @ 0xe0010 (67 entries) bios0: vendor LENOVO version 7EETB6WW (2.06 ) date 10/16/2006 bios0: LENOVO 06573PU acpi0 at bios0: rev 2 acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET BOOT SSDT SSDT SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) PCI1(S4) USB0(S3) USB1(S3) USB2(S3) USB7(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 132MHz ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus 4 (EXP2) acpiprt5 at acpi0: bus 12 (EXP3) acpiprt6 at acpi0: bus 21 (PCI1) acpiec0 at acpi0 acpicpu0 at acpi0: C3, C2, C1 acpipwrres0 at acpi0: PUBS acpitz0 at acpi0: critical temperature 127 degC acpitz1 at acpi0: critical temperature 98 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0
Re: X exiting after update (inteldrm error)
On Wed, 12 May 2010 02:28:36 -0300 Alan R. S. Bueno alan@gmail.com wrote: I'm not sure if misc@ is the right place to send this... After update kernel + userland + X (yesterday, in the morning (here in Brazil)... but with all the latest relevant changes in the trees src/ and xenocara/ applied), X exited (today, tonight, here in Brazil... yeah! :) with the following error: Both INTELDRM_GEM kernel and the corresponding new X intel driver were recently committed. Due to mirrors being out of sync, your cvs update may have only caught a portion of the needed changes. You should try again with cvs update of src and xenocara. Though not entirely relevant, you might also want to note: http://www.openbsd.org/faq/current.html#20100510 jcr -- The OpenBSD Journal - http://www.undeadly.org
Re: X exiting after update (inteldrm error)
On Wed, May 12, 2010 at 3:41 PM, J.C. Roberts list-...@designtools.org wrote: Both INTELDRM_GEM kernel and the corresponding new X intel driver were recently committed. Due to mirrors being out of sync, your cvs update may have only caught a portion of the needed changes. You should try again with cvs update of src and xenocara. No. The latest change that my cvs update caught was: http://marc.info/?l=openbsd-cvsm=127357649215000w=2 After that change, no *relevant* change was made (neither in src/ nor xenocara/) that can be the cause of the error; so, cvs update now is irrelevant. If you are subscribed to source-changes@, check the latest changes; if not, check here: http://marc.info/?l=openbsd-cvsr=1b=201005w=2 Though not entirely relevant, you might also want to note: http://www.openbsd.org/faq/current.html#20100510 It's not the case. Kernel + Userland + Xenocara are all up to date (well, to the date in my dmesg head...). Today my machine froze again in the same condictions. (I had to use the power button.) :-(
Re: X exiting after update (inteldrm error)
On Wed, 12 May 2010 17:20:28 -0300 Alan R. S. Bueno alan@gmail.com wrote: On Wed, May 12, 2010 at 3:41 PM, J.C. Roberts list-...@designtools.org wrote: Both INTELDRM_GEM kernel and the corresponding new X intel driver were recently committed. Due to mirrors being out of sync, your cvs update may have only caught a portion of the needed changes. You should try again with cvs update of src and xenocara. No. The latest change that my cvs update caught was: http://marc.info/?l=openbsd-cvsm=127357649215000w=2 After that change, no *relevant* change was made (neither in src/ nor xenocara/) that can be the cause of the error; so, cvs update now is irrelevant. If you are subscribed to source-changes@, check the latest changes; if not, check here: I think you're right about the *relevant* changes since the intagp stuff committed today seems to be for pineview from the commit logs. Today my machine froze again in the same condictions. (I had to use the power button.) :-( Bummer. I've been testing the new intel driver (with GEM) for a few weeks and it still has a few bugs with old 82845G. In my case, the screen gets corrupted, but X doesn't actually crash. This happens repeatably when switching to/from virtual terminals, and happens occasionally when flipping between xterms and gtk-based apps in X. Of course, once it's corrupted, a subsequent VT switch will crash X, but the corruption alone does not. The best thing you can do is enable DRM Debug in the kernel and try to get a core dump. $ cat /usr/src/sys/conf/GENERIC | grep DEBUG= makeoptions DEBUG=-g # compile full symbol table $ cat /usr/src/sys/arch/i386/conf/GENERIC_DRMDEBUG include arch/i386/conf/GENERIC option DRMDEBUG option DRMLOCKDEBUG And then follow the instructions in xenocara/README for how to set up and run the system to get a core file. -- The OpenBSD Journal - http://www.undeadly.org
Re: X exiting after update (inteldrm error)
On Wed, May 12, 2010 at 11:34 PM, J.C. Roberts list-...@designtools.org wrote: Bummer. I've been testing the new intel driver (with GEM) for a few weeks and it still has a few bugs with old 82845G. In my case, the screen gets corrupted, but X doesn't actually crash. This happens repeatably when switching to/from virtual terminals, and happens occasionally when flipping between xterms and gtk-based apps in X. Of course, once it's corrupted, a subsequent VT switch will crash X, but the corruption alone does not. I'm experiencing exactly the same issue on my X41 (915GM). ciao, david
X exiting after update (inteldrm error)
Hi, I'm not sure if misc@ is the right place to send this... After update kernel + userland + X (yesterday, in the morning (here in Brazil)... but with all the latest relevant changes in the trees src/ and xenocara/ applied), X exited (today, tonight, here in Brazil... yeah! :) with the following error: $ zcat /var/log/messages.0.gz [...] May 12 00:47:30 valinor /bsd: render error detected, EIR: 0x0010 May 12 00:47:30 valinor /bsd: page table error May 12 00:47:30 valinor /bsd: PGTBL_ER: 0x0002 May 12 00:47:30 valinor /bsd: render error detected, EIR: 0x0010 May 12 00:47:30 valinor /bsd: page table error May 12 00:47:30 valinor /bsd: PGTBL_ER: 0x0002 May 12 00:47:30 valinor /bsd: no reset function for chipset. May 12 00:47:30 valinor /bsd: no reset function for chipset. May 12 00:47:39 valinor /bsd: error: [drm:pid17835:inteldrm_lastclose] *ERROR* failed to idle hardware: 5 [...] After try to start X, the X exited again with the error: $ zcat /var/log/messages.0.gz [...] May 12 00:56:35 valinor /bsd: error: [drm:pid28250:inteldrm_lastclose] *ERROR* failed to idle hardware: 5 May 12 00:56:38 valinor /bsd: error: [drm:pid28250:i915_gem_entervt_ioctl] *ERROR* Reenabling wedged hardware, good luck May 12 00:56:38 valinor /bsd: render error detected, EIR: 0x0010 May 12 00:56:38 valinor /bsd: page table error May 12 00:56:38 valinor /bsd: PGTBL_ER: 0x0002 May 12 00:56:38 valinor /bsd: render error detected, EIR: 0x0010 May 12 00:56:38 valinor /bsd: page table error May 12 00:56:38 valinor /bsd: PGTBL_ER: 0x0002 May 12 00:56:38 valinor /bsd: no reset function for chipset. May 12 00:56:38 valinor /bsd: error: [drm:pid6:i915_gem_evict_inactive] *ERROR* Pinned object in unbind list May 12 00:56:38 valinor /bsd: no reset function for chipset. May 12 00:56:38 valinor /bsd: error: [drm:pid6:i915_gem_evict_inactive] *ERROR* Pinned object in unbind list May 12 00:56:48 valinor /bsd: error: [drm:pid28250:inteldrm_lastclose] *ERROR* failed to idle hardware: 5 [...] After reboot the machine, X works again... How-to-repeat: Well, the error occured only one time by now, but maybe it can happen again... I was using mupdf-0.5 and mozilla-firefox-3.6.3p1 (Google Images and cartoon...) when the error occurred. Render error? Any connection with mupdf or firefox? Bellow: dmesg, Xorg.0.log.old (when error happened), Xorg.0.log (system running OK, while I'm typing this message...). dmesg = OpenBSD 4.7-current (GENERIC) #0: Tue May 11 11:27:27 BRT 2010 r...@valinor.arda.net:/usr/obj/GENERIC cpu0: Intel(R) Celeron(R) M CPU 520 @ 1.60GHz (GenuineIntel 686-class) 1.60 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,SBF,SSE3,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM real mem = 1063690240 (1014MB) avail mem = 1020542976 (973MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 05/28/07, BIOS32 rev. 0 @ 0xffa10, SMBIOS rev. 2.4 @ 0xf70b0 (61 entries) bios0: vendor Dell Inc. version A06 date 05/28/2007 bios0: Dell Inc. Latitude D520 acpi0 at bios0: rev 0 acpi0: tables DSDT FACP HPET APIC MCFG SLIC SSDT SSDT acpi0: wakeup devices LID_(S3) PBTN(S4) PCI0(S4) USB0(S0) USB1(S0) USB2(S0) USB3(S0) EHCI(S0) AZAL(S3) PCIE(S4) RP01(S3) RP02(S4) RP03(S3) RP04(S3) RP05(S3) RP06(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 132MHz ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 0, remapped to apid 1 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 2 (PCIE) acpiprt2 at acpi0: bus 11 (RP01) acpiprt3 at acpi0: bus 12 (RP02) acpiprt4 at acpi0: bus -1 (RP03) acpiprt5 at acpi0: bus -1 (RP04) acpiprt6 at acpi0: bus -1 (RP05) acpiprt7 at acpi0: bus -1 (RP06) acpicpu0 at acpi0: C3, C2, C1 acpitz0 at acpi0: critical temperature 126 degC acpiac0 at acpi0: AC unit online acpibat0 at acpi0: BAT0 not present acpibat1 at acpi0: BAT1 not present acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: PBTN acpibtn2 at acpi0: SBTN acpidock0 at acpi0: GDCK not docked (0) acpivideo0 at acpi0: VID_ acpivout0 at acpivideo0: TV__ acpivout1 at acpivideo0: CRT_ acpivout2 at acpivideo0: LCD_ acpivout3 at acpivideo0: DVI_ acpivideo1 at acpi0: VID2 bios0: ROM list: 0xc/0xf000! 0xcf000/0x1000 pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 Intel 82945GM Host rev 0x03 vga1 at pci0 dev 2 function 0 Intel 82945GM Video rev 0x03 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1: apic 1 int 16 (irq 11) drm0 at inteldrm0 Intel 82945GM Video rev 0x03 at pci0 dev 2 function 1 not configured azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x01: apic 1 int 21 (irq 10)
