Bug 532460

Summary:	Booting installer with drm.debug=1 results in loader SIGSEGV
Product:	[Fedora] Fedora	Reporter:	James Laska <jlaska>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	anaconda-maint-list, jturner, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-11-02 14:12:16 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description James Laska 2009-11-02 13:52:34 UTC

Description of problem:

Either on bare metal or in virt ... booting the installer with drm.debug=1 results in a SIGSEGV

Version-Release number of selected component (if applicable):

 * anaconda-12.41

How reproducible:

 * Seems like everytime

Steps to Reproduce:
1. Add "drm.debug=1" to the boot options
  
Actual results:

Greetings.
anaconda installer init version 12.41 starting
mounting /proc filesystem... done
creating /dev filesystem... done
starting udev...done
mounting /dev/pts (unix98 pty) filesystem... done
mounting /sys filesystem... done
anaconda installer init version 12.41 using a serial console
trying to remount root filesystem read write... done
mounting /tmp as tmpfs... done
running install...
running /sbin/loader
loader received SIGSEGV!  Backtrace:
/sbin/loader[0x804e041]
[0xd1f400]
/sbin/loader[0x80531b1]
/sbin/loader[0x804f1c6]
/lib/libc.so.6(__libc_start_main+0xe6)[0x955b36]
/sbin/loader[0x804bee1]
install exited abnormally [1/1] 
you may safely reboot your system


Expected results:

No sigsegv

Additional info:

 * I thought loader sigsegv's included the debuginfo information in the backtrace?  Did that change?

Comment 1 Chris Lumens 2009-11-02 14:12:16 UTC


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