Bug 1467 - lockup when switching back from consoles
Summary: lockup when switching back from consoles
Status: RESOLVED WORKSFORME
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: 6.8.0
Hardware: x86 (IA32) Linux (All)
: high major
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
: 1848 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-09-25 08:13 UTC by Tobias Preclik
Modified: 2005-02-13 20:23 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Tobias Preclik 2004-09-25 08:13:28 UTC
i migrated from xfree and actually everything runs fine.
distro: gentoo
desktop: gnome 2.6
driver: i810
dri: enabled

nevertheless i noticed a pretty annoying problem. when i startx and switch to a
console (ctrl+alt+fx) and then back to the desktop i see nothing but a black
screen. the computers locked then. no mouse, no console switching no
ctrl+alt+backsp. the Xorg.0.log states the following:

Fatal server error:
EnterVT failed for screen 0


Please consult the The X.Org Foundation support 
	 at http://wiki.X.Org
 for help. 
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

Error in I810WaitLpRing(), now is 696107, start is 694106
pgetbl_ctl: 0x7d30001 pgetbl_err: 0x808a000
ipeir: 0 iphdr: 0
LP ring tail: 8 head: 0 len: 0 start 0
eir: 0 esr: 0 emr: 3d
instdone: ff7b instpm: 0
memmode: 4 instps: 0
hwstam: bac7 ier: 0 imr: bac7 iir: 0
space: 65520 wanted 65528
(II) I810(0): [drm] removed 1 reserved context for kernel
(II) I810(0): [drm] unmapping 8192 bytes of SAREA 0xc8949000 at 0x40249000

FatalError re-entered, aborting
lockup
Comment 1 Eric Piel 2004-10-20 00:59:27 UTC
Same error here, with Mandrake, kernel 2.6.9 and a i815.

Comment 2 Tobias Preclik 2005-01-01 07:06:29 UTC
(In reply to comment #1)
> Same error here, with Mandrake, kernel 2.6.9 and a i815.
my chipset is i815 too.

I noticed that it's not a total lockup (at least not anymore). Console switching
does work after some seconds and the x server crashes. Problem persists with
xorg 6.8.1 and vanilla kernel 2.6.9.

Fatal server error:
EnterVT failed for screen 0


Please consult the The X.Org Foundation support
     at http://wiki.X.Org
 for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional informati
Error in I810WaitLpRing(), now is 89374, start is 87373
pgetbl_ctl: 0x17890001 pgetbl_err: 0x12
ipeir: 0 iphdr: 0
LP ring tail: 8 head: 0 len: 0 start 0
eir: 0 esr: 10 emr: 3d
instdone: ff7b instpm: 0
memmode: 4 instps: 0
hwstam: bac7 ier: 0 imr: bac7 iir: 0
space: 65520 wanted 65528
(II) I810(0): [drm] removed 1 reserved context for kernel
(II) I810(0): [drm] unmapping 8192 bytes of SAREA 0xd894a000 at 0xb7d67000

FatalError re-entered, aborting
lockup
Comment 3 Tobias Preclik 2005-01-01 07:18:49 UTC
*** Bug 1848 has been marked as a duplicate of this bug. ***
Comment 4 Tobias Preclik 2005-01-01 07:55:48 UTC
Further investigations revealed that adding
Option "NoAccel" "true" to xorg.conf resolves the problem which means it's a dri
problem.

The following dmesg output occurs when the X server crashs:
[drm:i810_wait_ring] *ERROR* space: 65512 wanted 65528
[drm:i810_wait_ring] *ERROR* lockup
[drm:i810_wait_ring] *ERROR* space: 65504 wanted 65528
[drm:i810_wait_ring] *ERROR* lockup

And from time to time (I think it's when i'm switching consoles while the X
server hangs with a black screen):
[drm:i810_unlock] *ERROR* Process 6632 using kernel context 0

/var/log/Xorg.0.log contains one warning but no errors:
(WW) I810(0): Bad V_BIOS checksum

I'm allocating 12288KB VideoRam otherwise DRI does not work for me (at least not
with 8192 or no VideoRam setting in xorg.conf).

If you need further informations tell me please. Happy new year besides...
Comment 5 Tobias Preclik 2005-02-14 15:23:07 UTC
As of 6.8.1.904 the problem seems to be fixed. 6.8.2 works well too. Thank you!
Can anyone confirm this?


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.