After start X displays artifacts on a screen, mostly at its bottom. Switching to console causes crash and lock of a kernel with some responsibility to magic sysrq. I used yesterday git versions of drm, xf86-video-nouveau and mesa on slamd64-current linux (64 bit) distribution, linux 2.6.22.7 with SMP support on Athlon dual core CPU, nvidiafb module was loaded.
Created attachment 11772 [details] output from lspci -vv
Created attachment 11773 [details] Xorg.0.log
Created attachment 11774 [details] xorg.conf
Could you please retry without the nvidiafb module (this is not supported) and provide a kernel log ?
Without nvidiafb linux kernel did not hang. By the way other drm modules (ati) can work simultaneously with framebuffer. After start there were artifacts on a screen, moving of cursor or windows caused changes in the artifacts. 2D speed was (for example moving a window in KDE) much lower than for "nv" driver. xdriinfo displayed nouveau driver, glxinfo showed direct rendering. Start of glxgears opened black window, screen was locked (no reaction on mouse or keyboard), then after several seconds X crashed. After that /var/log/messages has following: Sep 27 18:31:44 darkstar kernel: [drm] Allocating FIFO number 0 Sep 27 18:31:44 darkstar kernel: [drm] nouveau_fifo_alloc: initialised FIFO 0 Sep 27 18:31:44 darkstar kernel: [drm] Allocating FIFO number 1 Sep 27 18:31:44 darkstar kernel: [drm] nouveau_fifo_alloc: initialised FIFO 1 Sep 27 18:31:58 darkstar kernel: [drm] Allocating FIFO number 2 Sep 27 18:31:58 darkstar kernel: [drm] nouveau_fifo_alloc: initialised FIFO 2 Sep 27 18:31:58 darkstar kernel: [drm] nouveau_fifo_free: freeing fifo 2 Sep 27 18:32:22 darkstar kernel: [drm] Allocating FIFO number 2 Sep 27 18:32:22 darkstar kernel: [drm] nouveau_fifo_alloc: initialised FIFO 2 Sep 27 18:32:28 darkstar kernel: [drm] nouveau_fifo_free: freeing fifo 1 Sep 27 18:32:28 darkstar kernel: [drm] nouveau_fifo_free: freeing fifo 2 Sep 27 18:32:28 darkstar kernel: [drm] nouveau_fifo_free: freeing fifo 0 and /var/log/syslog: Sep 27 18:32:22 darkstar kernel: [drm:nouveau_pgraph_irq_handler] *ERROR* PGRAPH error interrupt Sep 27 18:32:22 darkstar kernel: [drm:nouveau_graph_dump_trap_info] *ERROR* nSource: DATA_ERROR, nStatus: BAD_ARGUMENT Sep 27 18:32:22 darkstar kernel: [drm:nouveau_graph_dump_trap_info] *ERROR* Channel 2/0 (class 0x0062) - Method 0x0304, Data 0x00000000:0x15e004c0
Created attachment 11790 [details] Xorg.0.log made without nvidiafb
Created attachment 11791 [details] screenshot of artifacts
Something is using opengl (as testified by the kernel's "Allocating FIFO number 2"). IF you do not install nouveua_dri.so, do you still have 2D corruption (which is what I'm interested in fixing ATM).
I tried to remove nouveua_dri.so and there are still artefacts on the screen.
Created attachment 12364 [details] the screenshot of glxgears This screenshot was made with nouveau (mesa, drm) drivers as of 2007.10.31. It does not crash or cause kernel lock anymore. But the output of glxgears is very distorted. Morever, the new 2d artefact introduced: sometimes fonts are too bright (like in the gkrellm window on the screenshot).
Were you the person with Graphic Context Size issue that came to the irc channel?
Closing due to lack of information.
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.