WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

[Xen-ia64-devel] RE: No scheduling after domU launch

To: "Haavard Bjerke" <havard.bjerke@xxxxxxx>
Subject: [Xen-ia64-devel] RE: No scheduling after domU launch
From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Date: Wed, 18 May 2005 08:32:20 -0700
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 18 May 2005 15:31:41 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: DIscussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcVbvZqDmUPL5G2ETIeqUBcEGX+/kgAADtkQ
Thread-topic: No scheduling after domU launch
Given the previous discussion around this (last month?), I suspect
that there is a bug somewhere that is overwriting some random
memory related to the scheduler.  As Mark W pointed out, your
previous workaround fixed a problem that should never happen.
And I don't think any recent changes in xeno-unstable-ia64 have
had anything to do with the scheduler, so I suspect the
"random memory" moved to a different random spot which
is causing your current problem.

This is just a theory... you are probably as familiar with this
part of the code as anybody on this list right now.  Try
adding some more printf's to see if any clues arise.
I'll try to take a look but probably not today, so reply
to this thread if you learn anything new or interesting.

Dan

> -----Original Message-----
> From: Haavard Bjerke [mailto:havard.bjerke@xxxxxxx] 
> Sent: Wednesday, May 18, 2005 9:23 AM
> To: Magenheimer, Dan (HP Labs Fort Collins)
> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: No scheduling after domU launch
> 
> Since pulling the latest xeno-unstable-ia64 a few days ago, 
> scheduling seems to stop immediately after launching domU, 
> that is, domU continues to load, while dom0 stops because the 
> scheduler is never entered again. This looks like the same 
> problem as before, with dom0 freezing after domU launch; 
> only, now it seems to freeze earlier. Before, I was able to 
> run a hypercall right after launch. This is kind of critical, 
> since a user-space app running in dom0 is supposed to 
> establish a ctrl-channel right after launch, while domU is booting.
> 
> So I'm quite stuck and wondering why it stops scheduling, and 
> I could use some input. So far I've found out that 
> __enter_sceduler() is never called after domU launch, while 
> the routine that's supposed to call that routine, 
> ac_timer_softirq_action(), continues to be called. I think 
> the __enter_sceduler() routine should be in a heap, but I 
> don't understand why it would suddenly be removed from the heap..
> 
> Thanks,
> Håvard
> 

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

<Prev in Thread] Current Thread [Next in Thread>