Attachment 4910 Details for Bug 6241 – Kernel output

Kernel output

r300-kernel (text/plain), 1.61 KB, created by Diego on 2006-03-13 10:36:13 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Diego

Created: 2006-03-13 10:36:13 UTC

Size: 1.61 KB

patch

obsolete

>Mar 13 00:23:00 calisto kernel: [drm] Setting GART location based on new memory map
>Mar 13 00:23:00 calisto kernel: [drm] Loading R300 Microcode
>Mar 13 00:23:00 calisto kernel: [drm] writeback test succeeded in 1 usecs
>Mar 13 00:26:34 calisto kernel: [drm] Setting GART location based on new memory map
>Mar 13 00:26:34 calisto kernel: [drm] Loading R300 Microcode
>Mar 13 00:26:34 calisto kernel: [drm] writeback test succeeded in 1 usecs
>Mar 13 00:26:45 calisto kernel: NTFS volume version 3.1.
>Mar 13 00:27:38 calisto kernel: [drm:r300_emit_3d_load_vbpntr] *ERROR* Offset failed range check (k=0 i=2) while processing 3D_LOAD_VBPNTR packet.
>Mar 13 00:27:38 calisto kernel: [drm:r300_emit_packet3] *ERROR* r300_emit_raw_packet3 failed
>Mar 13 00:27:38 calisto kernel: [drm:r300_do_cp_cmdbuf] *ERROR* r300_emit_packet3 failed
>Mar 13 00:29:12 calisto kernel: [drm] Loading R300 Microcode
>Mar 13 00:29:28 calisto kernel: [drm] Setting GART location based on new memory map
>Mar 13 00:29:28 calisto kernel: [drm] Loading R300 Microcode
>Mar 13 00:29:28 calisto kernel: [drm] writeback test succeeded in 1 usecs
>Mar 13 00:29:39 calisto kernel: [drm] Setting GART location based on new memory map
>Mar 13 00:29:39 calisto kernel: [drm] Loading R300 Microcode
>Mar 13 00:29:39 calisto kernel: [drm] writeback test succeeded in 1 usecs
>Mar 13 00:33:12 calisto kernel: [drm:r300_emit_3d_load_vbpntr] *ERROR* Offset failed range check (k=0 i=2) while processing 3D_LOAD_VBPNTR packet.
>Mar 13 00:33:12 calisto kernel: [drm:r300_emit_packet3] *ERROR* r300_emit_raw_packet3 failed
>Mar 13 00:33:12 calisto kernel: [drm:r300_do_cp_cmdbuf] *ERROR* r300_emit_packet3 failed

Actions: View

Attachments on bug 6241: 4909 | 4910 | 4996

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.