Bug 679141 - radeonhd [X1400] X segfaults
Summary: radeonhd [X1400] X segfaults
Status: RESOLVED DUPLICATE of bug 678264
Alias: None
Product: openSUSE 11.4
Classification: openSUSE
Component: X.Org (show other bugs)
Version: Final
Hardware: All SUSE Other
: P3 - Medium : Critical (vote)
Target Milestone: ---
Assignee: Stefan Dirsch
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-12 20:49 UTC by John Sheehy
Modified: 2011-03-13 00:26 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
startx error output (1.40 KB, text/plain)
2011-03-12 21:37 UTC, John Sheehy 		Details
Xorg.0.log (33.46 KB, text/plain)
2011-03-12 21:41 UTC, John Sheehy 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John Sheehy 2011-03-12 20:49:05 UTC 
User-Agent:       Mozilla/5.0 (Android; Linux armv7l; rv:2.0b12pre) Gecko/20110217 Firefox/4.0b12pre Fennec/4.0b5

radeon X1400 on Thinkpad T60. xorg server crashes after upgraded from 11.3 to 11.4. hard to provide details with no browser. the last line of the backtrace says:

2: (vdso) (__kernel_rt_sigreturn+0x0) [0xffffe40c]

tried disabling vdso. noeffect

tried disabling modeset. no effect.

tried radeonhd package out of Xorg: repository. same problem.

Reproducible: Always

Steps to Reproduce:
1.startx or init 5
2.
3.
Actual Results:  
just start x

Expected Results:  
xorg server crashes
Comment 1 John Sheehy 2011-03-12 21:37:29 UTC 
Created attachment 418983 [details]
startx error output
Comment 2 John Sheehy 2011-03-12 21:41:12 UTC 
Created attachment 418984 [details]
Xorg.0.log
Comment 3 Stefan Dirsch 2011-03-13 00:21:03 UTC 
Please do *not* touch the priority flag. Check the policy for reporting bugs. Thanks.
Comment 4 Stefan Dirsch 2011-03-13 00:26:22 UTC 
Duplicate.

  https://bugzilla.novell.com/show_bug.cgi?id=678264#c15

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