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

Re: [Xen-devel] Kernel Bug asterisk


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Hans-Christian Armingeon <johnny@xxxxxxxxxx>
  • Date: Wed, 10 May 2006 15:49:27 +0200
  • Delivery-date: Thu, 11 May 2006 02:23:35 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Am Mittwoch, 10. Mai 2006 14:20 schrieb Keir Fraser:
> 
> On 9 May 2006, at 16:30, Hans-Christian Armingeon wrote:
> 
> >> Only one domain can own the RTC. We had problems with some user-space
> >> programs hanging if the RTC driver was loaded but unable to bind to 
> >> IRQ
> >> 8 or access the RTC I/O ports.
> >
> > I am having the problem, that hwclock hangs, if rtc is compiled into 
> > the kernel.
> >
> > Is there a easy fix possible, to avoid systems hanging after a 
> > dist-upgrade?
> 
> Not allowing RTC to bind to IRQ8 is our current workaround. Are you 
> seeing the hang in domain0 or in other domains?

I only see the hang in domU. Dom0 has physical access to the rtc.
I had the rtc driver built into the kernel, not as a module.

It was a bit annoying, especially on ubuntu dapper domains, because after a 
dist-upgrade, /sbin/hwclock usually got restored, and after a reboot, the 
domain was hanging.

johnny

> 
>   -- Keir
> 

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


 


Rackspace

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