On Tue, Dec 13, 2005 at 03:18:10PM +0800, Karamazov Brothers wrote:
> Program received signal SIGSEGV, Segmentation fault.
> _raw_spin_lock (lock=0x602bfb70) at include/asm/thread_info.h:47
> 47 {
> (gdb) bt
> #0 _raw_spin_lock (lock=0x602bfb70) at include/asm/thread_info.h:47
> #1 0x000000006020de18 in _spin_lock_irqsave (lock=0x602bfb70)
> at kernel/spinlock.c:78
Do you have CONFIG_SMP enabled? I can't see any other reason you'd be
getting spinlocks involved.
Jeff
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
User-mode-linux-user mailing list
User-mode-linux-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
