Bug 286792 - Konqueror crashed while idle, display goes black for a few seconds every 30 minutes.
Summary: Konqueror crashed while idle, display goes black for a few seconds every 30 m...
Status: RESOLVED DUPLICATE of bug 284830
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 4.6.5
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-16 18:20 UTC by Al Dunstan
Modified: 2011-11-17 23:35 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Al Dunstan 2011-11-16 18:20:12 UTC
Application: konqueror (4.6.5 (4.6.5))
KDE Platform Version: 4.6.5 (4.6.5)
Qt Version: 4.7.4
Operating System: Linux 2.6.35.14-103.fc14.i686 i686
Distribution: "Fedora release 15 (Lovelock)"

-- Information about the crash:
- What I was doing when the application crashed:
Staring at the screen.  A Konqueror window was up, but behind the window I was looking at (kterminal).  Suddenly Konqueror went away.

- Unusual behavior I noticed:
- While upgrading from FC14 to FC15 (earlier this week) the upgrade failed when it got to python-urwid, claiming the package was corrupt & it couldn't continue.  I rebooted and it made it farther along, until it ran into python-urwid again.  After the 3rd reboot it could no longer proceed.  I was able to get into a command line and do 'yum update'.  After some thrashing around I got rid of most of the duplicate packages, although I still can't update upstart.

- My display goes black every so often now, with this message in /var/log/messages:
Nov 16 13:15:45 valdez kernel: [14516.140064] radeon 0000:04:0d.0: GPU lockup CP stall for more than 1020msec
Nov 16 13:15:45 valdez kernel: [14516.450052] Failed to wait GUI idle while programming pipes. Bad things might happen.
Nov 16 13:15:45 valdez kernel: [14516.451087] radeon 0000:04:0d.0: (r100_asic_reset:2088) RBBM_STATUS=0x80010140
Nov 16 13:15:45 valdez kernel: [14516.956267] radeon 0000:04:0d.0: (r100_asic_reset:2109) RBBM_STATUS=0x80010140
Nov 16 13:15:45 valdez kernel: [14517.457375] radeon 0000:04:0d.0: (r100_asic_reset:2117) RBBM_STATUS=0x00000140
Nov 16 13:15:46 valdez kernel: [14517.457429] radeon 0000:04:0d.0: GPU reset succeed
Nov 16 13:15:46 valdez kernel: [14517.457433] radeon 0000:04:0d.0: GPU reset succeed
Nov 16 13:15:46 valdez kernel: [14517.815342] [drm] radeon: ring at 0x00000000D0000000
Nov 16 13:15:46 valdez kernel: [14517.815563] [drm] ring test succeeded in 1 usecs
Nov 16 13:15:46 valdez kernel: [14517.815583] [drm] ib test succeeded in 3 usecs

The 1st message in the log file has appeared 8 times in the last 3 hours; it looks like it's at 15 and 45 minutes after the hour.

- I see horizontal 'streaks' on the display.  If I minimize & restore a window they go away from that window (for a while), but they persist on the wallpaper (until the wallpaper changes).

The crash can be reproduced some of the time.

-- Backtrace:
Application: Konqueror (konqueror), signal: Aborted
[Current thread is 1 (Thread 0xb78a0780 (LWP 3119))]

Thread 2 (Thread 0xb33ffb70 (LWP 5825)):
[KCrash Handler]
#7  0x00a0f416 in __kernel_vsyscall ()
#8  0x01ed526f in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#9  0x01ed6ba5 in __GI_abort () at abort.c:93
#10 0x071ab894 in g_logv (log_domain=0x7211406 "GLib", log_level=<optimized out>, format=0x7216f64 "Cannot create pipe main loop wake-up: %s\n", args1=0xb33ff1ac "\036&\377\001(\223'\a\240\213") at gmessages.c:557
#11 0x071ab8d4 in g_log (log_domain=0x7211406 "GLib", log_level=G_LOG_LEVEL_ERROR, format=0x7216f64 "Cannot create pipe main loop wake-up: %s\n") at gmessages.c:577
#12 0x0719efdb in g_main_context_init_pipe (context=0xb3008ba0) at gmain.c:530
#13 0x0719f4e7 in g_main_context_init_pipe (context=0xb3008ba0) at gmain.c:520
#14 g_main_context_new () at gmain.c:626
#15 0x05466900 in QEventDispatcherGlibPrivate::QEventDispatcherGlibPrivate (this=0xb3008ac0, context=0x0) at kernel/qeventdispatcher_glib.cpp:310
#16 0x05466a8d in QEventDispatcherGlib::QEventDispatcherGlib (this=0xb3004cb0, parent=0x0) at kernel/qeventdispatcher_glib.cpp:357
#17 0x0533bbe4 in QThreadPrivate::createEventDispatcher (data=0x9315c38) at thread/qthread_unix.cpp:272
#18 0x0533c81b in QThreadPrivate::start (arg=0x92b14c0) at thread/qthread_unix.cpp:324
#19 0x001a3a2e in start_thread (arg=0xb33ffb70) at pthread_create.c:305
#20 0x01f8134e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133

Thread 1 (Thread 0xb78a0780 (LWP 3119)):
#0  0x00a0f416 in __kernel_vsyscall ()
#1  0x001a714c in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:172
#2  0x0533cd58 in wait (time=4294967295, this=0x9316218) at thread/qwaitcondition_unix.cpp:88
#3  QWaitCondition::wait (this=0x9307fa4, mutex=0x9307f90, time=4294967295) at thread/qwaitcondition_unix.cpp:160
#4  0x05330093 in QThreadPoolPrivate::waitForDone (this=0x9307f40) at concurrent/qthreadpool.cpp:295
#5  0x053314f1 in QThreadPool::~QThreadPool (this=0x937b868, __in_chrg=<optimized out>) at concurrent/qthreadpool.cpp:428
#6  0x05331553 in QThreadPool::~QThreadPool (this=0x937b868, __in_chrg=<optimized out>) at concurrent/qthreadpool.cpp:430
#7  0x05331589 in QGlobalStaticDeleter<QThreadPool>::~QGlobalStaticDeleter (this=0x556e7c0, __in_chrg=<optimized out>) at ../../src/corelib/global/qglobal.h:1823
#8  0x01ed88d1 in __run_exit_handlers (status=1, listp=0x202f324, run_list_atexit=true) at exit.c:78
#9  0x01ed895d in __GI_exit (status=1) at exit.c:100
#10 0x015bec99 in qt_xio_errhandler () at kernel/qapplication_x11.cpp:772
#11 0x011d260a in KApplication::xioErrhandler (this=0xbfdff9e4, dpy=0x8964ac8) at /usr/src/debug/kdelibs-4.6.5/kdeui/kernel/kapplication.cpp:419
#12 0x011d2645 in kde_xio_errhandler (dpy=0x8964ac8) at /usr/src/debug/kdelibs-4.6.5/kdeui/kernel/kapplication.cpp:126
#13 0x00c74075 in _XIOError (dpy=0x8964ac8) at XlibInt.c:1618
#14 0x00c717cf in _XEventsQueued (dpy=0x8964ac8, mode=2) at xcb_io.c:307
#15 0x00c620b8 in XEventsQueued (dpy=0x8964ac8, mode=2) at Pending.c:43
#16 0x015fa69e in x11EventSourcePrepare (s=0x8952f40, timeout=0xbfdff6dc) at kernel/qguieventdispatcher_glib.cpp:77
#17 0x071a1b5c in g_main_context_prepare (context=0x8952270, priority=0xbfdff738) at gmain.c:2762
#18 0x071a29d8 in g_main_context_iterate (context=0x8952270, block=1, dispatch=1, self=0x894f5f8) at gmain.c:3072
#19 0x071a306f in g_main_context_iteration (context=0x8952270, may_block=1) at gmain.c:3155
#20 0x05466e68 in QEventDispatcherGlib::processEvents (this=0x8933b00, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#21 0x015fa7db in QGuiEventDispatcherGlib::processEvents (this=0x8933b00, flags=...) at kernel/qguieventdispatcher_glib.cpp:207
#22 0x05437b6e in QEventLoop::processEvents (this=0xbfdff8b4, flags=...) at kernel/qeventloop.cpp:149
#23 0x05437dc1 in QEventLoop::exec (this=0xbfdff8b4, flags=...) at kernel/qeventloop.cpp:201
#24 0x0543c51b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#25 0x01543ae5 in QApplication::exec () at kernel/qapplication.cpp:3755
#26 0x00ba0738 in kdemain (argc=3, argv=0xbfdffd04) at /usr/src/debug/kdebase-4.6.5/konqueror/src/konqmain.cpp:219
#27 0x0804869c in main (argc=3, argv=0xbfdffd04) at /usr/src/debug/kdebase-4.6.5/i686-redhat-linux-gnu/konqueror/src/konqueror_dummy.cpp:3

Possible duplicates by query: bug 286604, bug 286570, bug 281996, bug 281995, bug 281204.

Reported using DrKonqi
Comment 1 Christoph Feck 2011-11-17 23:35:54 UTC
Please report the video issues to ATI/Radeon driver developers.

*** This bug has been marked as a duplicate of bug 284830 ***