Oh, sorry Keir,
I stumped in an old Bug.
I have rtc support in that kernel, and didn't remove /sbin/hwclock, so hwclock 
consumed all the time.
That was the issue.
Now the system performs normal.
What can I do to debug the problem with the irq? What does the 
Sorry,
Johnny
Am Montag, 5. Juni 2006 19:21 schrieb Hans-Christian Armingeon:
> Am Montag, 5. Juni 2006 19:08 schrieben Sie:
> > 
> > On 5 Jun 2006, at 17:58, Hans-Christian Armingeon wrote:
> > 
> > > my system (dom0) is very slow, after the reboot with noirqdebug.
> > >
> > > The domU is very slow, too, and consumes a lot of cpu time.
> > >
> > > What can I do?
> > 
> > Slower than booting without 'noirqdebug'?
>
> Yes. The domain with the device, that owns irq17 consumes very much cpu time, 
> and makes a dual Opteron slow.
>
> > 
> > If you boot without noirqdebug, how long does it take before domain0 
> > complains about one of its irqs? Does it happen only after you have 
> > started your driver domU?
>
> Well, soetimes it takes a few hours, up to a few days.
>
> Johnny
>
> > 
> > -- Keir
> > 
> > 
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users