[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-bugs] [Bug 347] Unable to bring up x86_64 SMP DomUs



http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=347





------- Additional Comments From ryanh@xxxxxxxxxx  2005-10-29 17:04 -------
WARK: CPU0 calling flush_scheduled_work()
WARK: CPU0 in flush_workqueue()
WARK: cpu_workqueue size-> 128 0x80
WARK: CPU0 trying for cpu_hotplug lock()
WARK: CPU0 got it()
WARK: CPU0 wq for CPU0 should be at 0xffff8800003f5800+0x0
WARK: CPU0 calling flush_cpu_wkq(0xffff8800003f5800)
WARK: CPU0 flush_cpu_workqueue() IN
cwq at 0xffff8800003f5800, cwq->thread=0xffff8800015554e0, lock->1
WARK: CPU0 trying for cwq->lock
cwq at 0xffff8800003f5800, cwq->thread=0xffff8800015554e0, lock->1
WARK: CPU0 got it
WARK: CPU0 flush_cpu_workqueue() OUT
cwq at 0xffff8800003f5800, cwq->thread=0xffff8800015554e0, lock->1
WARK: CPU0 wq for CPU1 should be at 0xffff8800003f5800+0x80
WARK: CPU0 calling flush_cpu_wkq(0xffff8800003f5880)
WARK: CPU0 flush_cpu_workqueue() IN
cwq at 0xffff8800003f5880, cwq->thread=0x0000000000000000, lock->0
WARK: CPU0 trying for cwq->lock
cwq at 0xffff8800003f5880, cwq->thread=0x0000000000000000, lock->0

still digging, but I'm getting stuck blocking on trying for a spinlock thats not
been initialized.  The workqueue at 0xffff8800003f5800 has been initialized, the
thread value is set and the lock init to 1 (unlocked on x86).  But the second
cwq for cpu1 is not initalized, thread is still NULL, and the lock value is 0
(locked).  

-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.