[Bug 330052] Re: Xvfb crashes with SIGSEGV in FreeColormap()

2009-09-16 Thread Adam Dickmeiss
Compiled xvfb (2:1.6.0-0ubuntu14) from deb sources but with debugging
enabled and no stripping..

a...@durum:~/xvfb$ diff rules xorg-server-1.6.0/debian/rules 
16c16
   CFLAGS += -O0
---
   CFLAGS += -O2
181c181
   # dh_strip -s --dbg-package=xserver-xorg-core
---
   dh_strip -s --dbg-package=xserver-xorg-core

In console 1:
   valgrind Xvfb  -auth hosts :1 
In console 2:
   xeyes  -display :1

** Attachment added: Valgrind output
   http://launchpadlibrarian.net/31895042/xvfb.valgrind.lst

-- 
Xvfb crashes with SIGSEGV in FreeColormap()
https://bugs.launchpad.net/bugs/330052
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 330052] Re: Xvfb crashes with SIGSEGV in FreeColormap()

2009-09-16 Thread Adam Dickmeiss
valgrind output shows that the immediate problem is that xrealloc in
glx/glxscreen.c:276 causes some colormaps to have a bad pVisual member..
That is : some colormaps STILL point to the old memory .. In other
words.. not all colormaps gets fixed up in AddScreenVisuals. Here is a
gdb session where we track the colormaps created/destroyed.

a...@durum:~/xvfb$ gdb --args Xvfb  -auth hosts :1 
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu...
(gdb) break colormap.c:279
Breakpoint 1 at 0x56db8c: file ../../dix/colormap.c, line 279.
(gdb) break FreeColormap
Breakpoint 2 at 0x56e2d1: file ../../dix/colormap.c, line 428.
(gdb) run
Starting program: /usr/bin/Xvfb -auth hosts :1
[Thread debugging using libthread_db enabled]
[New Thread 0x7f0639991710 (LWP 3767)]
[Switching to Thread 0x7f0639991710 (LWP 3767)]

Breakpoint 1, CreateColormap (mid=32, pScreen=0x2253800, pVisual=0x2253dc0, 
ppcmap=0x7fff419bba90, alloc=0, client=0) at ../../dix/colormap.c:279
279 if (!pmap)
(gdb) print pmap
$1 = (ColormapPtr) 0x2254e20
(gdb) bt
#0  CreateColormap (mid=32, pScreen=0x2253800, pVisual=0x2253dc0, 
ppcmap=0x7fff419bba90, alloc=0, client=0) at ../../dix/colormap.c:279
#1  0x005cf8b2 in miCreateDefColormap (pScreen=0x2253800)
at ../../mi/micmap.c:318
#2  0x0056d551 in fbCreateDefColormap (pScreen=0x2253800)
at ../../../fb/fbcmap_mi.c:91
#3  0x0042defc in vfbScreenInit (index=0, pScreen=0x2253800, argc=4, 
argv=0x7fff419bbd28) at ../../../hw/vfb/InitOutput.c:952
#4  0x005a1199 in AddScreen (pfnInit=0x42db2b vfbScreenInit, argc=4, 
argv=0x7fff419bbd28) at ../../dix/main.c:702
#5  0x0042e0e3 in InitOutput (screenInfo=0x88a780, argc=4, 
argv=0x7fff419bbd28) at ../../../hw/vfb/InitOutput.c:1018
#6  0x005a03b6 in main (argc=4, argv=0x7fff419bbd28, 
envp=0x7fff419bbd50) at ../../dix/main.c:315
(gdb) cont
Continuing.

Breakpoint 1, CreateColormap (mid=64, pScreen=0x2253800, pVisual=0x2253df8, 
ppcmap=0x2254238, alloc=0, client=0) at ../../dix/colormap.c:279
279 if (!pmap)
(gdb) print pmap
$2 = (ColormapPtr) 0x2265d90
(gdb) bt
#0  CreateColormap (mid=64, pScreen=0x2253800, pVisual=0x2253df8, 
ppcmap=0x2254238, alloc=0, client=0) at ../../dix/colormap.c:279
#1  0x004ee198 in PictureInitIndexedFormat (pScreen=0x2253800, 
format=0x2254210) at ../../render/picture.c:417
#2  0x004ee238 in PictureInitIndexedFormats (pScreen=0x2253800)
at ../../render/picture.c:439
#3  0x004ee28b in PictureFinishInit () at ../../render/picture.c:451
#4  0x004f133c in RenderExtensionInit () at ../../render/render.c:244
#5  0x0042e41c in InitExtensions (argc=4, argv=0x7fff419bbd28)
at ../../../mi/miinitext.c:457
#6  0x005a03e1 in main (argc=4, argv=0x7fff419bbd28, 
envp=0x7fff419bbd50) at ../../dix/main.c:319
(gdb) cont
Continuing.

Breakpoint 1, CreateColormap (mid=65, pScreen=0x2253800, pVisual=0x2253e30, 
ppcmap=0x2254280, alloc=0, client=0) at ../../dix/colormap.c:279
279 if (!pmap)
(gdb) print pmap
$3 = (ColormapPtr) 0x2271e50
(gdb) bt
#0  CreateColormap (mid=65, pScreen=0x2253800, pVisual=0x2253e30, 
ppcmap=0x2254280, alloc=0, client=0) at ../../dix/colormap.c:279
#1  0x004ee198 in PictureInitIndexedFormat (pScreen=0x2253800, 
format=0x2254258) at ../../render/picture.c:417
#2  0x004ee238 in PictureInitIndexedFormats (pScreen=0x2253800)
at ../../render/picture.c:439
#3  0x004ee28b in PictureFinishInit () at ../../render/picture.c:451
#4  0x004f133c in RenderExtensionInit () at ../../render/render.c:244
#5  0x0042e41c in InitExtensions (argc=4, argv=0x7fff419bbd28)
at ../../../mi/miinitext.c:457
#6  0x005a03e1 in main (argc=4, argv=0x7fff419bbd28, 
envp=0x7fff419bbd50) at ../../dix/main.c:319
(gdb) cont
Continuing.

Breakpoint 1, CreateColormap (mid=66, pScreen=0x2253800, pVisual=0x2253ed8, 
ppcmap=0x2254310, alloc=0, client=0) at ../../dix/colormap.c:279
279 if (!pmap)
(gdb) print pmap
$4 = (ColormapPtr) 0x227db00
(gdb) cont
Continuing.
[dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing 
from list!
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)
(EE) config/hal: NewInputDeviceRequest failed (2)

Breakpoint 2, FreeColormap (value=0x2271e50, mid=65)
at ../../dix/colormap.c:428
428 ColormapPtr pmap = (ColormapPtr)value;
(gdb) cont
Continuing.

Breakpoint 2, FreeColormap (value=0x2265d90, mid=64)
at ../../dix/colormap.c:428
428 ColormapPtr pmap = (ColormapPtr)value;
(gdb) cont
Continuing.


[Bug 330052] Re: Xvfb crashes with SIGSEGV in FreeColormap()

2009-09-15 Thread Adam Dickmeiss
The problem still exists and has been reported by others..
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529927

** Bug watch added: Debian Bug tracker #529927
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=529927

-- 
Xvfb crashes with SIGSEGV in FreeColormap()
https://bugs.launchpad.net/bugs/330052
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 360952] Re: Unstable system, EXT3 FS errors and boot failure

2009-07-29 Thread Adam Dickmeiss
*** This bug is a duplicate of bug 371191 ***
https://bugs.launchpad.net/bugs/371191

** This bug has been marked a duplicate of bug 371191
   Corrupted file system ext3 after Jaunty 64 upgrade

-- 
Unstable system, EXT3 FS errors and boot failure
https://bugs.launchpad.net/bugs/360952
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 371191] Re: Corrupted file system ext3 after Jaunty 64 upgrade

2009-07-29 Thread Adam Dickmeiss
Bug #360952 mentioned HPET (in fact I was the only one to comment on
it). In any case.. The problem persists even after messing with HPET. So
this did not solve it.

However, manually installing Linux kernel 2.6.29.3 from source DID solve
the problem (or at least the symptoms).

Seems like a serious bug to me!

-- 
Corrupted file system ext3 after Jaunty 64 upgrade
https://bugs.launchpad.net/bugs/371191
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 360952] Re: Unstable system, EXT3 FS errors and boot failure

2009-04-16 Thread Adam Dickmeiss
I am under the assumption that this problem is related to the HPET issues 
others are experiencing. With HPET (enabled
by default), the system becomes unstable over time.. Installed Jaunty again and 
tried two kernels: one with HPET enabled and one with HPET disabled. So far, 
the system, with HPET disabled has not suffered from these problems, while the 
other consistently makes the FS corrupt.

** Tags added: kernel

-- 
Unstable system, EXT3 FS errors and boot failure
https://bugs.launchpad.net/bugs/360952
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 360952] [NEW] Unstable system, EXT3 FS errors and boot failure

2009-04-14 Thread Adam Dickmeiss
Public bug reported:

System is Ubuntu Jaunty amd64. Hardware is Lenovo T61, type 6460-D6G.

System becomes unstable within minutes or a few hours of operation (uptime) and 
we see crashes in many
places.. Mostly in apt-get (SEGVs), due to that being used heavily the first 
few hours of operation. Eventually
the kernel will warn about EXT3-FS errors.. At next reboot Grub will be unable 
to list boot entries and show 'Error 2'.

It is assumed this is a software failure rather than hardward because
it happens on two different laptops (same T61 model) and 2) both laptops has 
been running for months with Ubuntu Intrepid (amd64/i386). Ubuntu Jaunty was 
installed twice on first T61 laptop and once on second T61 laptop. For the 
first laptop Ubuntu Jaunty was installed via upgrade and for the second time 
and on second laptop Ubuntu Jaunty was installed via Netboot.

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
Unstable system, EXT3 FS errors and boot failure
https://bugs.launchpad.net/bugs/360952
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 360952] Re: Unstable system, EXT3 FS errors and boot failure

2009-04-14 Thread Adam Dickmeiss
dmesg from second laptop.. during 3rd install. Interestingly this laptop was 
running for much longer time than
the other one before it the file system was forced read-only.

** Attachment added: dmesg
   http://launchpadlibrarian.net/25375608/dmesg.from.gyros

-- 
Unstable system, EXT3 FS errors and boot failure
https://bugs.launchpad.net/bugs/360952
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 360952] Re: Unstable system, EXT3 FS errors and boot failure

2009-04-14 Thread Adam Dickmeiss

** Attachment added: Hardware details
   http://launchpadlibrarian.net/25375526/lshw.txt

-- 
Unstable system, EXT3 FS errors and boot failure
https://bugs.launchpad.net/bugs/360952
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 360952] Re: Unstable system, EXT3 FS errors and boot failure

2009-04-14 Thread Adam Dickmeiss
dmesg from first laptop .. during second install.. The dmesg was copied away 
from the laptop via ssh because
the FS was forced into read-only mode. After rebooting Grub Error 2 was shown.

** Attachment added: dmesg
   http://launchpadlibrarian.net/25375598/dmesg.from.curry

-- 
Unstable system, EXT3 FS errors and boot failure
https://bugs.launchpad.net/bugs/360952
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 330052] Re: Xvfb crashes with SIGSEGV

2009-03-20 Thread Adam Dickmeiss
xserver configuration

** Attachment added: /etc/X11/xort.conf
   http://launchpadlibrarian.net/24163269/xorg.conf

-- 
Xvfb crashes with SIGSEGV
https://bugs.launchpad.net/bugs/330052
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 330052] Re: Xvfb crashes with SIGSEGV

2009-03-20 Thread Adam Dickmeiss
Program received signal SIGSEGV, Segmentation fault.
---Type return to continue, or q return to quit---
[Switching to Thread 0x7facb72e46f0 (LWP 7931)]
0x00507665 in FreeColormap ()
(gdb) bt full
#0  0x00507665 in FreeColormap ()
No symbol table info available.
#1  0x0052a1cb in FreeClientResources ()
No symbol table info available.
#2  0x0052a2b4 in FreeAllResources ()
No symbol table info available.
#3  0x00526adb in main ()
No symbol table info available.
(gdb) 


** Attachment added: lspci -vvnn
   http://launchpadlibrarian.net/24163255/lspci.out

-- 
Xvfb crashes with SIGSEGV
https://bugs.launchpad.net/bugs/330052
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 330052] [NEW] Xvfb crashes with SIGSEGV

2009-02-16 Thread Adam Dickmeiss
Public bug reported:

Binary package hint: xvfb

a...@durum:~$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.10
DISTRIB_CODENAME=intrepid
DISTRIB_DESCRIPTION=Ubuntu 8.10
a...@durum:~$ apt-cache policy xvfb
xvfb:
  Installed: 2:1.5.2-2ubuntu3
  Candidate: 2:1.5.2-2ubuntu3
  Version table:
 *** 2:1.5.2-2ubuntu3 0
500 http://dk.archive.ubuntu.com intrepid/main Packages
100 /var/lib/dpkg/status

a...@durum:~$ echo localhost hosts
a...@durum:~$ Xvfb :1 -auth hosts
Could not init font path element /usr/share/fonts/X11/cyrillic, removing from 
list!
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
Segmentation fault
a...@durum:~$ 

The crash happens when an X client is shut down.. For example, when
xeyes is shut down with Control-C.

a...@durum:~$ xeyes -display :1
^C


GDB session:

Starting program: /usr/bin/Xvfb :1 -auth hosts
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0x7f677e5d06f0 (LWP 32363)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Could not init font path element /usr/share/fonts/X11/cyrillic, removing from 
list!
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed
(EE) config/hal: NewInputDeviceRequest failed

Program received signal SIGSEGV, Segmentation fault.
---Type return to continue, or q return to quit---
[Switching to Thread 0x7f677e5d06f0 (LWP 32363)]
0x00507665 in FreeColormap ()
(gdb) bt
#0  0x00507665 in FreeColormap ()
#1  0x0052a1cb in FreeClientResources ()
#2  0x0052a2b4 in FreeAllResources ()
#3  0x00526adb in main ()
(gdb)

** Affects: xorg-server (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Xvfb crashes with SIGSEGV
https://bugs.launchpad.net/bugs/330052
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 330052] Re: Xvfb crashes with SIGSEGV

2009-02-16 Thread Adam Dickmeiss
If I specify a screen the crash does not occur.

 Xvfb :1 -auth hosts -screen 0 800x600x24

-- 
Xvfb crashes with SIGSEGV
https://bugs.launchpad.net/bugs/330052
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs