Bug 784848

Summary:	freeze when marking and dragging text in firefox and konqueror
Product:	[openSUSE] openSUSE 12.2	Reporter:	Forgotten User pZNWf0nnEb <forgotten_pZNWf0nnEb>
Component:	X.Org	Assignee:	E-mail List <xorg-maintainer-bugs>
Status:	VERIFIED INVALID	QA Contact:	E-mail List <xorg-maintainer-bugs>
Severity:	Critical
Priority:	P5 - None	CC:	freespacer
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 12.2
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	part of /var/log/messages with kernel 3.4.11-2.16-desktop

Description Forgotten User pZNWf0nnEb 2012-10-12 09:26:53 UTC

User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0.1

System: openSUSE 12.2 x86_64, up to date, kernel: 3.4.6-2.10-desktop
Firefox: 15.0.1-2.11.1
Konqueror: 4.8.5-2.4.1

Reproducible: Always

Steps to Reproduce:
1.Open Firefox or Konqueror.
2.Visit any website and mark a passage of text
3.Now drag this text (hold left mouse button and move the mouse)
4.system is freezing (see below for details)
Actual Results:
As a result the display freezes within <1s after moving the text. After seeing the freezed picture on my monitor for around 5 seconds it looses a signal from the graphics card.
The system doesn't respond to Ctrl+Alt+F1, Ctrl+Esc or Ctrl+Alt+Entf. When I use magic sysrq, only reboot (Alt+print+b) seems to have any effect (I cannot see anything on the display, so it's hard to judge).

This bug only occurs since I have upgraded from openSUSE 12.1 to 12.2 several days ago (I kept the 12.1 up to date every week so Firefox was the same version 15.0.1, I also had KDE 4.8.5). I'm sure that it didn't happen with 12.1 because I drag text in the browser unconciously several times a day.

What I also changed: With 12.1 I used the proprietary AMD driver 12.6 legacy for my Raedon HD4850, with 12.2 the FOSS driver.

This bug isn't present when dragging text in Libreoffice or Dolphin (dragging files). Maybe that's because with these programs one cannot see the dragged text moving with the mouse but only a icon representing the text?

I weren't sure what component would be the reason, so I chose "other".

Please be kind to give me hints on how the create useful crash logs for you guys.

Comment 1 Forgotten User pZNWf0nnEb 2012-10-12 09:41:15 UTC

Tested it again: This bug does NOT occur when using the AMD legacy driver 12.6 only the radeonhd driver from the openSUSE 12.1 package (xorg-x11-driver-video-radeonhd 1.3.0_20100512_80ba041-11.1.2-x86_64), so this seems to be a driver issue (changed component to "kernel").

Comment 2 Forgotten User pZNWf0nnEb 2012-10-17 16:55:02 UTC

Created attachment 509892 [details]
part of /var/log/messages with kernel 3.4.11-2.16-desktop

Updated to kernel 3.4.11-2.16-desktop and have the same freeze / unresponding system. See the attached file for a part of /var/log/messages after the freeze.

I also tested kernel 3.6.2-desktop with better results: I can move the mouse pointer (and see it moving) but everything else seems to be frozen. But other than with kernel 3.4.11, I now can switch to text console and SqsRq key is working, too. The output in /var/log/messages changed:

Oct 17 18:25:01 dennisgrunert kernel: [  113.950546] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
Oct 17 18:25:01 dennisgrunert kernel: [  113.950557] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000f8a last fence id 0x0000000000000f89)

and then the next two lines are in the log several times a second until I rebooted the system:

Oct 17 18:25:01 dennisgrunert kernel: [  113.953223] radeon 0000:01:00.0: couldn't schedule ib
Oct 17 18:25:01 dennisgrunert kernel: [  113.953229] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !

I hope this error messages from both kernel versions will help. For 3.4.11 this bug is still critical and unfortunately no one told me how to produce useful error messages / back traces / test different scenarios with this bug.

Comment 3 Sebastian Siebert 2012-10-29 09:08:42 UTC

@Stefan:
Can you take a look to this report, please?

Thank you.

Greetings,
Sebastian

Comment 4 Forgotten User pZNWf0nnEb 2013-05-20 21:42:33 UTC

This bug disappeared for me with an upgrade to openSUSE 12.3. Since nobody was interested in it anyway, I closed it as invalid.