Re: 4.5.99.903 problem on Linux

2006-04-19 Thread David Dawes
On Wed, Apr 19, 2006 at 08:52:52PM +0900, Takaaki Nomura wrote:
>On Tue, 18 Apr 2006 19:27:36 -0400, David Dawes wrote:
>>On Fri, Apr 14, 2006 at 08:39:47PM +0900, Takaaki Nomura wrote:
>>>On Thu, 13 Apr 2006 20:27:29 -0400, David Dawes wrote:
On Wed, Apr 12, 2006 at 08:22:39PM +0900, Takaaki Nomura wrote:
>I've tested 4.5.99.903 on FreeBSD and Linux.
>
>When I terminated the server on Linux, I couldn't return to
>the console and the root window remained.
>
>The problem didn't occur on FreeBSD.
>
>I've attached the server log below.
>
>Are there any latest changes on the CVS version?

Not that would affect this.

Is the problem repeatable?  If so, can you get some debugging information
with gdb?  If you start the server with no clients, then exit, does the
problem still occur?  If the stack trace in the log is accurate, it shows
a crash in main().  A trace with gdb from a server built with debugging
info should help.

>Caught signal 11.
>Stack trace:
> 0: 0x808db5d: 0x808db40 xf86ShowStackTrace + 0x1d
>   Module "/usr/X11R6.6/bin/XFree86"
> 1: 0x808dc23: 0x808dbc0 xf86SigHandler + 0x63
>   Module "/usr/X11R6.6/bin/XFree86"
> 2: 0xe420: 0xe420 __kernel_sigreturn + 0x0
>   Module ""
> 3: 0x80d2946: 0x80d24c0 main + 0x486
>   Module "/usr/X11R6.6/bin/XFree86"
>
>Fatal server error:
>Server aborting

David
>>>
>>>It is repeatable on both of my two test PCs running Fedora Core 5.
>>>I've attached the static server logs below. One is with glint-based
>>>PC and the other is with i810-base PC.
>>>
>>>It's strange that gdb indicates the static symbol(variable)s of Enc61
>>>and i810_pitch_flags.
>>>
>>>Fedora Core 5 uses gcc 4.1.0.
>>>
>>>I can't test until next week.
>>
>>I've gotten access to a machine running FC5 and have reproduced this
>>problem.  It seems to be an array overrun.  The attached patch fixes it
>>for me.  Let me know how it goes for you.
>>
>>David
>
>I've tested the 4.5.99.903 static/loader servers with your patch on 
>both of my two test PCs running FC5. The problem didn't occur.
>It seemed to be fixed. Thanks a lot.

Thanks for the report and feedback.

David
___
Devel mailing list
Devel@XFree86.Org
http://XFree86.Org/mailman/listinfo/devel


Re: 4.5.99.903 problem on Linux

2006-04-19 Thread Takaaki Nomura
On Tue, 18 Apr 2006 19:27:36 -0400, David Dawes wrote:
>On Fri, Apr 14, 2006 at 08:39:47PM +0900, Takaaki Nomura wrote:
>>On Thu, 13 Apr 2006 20:27:29 -0400, David Dawes wrote:
>>>On Wed, Apr 12, 2006 at 08:22:39PM +0900, Takaaki Nomura wrote:
I've tested 4.5.99.903 on FreeBSD and Linux.

When I terminated the server on Linux, I couldn't return to
the console and the root window remained.

The problem didn't occur on FreeBSD.

I've attached the server log below.

Are there any latest changes on the CVS version?
>>>
>>>Not that would affect this.
>>>
>>>Is the problem repeatable?  If so, can you get some debugging information
>>>with gdb?  If you start the server with no clients, then exit, does the
>>>problem still occur?  If the stack trace in the log is accurate, it shows
>>>a crash in main().  A trace with gdb from a server built with debugging
>>>info should help.
>>>
Caught signal 11.
Stack trace:
 0: 0x808db5d: 0x808db40 xf86ShowStackTrace + 0x1d
Module "/usr/X11R6.6/bin/XFree86"
 1: 0x808dc23: 0x808dbc0 xf86SigHandler + 0x63
Module "/usr/X11R6.6/bin/XFree86"
 2: 0xe420: 0xe420 __kernel_sigreturn + 0x0
Module ""
 3: 0x80d2946: 0x80d24c0 main + 0x486
Module "/usr/X11R6.6/bin/XFree86"

Fatal server error:
Server aborting
>>>
>>>David
>>
>>It is repeatable on both of my two test PCs running Fedora Core 5.
>>I've attached the static server logs below. One is with glint-based
>>PC and the other is with i810-base PC.
>>
>>It's strange that gdb indicates the static symbol(variable)s of Enc61
>>and i810_pitch_flags.
>>
>>Fedora Core 5 uses gcc 4.1.0.
>>
>>I can't test until next week.
>
>I've gotten access to a machine running FC5 and have reproduced this
>problem.  It seems to be an array overrun.  The attached patch fixes it
>for me.  Let me know how it goes for you.
>
>David

I've tested the 4.5.99.903 static/loader servers with your patch on 
both of my two test PCs running FC5. The problem didn't occur.
It seemed to be fixed. Thanks a lot.

--
Takaaki Nomura
___
Devel mailing list
Devel@XFree86.Org
http://XFree86.Org/mailman/listinfo/devel


Re: 4.5.99.903 problem on Linux

2006-04-18 Thread David Dawes
On Fri, Apr 14, 2006 at 08:39:47PM +0900, Takaaki Nomura wrote:
>On Thu, 13 Apr 2006 20:27:29 -0400, David Dawes wrote:
>>On Wed, Apr 12, 2006 at 08:22:39PM +0900, Takaaki Nomura wrote:
>>>I've tested 4.5.99.903 on FreeBSD and Linux.
>>>
>>>When I terminated the server on Linux, I couldn't return to
>>>the console and the root window remained.
>>>
>>>The problem didn't occur on FreeBSD.
>>>
>>>I've attached the server log below.
>>>
>>>Are there any latest changes on the CVS version?
>>
>>Not that would affect this.
>>
>>Is the problem repeatable?  If so, can you get some debugging information
>>with gdb?  If you start the server with no clients, then exit, does the
>>problem still occur?  If the stack trace in the log is accurate, it shows
>>a crash in main().  A trace with gdb from a server built with debugging
>>info should help.
>>
>>>Caught signal 11.
>>>Stack trace:
>>> 0: 0x808db5d: 0x808db40 xf86ShowStackTrace + 0x1d
>>> Module "/usr/X11R6.6/bin/XFree86"
>>> 1: 0x808dc23: 0x808dbc0 xf86SigHandler + 0x63
>>> Module "/usr/X11R6.6/bin/XFree86"
>>> 2: 0xe420: 0xe420 __kernel_sigreturn + 0x0
>>> Module ""
>>> 3: 0x80d2946: 0x80d24c0 main + 0x486
>>> Module "/usr/X11R6.6/bin/XFree86"
>>>
>>>Fatal server error:
>>>Server aborting
>>
>>David
>
>It is repeatable on both of my two test PCs running Fedora Core 5.
>I've attached the static server logs below. One is with glint-based
>PC and the other is with i810-base PC.
>
>It's strange that gdb indicates the static symbol(variable)s of Enc61
>and i810_pitch_flags.
>
>Fedora Core 5 uses gcc 4.1.0.
>
>I can't test until next week.

I've gotten access to a machine running FC5 and have reproduced this
problem.  It seems to be an array overrun.  The attached patch fixes it
for me.  Let me know how it goes for you.

David
Index: common/xf86KbdLnx.c
===
RCS file: /home/x-cvs/xc/programs/Xserver/hw/xfree86/common/xf86KbdLnx.c,v
retrieving revision 3.21
diff -u -r3.21 xf86KbdLnx.c
--- common/xf86KbdLnx.c 20 Feb 2006 00:14:37 -  3.21
+++ common/xf86KbdLnx.c 18 Apr 2006 23:23:22 -
@@ -364,7 +364,7 @@
   }
   else {
 k = map+GLYPHS_PER_KEY;
-maxkey = NUM_AT2LNX;
+maxkey = NUM_AT2LNX - 1;
   }
 
   for (i = 0; i < maxkey; ++i)
Index: os-support/linux/lnx_KbdMap.c
===
RCS file: 
/home/x-cvs/xc/programs/Xserver/hw/xfree86/os-support/linux/lnx_KbdMap.c,v
retrieving revision 1.4
diff -u -r1.4 lnx_KbdMap.c
--- os-support/linux/lnx_KbdMap.c   20 Feb 2006 00:14:37 -  1.4
+++ os-support/linux/lnx_KbdMap.c   18 Apr 2006 23:23:18 -
@@ -287,7 +287,7 @@
   }
   else {
 k = map+GLYPHS_PER_KEY;
-maxkey = NUM_AT2LNX;
+maxkey = NUM_AT2LNX - 1;
   }
 
   for (i = 0; i < maxkey; ++i)


Re: 4.5.99.903 problem on Linux

2006-04-14 Thread Takaaki Nomura
On Thu, 13 Apr 2006 20:27:29 -0400, David Dawes wrote:
>On Wed, Apr 12, 2006 at 08:22:39PM +0900, Takaaki Nomura wrote:
>>I've tested 4.5.99.903 on FreeBSD and Linux.
>>
>>When I terminated the server on Linux, I couldn't return to
>>the console and the root window remained.
>>
>>The problem didn't occur on FreeBSD.
>>
>>I've attached the server log below.
>>
>>Are there any latest changes on the CVS version?
>
>Not that would affect this.
>
>Is the problem repeatable?  If so, can you get some debugging information
>with gdb?  If you start the server with no clients, then exit, does the
>problem still occur?  If the stack trace in the log is accurate, it shows
>a crash in main().  A trace with gdb from a server built with debugging
>info should help.
>
>>Caught signal 11.
>>Stack trace:
>> 0: 0x808db5d: 0x808db40 xf86ShowStackTrace + 0x1d
>>  Module "/usr/X11R6.6/bin/XFree86"
>> 1: 0x808dc23: 0x808dbc0 xf86SigHandler + 0x63
>>  Module "/usr/X11R6.6/bin/XFree86"
>> 2: 0xe420: 0xe420 __kernel_sigreturn + 0x0
>>  Module ""
>> 3: 0x80d2946: 0x80d24c0 main + 0x486
>>  Module "/usr/X11R6.6/bin/XFree86"
>>
>>Fatal server error:
>>Server aborting
>
>David

It is repeatable on both of my two test PCs running Fedora Core 5.
I've attached the static server logs below. One is with glint-based
PC and the other is with i810-base PC.

It's strange that gdb indicates the static symbol(variable)s of Enc61
and i810_pitch_flags.

Fedora Core 5 uses gcc 4.1.0.

I can't test until next week.

--
Takaaki Nomura

-
[EMAIL PROTECTED] bin]# gdb XFree86.static.4.5.99.903 < gdb.cmd
GNU gdb Red Hat Linux (6.3.0.0-1.122rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".

(gdb) Starting program: /usr/X11R6.6/bin/XFree86.static.4.5.99.903 
Reading symbols from shared object read from target memory...(no debugging 
symbols found)...done.
Loaded system supplied DSO at 0xe000
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

This is a pre-release version of XFree86, and is not supported in any
way.  Bugs may be reported to XFree86@XFree86.Org and patches submitted
to [EMAIL PROTECTED]  Before reporting bugs in pre-release versions,
please check the latest version in the XFree86 CVS repository
(http://www.XFree86.Org/cvs).

XFree86 Version 4.5.99.903 (4.6.0 RC 3)
Release Date: 8 April 2006
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.16.4 i686 [ELF] 
Current Operating System: Linux nomura-ux 2.6.16.4 #1 Wed Apr 12 10:40:03 JST 
2006 i686
Build Date: 12 April 2006
Changelog Date: 8 April 2006
Before reporting problems, check http://www.XFree86.Org/
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (EE) error, (WW) warning,
(II) informational, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Fri Apr 14 10:32:25 2006
(==) Using config file: "/etc/XF86Config".
Detaching after fork from child process 3060.

Program received signal SIGSEGV, Segmentation fault.
0x087525f4 in Enc61 ()
(gdb) #0  0x087525f4 in Enc61 ()
#1  0x0853fa64 in AnimCurCloseScreen ()
#2  0x08416076 in main ()
(gdb) [EMAIL PROTECTED] bin]# 
[EMAIL PROTECTED] bin]# exit
-
[EMAIL PROTECTED] gdb XFree86.static.4.5.99.903 < gdb.cmd
GNU gdb Red Hat Linux (6.3.0.0-1.122rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".

(gdb) Starting program: /usr/X11R6.6/bin/XFree86.static.4.5.99.903 
Reading symbols from shared object read from target memory...(no debugging 
symbols found)...done.
Loaded system supplied DSO at 0xe000
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/nomura-xp:0
_XSERVTransMakeAllCOTSSer

Re: 4.5.99.903 problem on Linux

2006-04-13 Thread David Dawes
On Wed, Apr 12, 2006 at 08:22:39PM +0900, Takaaki Nomura wrote:
>I've tested 4.5.99.903 on FreeBSD and Linux.
>
>When I terminated the server on Linux, I couldn't return to
>the console and the root window remained.
>
>The problem didn't occur on FreeBSD.
>
>I've attached the server log below.
>
>Are there any latest changes on the CVS version?

Not that would affect this.

Is the problem repeatable?  If so, can you get some debugging information
with gdb?  If you start the server with no clients, then exit, does the
problem still occur?  If the stack trace in the log is accurate, it shows
a crash in main().  A trace with gdb from a server built with debugging
info should help.

>Caught signal 11.
>Stack trace:
> 0: 0x808db5d: 0x808db40 xf86ShowStackTrace + 0x1d
>   Module "/usr/X11R6.6/bin/XFree86"
> 1: 0x808dc23: 0x808dbc0 xf86SigHandler + 0x63
>   Module "/usr/X11R6.6/bin/XFree86"
> 2: 0xe420: 0xe420 __kernel_sigreturn + 0x0
>   Module ""
> 3: 0x80d2946: 0x80d24c0 main + 0x486
>   Module "/usr/X11R6.6/bin/XFree86"
>
>Fatal server error:
>Server aborting

David
___
Devel mailing list
Devel@XFree86.Org
http://XFree86.Org/mailman/listinfo/devel


4.5.99.903 problem on Linux

2006-04-12 Thread Takaaki Nomura
I've tested 4.5.99.903 on FreeBSD and Linux.

When I terminated the server on Linux, I couldn't return to
the console and the root window remained.

The problem didn't occur on FreeBSD.

I've attached the server log below.

Are there any latest changes on the CVS version?

--
Takaaki Nomura

This is a pre-release version of XFree86, and is not supported in any
way.  Bugs may be reported to XFree86@XFree86.Org and patches submitted
to [EMAIL PROTECTED]  Before reporting bugs in pre-release versions,
please check the latest version in the XFree86 CVS repository
(http://www.XFree86.Org/cvs).

XFree86 Version 4.5.99.903 (4.6.0 RC 3)
Release Date: 8 April 2006
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.16.4 i686 [ELF] 
Current Operating System: Linux nomura-ux 2.6.16.4 #1 Wed Apr 12 10:40:03 JST 
2006 i686
Build Date: 12 April 2006
Changelog Date: 8 April 2006
Before reporting problems, check http://www.XFree86.Org/
to make sure that you have the latest version.
Module Loader present
Command line: /usr/X11R6.6/bin/X :0 -verbose 1
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (EE) error, (WW) warning,
(II) informational, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/XFree86.0.log", Time: Wed Apr 12 15:07:21 2006
(==) Using config file: "/etc/XF86Config".
(II) Executable is "/usr/X11R6.6/bin/XFree86".
(II) Reading symbols from "/usr/X11R6.6/bin/XFree86".
(II) Module ABI versions:
XFree86 ANSI C Emulation: 0.3
XFree86 Video Driver: 0.10
XFree86 XInput driver : 0.5
XFree86 Server Extension : 0.4
XFree86 Font Renderer : 0.5
(II) Loader running on linux
(**) Option "Protocol" "Standard"
(**) Option "AutoRepeat" "500 5"
(**) Option "XkbModel" "jp106"
(**) XKB: model: "jp106"
(**) Option "XkbLayout" "jp"
(**) XKB: layout: "jp"
(==) Keyboard: CustomKeycode disabled.
(==) ServerLayout "simple layout"
(==) |-->Screen "Screen 1" (0) (0, 0)
(**) |  |-->Device "Oxygen"
(**) |  |-->Monitor "Multisync" (0)
(**) |-->Input Device "Mouse1"
(**) |-->Input Device "Keyboard1"
(**) FontPath set to 
"/usr/X11R6.6/lib/X11/fonts/misc/,/usr/X11R6.6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6.6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6.6/lib/X11/fonts/Type1/,/usr/X11R6.6/lib/X11/fonts/Speedo/,/usr/X11R6.6/lib/X11/fonts/75dpi/,/usr/X11R6.6/lib/X11/fonts/100dpi/"
(**) RgbPath set to "/usr/X11R6.6/lib/X11/rgb"
(**) ModulePath set to "/usr/X11R6.6/lib/modules"
(II) Checking for unused ServerFlags options:
(II) LoadModule: "pcidata"
(II) Loading /usr/X11R6.6/lib/modules/libpcidata.a
(II) Module pcidata: vendor="The XFree86 Project"
compiled for 4.5.99.903, module version = 1.0.0
ABI class: XFree86 Video Driver, version 0.10
(II) LoadModule: "bitmap"
(II) Loading /usr/X11R6.6/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor="The XFree86 Project"
compiled for 4.5.99.903, module version = 1.0.0
Module class: XFree86 Font Renderer
ABI class: XFree86 Font Renderer, version 0.5
(II) Loading font Bitmap
(--) using VT number 7

(II) PCI: Probing config type using method 1
(II) PCI: Config type is 1
(II) PCI: stages = 0x03, oldVal1 = 0x8002183c, mode1Res1 = 0x8000
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,7190 card 8086,7190 rev 03 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 8086,7191 card , rev 03 class 06,04,00 hdr 01
(II) PCI: 00:07:0: chip 8086,7110 card , rev 02 class 06,01,00 hdr 80
(II) PCI: 00:07:1: chip 8086,7111 card , rev 01 class 01,01,80 hdr 00
(II) PCI: 00:07:2: chip 8086,7112 card , rev 01 class 0c,03,00 hdr 00
(II) PCI: 00:07:3: chip 8086,7113 card , rev 02 class 06,80,00 hdr 00
(II) PCI: 00:0b:0: chip 1000,000f card 1000,1000 rev 26 class 01,00,00 hdr 00
(II) PCI: 00:0c:0: chip 9005,0010 card 9005,2180 rev 00 class 01,00,00 hdr 00
(II) PCI: 00:0e:0: chip 3388,0021 card , rev 15 class 06,04,00 hdr 01
(II) PCI: 00:10:0: chip 8086,1229 card 1054,1229 rev 05 class 02,00,00 hdr 00
(II) PCI: 01:00:0: chip 3d3d,000a card 3d3d,0125 rev 01 class 03,00,00 hdr 00
(II) PCI: 02:00:0: chip 10ec,8169 card 10fc,d026 rev 10 class 02,00,00 hdr 00
(II) PCI: 02:01:0: chip 1033,0035 card 10fc,d026 rev 43 class 0c,03,10 hdr 80
(II) PCI: 02:01:1: chip 1033,0035 card 10fc,d026 rev 43 class 0c,03,10 hdr 00
(II) PCI: 02:01:2: chip 1033,00e0 card 10fc,d026 rev 04 class 0c,03,20 hdr 00
(II) PCI: 02:03:0: chip 104c,8024 card 10fc,d026 rev 00 class 0c,00,10 hdr 00
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,2), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1  0   0x - 0x (0x1) IX[B]
(II) Bus 0 non-prefetchable memory range:
[0] -1  0   0x - 0x (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
[0] -1  0   0x - 0x (0x0) MX[B]
(II)