On 11/01/2011 09:12 PM, M. Edward (Ed) Borasky wrote:

On Tue, Nov 1, 2011 at 12:23 AM, Bernhard M. Wiedemann wrote:

...

Am 01.11.2011 06:07, schrieb M. Edward (Ed) Borasky:

...

I've got a bizarre GNOME 3 issue on my openSUSE 12.1 RC2 laptop. I usually am in the Chrome browser, but it fails in Chromium as well. At seemingly random times, I'll browse to a web site or activate some JavaScript widget and the screen will suddenly drop back to a login prompt! I think I can poke around and find a sequence of operations that will trigger this, but what do I have to do to get log files / crash dumps to figure out what's happening?

could be a Xorg crash. Check /var/log/Xorg.0.log

if there is a segfault, you can get a useful backtrace by following http://en.opensuse.org/openSUSE:Bugreport_X#How_to_test_the_latest_Xorg

It looks normal - no segfaults, anyhow. I'm guessing GNOME at this point. Are there log files from GNOME somewhere?

I did push ulimit up - with luck I'll get a core dump and can find a guilty / victim process.

...

Ciao Bernhard M. -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-testing+owner@opensuse.org

Perhaps the other way to backtrace that is opening the chrome then in a console session like tty2 use gdb attach Pid of chrome so the debugger is outside X Another place to look is inside ~/.xsession-errors -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-testing+owner@opensuse.org

I think I have it cornered - looks like an Xorg segfault! [ 1313.622] Backtrace: [ 1313.622] 0: /usr/bin/Xorg (xorg_backtrace+0x26) [0x462396] [ 1313.622] 1: /usr/bin/Xorg (0x400000+0x66919) [0x466919] [ 1313.622] 2: /lib64/libpthread.so.0 (0x7f248571e000+0xfd00) [0x7f248572dd00] [ 1313.622] 3: /usr/lib64/xorg/modules/extensions/librecord.so (0x7f2483525000+0x28d4) [0x7f24835278d4] [ 1313.622] 4: /usr/bin/Xorg (_CallCallbacks+0x34) [0x4379b4] [ 1313.622] 5: /usr/bin/Xorg (WriteToClient+0x21a) [0x4653ca] [ 1313.622] 6: /usr/lib64/xorg/modules/extensions/libdri2.so (ProcDRI2WaitMSCReply+0x52) [0x7f2482f0c062] [ 1313.622] 7: /usr/lib64/xorg/modules/extensions/libdri2.so (DRI2WaitMSCComplete+0x53) [0x7f2482f0a7a3] [ 1313.622] 8: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7f2482cb6000+0x266a4) [0x7f2482cdc6a4] [ 1313.622] 9: /usr/lib64/libdrm.so.2 (drmHandleEvent+0xa3) [0x7f2483115cd3] [ 1313.622] 10: /usr/bin/Xorg (WakeupHandler+0x6b) [0x4371bb] [ 1313.622] 11: /usr/bin/Xorg (WaitForSomething+0x1b6) [0x45fe36] [ 1313.622] 12: /usr/bin/Xorg (0x400000+0x33032) [0x433032] [ 1313.622] 13: /usr/bin/Xorg (0x400000+0x272ce) [0x4272ce] [ 1313.622] 14: /lib64/libc.so.6 (__libc_start_main+0xed) [0x7f248469523d] [ 1313.622] 15: /usr/bin/Xorg (0x400000+0x275bd) [0x4275bd] [ 1313.622] Segmentation fault at address 0x7f2480865010 [ 1313.622] Fatal server error: [ 1313.622] Caught signal 11 (Segmentation fault). Server aborting [ 1313.622] [ 1313.622] Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 1313.622] Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 1313.622] [ 1313.649] (II) Power Button: Close [ 1313.649] (II) UnloadModule: "evdev" [ 1313.649] (II) Unloading evdev [ 1313.670] (II) Video Bus: Close [ 1313.670] (II) UnloadModule: "evdev" [ 1313.670] (II) Unloading evdev [ 1313.687] (II) Sleep Button: Close [ 1313.687] (II) UnloadModule: "evdev" [ 1313.687] (II) Unloading evdev [ 1313.709] (II) ASUS USB2.0 WebCam: Close [ 1313.709] (II) UnloadModule: "evdev" [ 1313.709] (II) Unloading evdev [ 1313.734] (II) Logitech USB Receiver: Close [ 1313.734] (II) UnloadModule: "evdev" [ 1313.734] (II) Unloading evdev [ 1313.766] (II) Logitech USB Receiver: Close [ 1313.766] (II) UnloadModule: "evdev" [ 1313.766] (II) Unloading evdev [ 1313.798] (II) Asus WMI hotkeys: Close [ 1313.798] (II) UnloadModule: "evdev" [ 1313.798] (II) Unloading evdev [ 1313.830] (II) AT Translated Set 2 keyboard: Close [ 1313.830] (II) UnloadModule: "evdev" [ 1313.830] (II) Unloading evdev [ 1313.894] (II) UnloadModule: "synaptics" [ 1313.894] (II) Unloading synaptics [ 1313.894] (II) AIGLX: Suspending AIGLX clients for VT switch I'm guessing this is already in Bugzilla, so I'll go check. I'm wondering why AIGLX is in there, though - this laptop has an Intel GPU, not a Radeon / ATI. On Wed, Nov 9, 2011 at 12:41 PM, M. Edward (Ed) Borasky wrote:

I have lots more info now. I set /proc/sys/kernel/core_pattern and discovered that it's a Chrome crash. The Chrome executable is wrapped by a bash script that has this line at the bottom:

# We don't want bug-buddy intercepting our crashes. http://crbug.com/24120 export GNOME_DISABLE_CRASH_DIALOG=SET_BY_GOOGLE_CHROME

so I wonder if Chrome even managed to send a message up to Google on the way down - the crash is so fast that I'd be surprised. Google doesn't supply debug symbols for Chrome so I think I'll switch to Chromium where we have a real open source debugging process ;-)

On Wed, Nov 2, 2011 at 1:59 AM, Bruno Friedmann wrote:

...

On 11/01/2011 09:12 PM, M. Edward (Ed) Borasky wrote:

...

On Tue, Nov 1, 2011 at 12:23 AM, Bernhard M. Wiedemann wrote:

...

Am 01.11.2011 06:07, schrieb M. Edward (Ed) Borasky:

...

I've got a bizarre GNOME 3 issue on my openSUSE 12.1 RC2 laptop. I usually am in the Chrome browser, but it fails in Chromium as well. At seemingly random times, I'll browse to a web site or activate some JavaScript widget and the screen will suddenly drop back to a login prompt! I think I can poke around and find a sequence of operations that will trigger this, but what do I have to do to get log files / crash dumps to figure out what's happening?

could be a Xorg crash. Check /var/log/Xorg.0.log

if there is a segfault, you can get a useful backtrace by following http://en.opensuse.org/openSUSE:Bugreport_X#How_to_test_the_latest_Xorg

It looks normal - no segfaults, anyhow. I'm guessing GNOME at this point. Are there log files from GNOME somewhere?

I did push ulimit up - with luck I'll get a core dump and can find a guilty / victim process.

...

Ciao Bernhard M. -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-testing+owner@opensuse.org

Perhaps the other way to backtrace that is opening the chrome then in a console session like tty2 use gdb attach Pid of chrome

so the debugger is outside X

Another place to look is inside ~/.xsession-errors

--

Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch

openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-testing+owner@opensuse.org

-- http://twitter.com/znmeb http://borasky-research.net

"A mathematician is a device for turning coffee into theorems." -- Paul Erdős

-- http://twitter.com/znmeb http://borasky-research.net "A mathematician is a device for turning coffee into theorems." -- Paul Erdős -- To unsubscribe, e-mail: opensuse-testing+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-testing+owner@opensuse.org