Attachment 4557 Details for Bug 5795 – this log file shows (only) the switching between consoles

this log file shows (only) the switching between consoles

Xorg.0.log (text/plain), 3.20 KB, created by Raphael Langerhorst on 2006-02-05 22:41:29 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Raphael Langerhorst

Created: 2006-02-05 22:41:29 UTC

Size: 3.20 KB

patch

obsolete

>(**) Keyboard1: XkbRules: "xorg"
>(**) Option "XkbModel" "pc105"
>(**) Keyboard1: XkbModel: "pc105"
>(**) Option "XkbLayout" "de"
>(**) Keyboard1: XkbLayout: "de"
>(**) Option "CustomKeycodes" "off"
>(**) Keyboard1: CustomKeycodes disabled
>(II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD)
>(II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE)
>Could not init font path element /usr/pkg/share/tex-contrib/BaKoMa/ttf/, removing from list!
>(WW) I810(0): Successfully set original devices
>(II) I810(0): xf86UnbindGARTMemory: unbind key 4
>(II) I810(0): xf86UnbindGARTMemory: unbind key 0
>(II) I810(0): xf86UnbindGARTMemory: unbind key 1
>(II) I810(0): xf86UnbindGARTMemory: unbind key 3
>(II) I810(0): xf86UnbindGARTMemory: unbind key 2
>(WW) I810(0): Successfully set original devices (2)
>(II) I810(0): Detected resume, re-POSTing.
>(WW) I810(0): remove MTRR a0000 - c0000
>(WW) I810(0): Bad V_BIOS checksum
>(II) I810(0): Primary V_BIOS segment is: 0xc000
>(WW) I810(0): remove MTRR 0 - 1000
>(WW) I810(0): remove MTRR 0 - 1000
>(II) I810(0): Re-POSTing via int10.
>(II) I810(0): xf86BindGARTMemory: bind key 4 at 0x000df000 (pgoffset 223)
>(II) I810(0): xf86BindGARTMemory: bind key 0 at 0x07fff000 (pgoffset 32767)
>(II) I810(0): xf86BindGARTMemory: bind key 1 at 0x07ffb000 (pgoffset 32763)
>(II) I810(0): xf86BindGARTMemory: bind key 3 at 0x07fea000 (pgoffset 32746)
>(II) I810(0): xf86BindGARTMemory: bind key 2 at 0x07ffa000 (pgoffset 32762)
>(WW) I810(0): PRB0_HEAD (0x00666708) and PRB0_TAIL (0x000b6658) indicate ring buffer not flushed
>(II) I810(0): Before: SWF1 is 0x00000001
>(II) I810(0): After: SWF1 is 0x00000008
>(II) Loading sub module "ddc"
>(II) LoadModule: "ddc"
>(II) Reloading /usr/pkg/xorg/lib/modules/libddc.so
>(II) I810(0): VESA VBE DDC supported
>(II) I810(0): VESA VBE DDC Level none
>(II) I810(0): VESA VBE DDC transfer in appr. 0 sec.
>(II) I810(0): VESA VBE DDC read failed
>(II) I810(0): Display plane A is enabled and connected to Pipe A.
>(II) I810(0): Display plane B is disabled and connected to Pipe B.
>(II) I810(0): Enabling plane A.
>(II) I810(0): Display plane A is now enabled and connected to Pipe A.
>(II) I810(0): Display plane B is now disabled and connected to Pipe B.
>(II) I810(0): PIPEACONF is 0x80000000
>(II) I810(0): PIPEBCONF is 0x80000000
>(II) I810(0): Mode bandwidth is 47 Mpixel/s
>(II) I810(0): maxBandwidth is 640 Mbyte/s, pipe bandwidths are 252 Mbyte/s, 0 Mbyte/s
>Error in I830WaitLpRing(), now is 973430469, start is 973428468
>pgetbl_ctl: 0xff60001 pgetbl_err: 0x1d
>ipeir: 0 iphdr: 77544242
>LP ring tail: 8 head: 1f8 len: 1f001 start 0
>eir: 0 esr: 11 emr: ffff
>instdone: ffc1 instpm: 0
>memmode: 108 instps: c2e
>hwstam: ffff ier: 0 imr: ffff iir: 0
>space: 488 wanted 131064
>
>Fatal server error:
>lockup
>
>
>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 I830WaitLpRing(), now is 973432471, start is 973430470
>pgetbl_ctl: 0xff60001 pgetbl_err: 0x1d
>ipeir: 0 iphdr: 77544242
>LP ring tail: 10 head: 200 len: 1f001 start 0
>eir: 0 esr: 11 emr: ffff
>instdone: ffc1 instpm: 0
>memmode: 108 instps: c2e
>hwstam: ffff ier: 0 imr: ffff iir: 0
>space: 488 wanted 131064
>
>FatalError re-entered, aborting
>lockup
>

Actions: View

Attachments on bug 5795: 4556 | 4557 | 4558 | 4559 | 5025 | 5535 | 5992 | 6077 | 6137 | 6151 | 6153 | 6318 | 7247 | 7252 | 7253 | 7254 | 7255 | 7256 | 7257 | 7258 | 7259 | 7260 | 7261 | 7264 | 7265 | 7320 | 7321

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.