Re: another i810 crash when switching bewteen X and text console

[loic.mahe@xxxxxxxxxxxxxx]

Sorry to be late, but I had to switch to another activity.

I made some tests with the lastest build (4.7.99.3).
The PC (Dell GX270) is
cold-started between each test, since it seems that
a simple reboot doesn't
reset the BIOS.

> (Christian)
> A question to the person who started this thread:
Does setting the
> "VideoRam" option in the "Device" section of the
XFree86 configuration
> file to 32000 and not running 865patch help?

Test with VideoRam set to 32000 in the config file
and 865patch not started.
Here are the significant log lines (I can send the
whole file upon demand) :

(II) I810(0): VESA VBE Total Mem: 8064 kB
(WW) I810(0): Detected stolen memory (8000 kB)
doesn't match what the BIOS reports (8064 kB)
(II) I810(0): Will attempt to tell the BIOS that there is 12288 kB VideoRAM
(WW) I810(0): Extended BIOS function 0x5f11 not
supported.
(II) I810(0): BIOS view of memory size can't be
changed (this is not an error)
(**) I810(0): VideoRAM: 32000 kByte
(--) I810(0): Maximum frambuffer space: 31832 kByte
(--) I810(0): Maximum space available for video
modes: 8064 kByte
(II) I810(0): VESA VBE Total Mem: 0 kB
(II) I810(0): BIOS call 0x5f05 not supported, setting
refresh with VBE 3 method.

What is strange here is the second "VESA VBE
Total Mem:" line, which indicates 0 kB !!!

Then, if I switch to the text console and back, the
crash is still here :

(WW) I810(0): PGTBL_ER is 0x00000029

   *** If unresolved symbols were reported
above, they might not
   *** be the reason for the server aborting.

Caught signal 11.
Stack trace:
 0: 0x808e796: 0x808e780 xf86ShowStackTrace
+ 0x16
        Module "/usr/X11R6/bin/XFree86"
 1: 0x808e8a8: 0x808e820 xf86SigHandler +
0x88
        Module "/usr/X11R6/bin/XFree86"
 2: 0x400828b8: <cannot guess>
 3: 0x40561734: 0x405615c0 I830BIOSEnterVT
+ 0x174
        Module "/usr/X11R6/lib/modules/drivers/i810_drv.o"
        Section ".text"
 4: 0x406eb307: 0x406eb2e0 XAAEnterVT + 0x27
        Module "/usr/X11R6/lib/modules/libxaa.a:xaaInit.o"
        Section ".text"
 5: 0x4073c41a: 0x4073c3f0 xf86CursorEnterVT
+ 0x2a
        Module "/usr/X11R6/lib/modules/libramdac.a:xf86Cursor.o"
        Section ".text"
 6: 0x810ca6e: 0x810ca40 CMapEnterVT + 0x2e
        Module "/usr/X11R6/bin/XFree86"
 7: 0x810a7ec: 0x810a7c0 xf86XVEnterVT + 0x2c
        Module "/usr/X11R6/bin/XFree86"
 8: 0x808eb9f: 0x808e8c0 xf86VTSwitch + 0x2df
        Module "/usr/X11R6/bin/XFree86"
 9: 0x808e6ae: 0x808e4f0 xf86Wakeup + 0x1be
        Module "/usr/X11R6/bin/XFree86"
10: 0x80c645c: 0x80c6420 WakeupHandler + 0x3c
        Module "/usr/X11R6/bin/XFree86"
11: 0x80e196a: 0x80e15b0 WaitForSomething + 0x3ba
        Module "/usr/X11R6/bin/XFree86"
12: 0x80c00b4: 0x80c0040 Dispatch + 0x74
        Module "/usr/X11R6/bin/XFree86"
13: 0x80d10cb: 0x80d0b30 main + 0x59b
        Module "/usr/X11R6/bin/XFree86"

Fatal server error:
Server aborting

After the crash (without reboot), X starts again (since
it's respawned by init)
and here are again the significant log lines :

(WW) I810(0): Bad V_BIOS checksum
(II) I810(0): VESA VBE Total Mem: 0 kB
(WW) I810(0): Detected stolen memory (8000 kB)
doesn't match what the BIOS reports (0 kB)
(II) UnloadSubModule: "int10"
(II) Loading sub module "int10"
(II) I810(0): VESA VBE Total Mem: 12288 kB
(II) I810(0): Tweak BIOS image to 12288 kB VideoRAM
(==) I810(0): VideoRAM: 65536 kByte
(--) I810(0): Maximum frambuffer space: 65368 kByte
(--) I810(0): Maximum space available for video
modes: 12288 kByte
(WW) I810(0): Extended BIOS function 0x5f05 failed.

So I think the 865patch is still need for the 865G
on the Dell GX270.

This is not a problem for me, as I previoulsy stated,
since at installation
time (RedHat's anaconda), the Video Memory isn't always
correctly detected
(and it's perhaps to confusing for the end-user).
So I prefer not to use this configuration option and
use the 865patch.

> (Marc)
> Indeed.  The problem is that zero isn't
recognised as a valid
> TweakMemorySize() return.  The attached, which I've already committed,
> should fix this.

I'm not sure, since every time I don't use the 865patch,
with or without
the VideoRam parameter, I get these messages on the
second int10 launch
(before drmOpenDevice).

(WW) I810(0): Bad V_BIOS checksum
(II) I810(0): VESA VBE Total Mem: 0 kB

And the crash still occurs after switch to text console
and back.

Loïc