From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040217 Description of problem: When I boot to either of these kernels, everything else I have tested has worked. However, if I attempt to lock the screen within X, the screen blacks and input is no longer accepted. I can get the machine to safely shutdown by tapping the power button once. The last kernel to work properly was kernel-smp-2.6.3-1.118. Version-Release number of selected component (if applicable): kernel-smp-2.6.3-2.1.240 and kernel-smp-2.6.3-2.1.242 How reproducible: Always Steps to Reproduce: 1.Boot to either of the kernels shown 2.Log into X 3.Lock the screen from the menu Actual Results: Monitor blacks out, and all terminal input is rejected. Expected Results: Usual screen locking ie: xscreensaver starting properly. Additional info: Motherboard: Intel D865GBFLK Proccessor: Intel Pentium 4 C 2.8Ghz (Hyper Threading enabled in BIOS) Ram: 512MB GEIL DDR in Dual Channel Mode Video: Onboard Intel Extreme 2(which does have a bug in X regarding the refresh rate a patch exists but has not been committed)
Created attachment 98362 [details] Relevant output from /var/log/messages
Mar 7 16:22:24 snore kernel: [<21904099>] i830_dma_dispatch_vertex+0x1c2/0x469 [i830] Mar 7 16:22:24 snore kernel: [<021fb665>] vt_console_print+0x0/0x289 Mar 7 16:22:24 snore kernel: [<21904099>] i830_dma_dispatch_vertex+0x1c2/0x469 [i830] Mar 7 16:22:24 snore kernel: [<0215fa07>] get_user_size+0x2e/0x55 Mar 7 16:22:24 snore kernel: [<21904099>] i830_dma_dispatch_vertex+0x1c2/0x469 [i830] Mar 7 16:22:24 snore kernel: [<0210dc12>] handle_BUG+0x32/0xdf Mar 7 16:22:24 snore kernel: [<0210dd23>] die+0x64/0x124 Mar 7 16:22:24 snore kernel: [<02120501>] do_page_fault+0x2fe/0x4b5 Mar 7 16:22:24 snore kernel: [<21904099>] i830_dma_dispatch_vertex+0x1c2/0x469 [i830] Mar 7 16:22:24 snore kernel: [<021ae572>] avc_has_perm+0x3f/0x49 Mar 7 16:22:24 snore kernel: [<021af8e8>] inode_has_perm+0x57/0x5f Mar 7 16:22:24 snore kernel: [<02120203>] do_page_fault+0x0/0x4b5 Mar 7 16:22:24 snore kernel: [<21904099>] i830_dma_dispatch_vertex+0x1c2/0x469 [i830] Mar 7 16:22:24 snore kernel: [<2190463b>] i830_dma_vertex+0xbb/0xdf [i830] Mar 7 16:22:24 snore kernel: [<218ff850>] i830_ioctl+0xe5/0xf2 [i830] Mar 7 16:22:24 snore kernel: [<21904580>] i830_dma_vertex+0x0/0xdf [i830] Mar 7 16:22:24 snore kernel: [<02173545>] sys_ioctl+0x243/0x2a6
*** Bug 117780 has been marked as a duplicate of this bug. ***
Is this a dupe of 117642? EIP is almost at the same place: i830_dma_dispatch_vertex+0x1c2/0x469 in both cases.
It certainly sounds the similar enough to be the same issue.
*** Bug 117642 has been marked as a duplicate of this bug. ***
*** Bug 118527 has been marked as a duplicate of this bug. ***
i830+ DRM and 4/4 split do *not* get along; they've never worked together.
I just found + fixed a bug in this specific function that perfectly explains the oops; the kernel with the fix is available from http://people.redhat.com/arjanv/2.6/
I still have Problems with the i810 driver, it freezes when I try the glblur screensaver, there are errors like Mar 23 17:11:17 itspc114 kernel: [drm:i810_wait_ring] *ERROR* space: 65300 wanted 65528 Mar 23 17:11:17 itspc114 kernel: [drm:i810_wait_ring] *ERROR* lockup Mar 23 17:11:22 itspc114 kernel: [drm:i810_wait_ring] *ERROR* space: 65284 wanted 65528 Mar 23 17:11:22 itspc114 kernel: [drm:i810_wait_ring] *ERROR* lockup Mar 23 17:13:51 itspc114 kernel: [drm:i810_wait_ring] *ERROR* space: 65276 wanted 65528 Mar 23 17:13:51 itspc114 kernel: [drm:i810_wait_ring] *ERROR* lockup in /var/log/messages, and Error in I810WaitLpRing(), now is 88290, start is 86289 pgetbl_ctl: 0xfd10001 pgetbl_err: 0x0 ipeir: 4 iphdr: 3f5f56ef LP ring tail: 3db0 head: 3cc4 len: f001 start 580000 eir: 0 esr: 1 emr: 3d instdone: ff72 instpm: 0 memmode: 24 instps: 830 hwstam: 9ac7 ier: 0 imr: 9ac7 iir: 0 space: 65292 wanted 65528 (II) I810(0): [drm] removed 1 reserved context for kernel (II) I810(0): [drm] unmapping 8192 bytes of SAREA 0x129d7000 at 0xf6ef1000 Fatal server error: lockup in /var/log/XFree86.0.log This is with xorg-x11-0.0.6.6-0.0.2004_03_11.6 and kernel-2.6.4-1.286
THAT is an entirely different matter and maybe an X bug (most likely actually)
Well, I get the same error as Michael Young's X errors. I've updated/installed the xorg packages so I can not say what will happen with the "old" XFree86 packages. Should this be a different bugzilla notice?
*** Bug 119301 has been marked as a duplicate of this bug. ***
*** Bug 119496 has been marked as a duplicate of this bug. ***
FYI, the subsequent problem in "drm:i810_wait_ring" has been reported as #119705 for the xorg-x11 component.
small success message. i'm running w/ 2.6.5-1.326 and found explanations on the web wrt. mtrr and dri. turns out that the 4MB mtrr setup done by the vesafb driver cannot be reused/changed by the x-server. fix is to manually disable this segment (echo "disable=06" > /proc/mtrr; 06 is the segment number on my machine) before starting the x-server. i can enable dri in the xconfig and see accelerated gfx. only downside is that the x-server (esp. the i810 videodrv) generates oopses on restart randomly. i can provide the log entries but a feeling tells me this will go away with newer x11 versions.
The latest rawhide kernel has i8xx DRM fixes which are believed may resolve this issue. Details can be found in bug #119311. Please test Fedora Core 2 test3 fully updated with the latest rawhide updates, and see if the problem is resolved for you with this new kernel or not. Setting bug status to "MODIFIED" pending user testing. Please change status to "RAWHIDE" if the problem is resolved now, or back to "ASSIGNED" if it persists.
Thank you. The glx xscreensaver modules now work for my toshiba laptop. Good work.
Works for me too. With the -349 kernel the GLblur screen saver causes a hang but it works with the -350 kernel.
Yay, -350 seems to be working well here too. :-)
I still have Problems with the i810 driver :(, it freezes when I try to run tuxracer or quake 3. I had the same error that Michael Young in the COmment 10. I'm running on Fedora COre 2 final (Kernel 2.6.5-1.358) on a P3 with a i810 motherboard. thx for any help..