From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gerd Knorr <kraxel@suse.de>
Subject: Re: network (irq?) problems in unstable
Date: Tue, 31 May 2005 12:18:51 +0200
Message-ID: <20050531101851.GB22211@bytesex>
References: <20050530125247.GA12140@bytesex>
	<61adb21cca3abe8c474f66040037da6a@cl.cam.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <61adb21cca3abe8c474f66040037da6a@cl.cam.ac.uk>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

> looking at boot-time output of Xen vs. native Linux. Also, particularly 
> if you have a null modem cable attached, add tracing on a debug key to 
> see what Xen thinks the status of each IRQ line is (disabled, 
> in_progress, etc.). Managing IRQ lines via legacy PIC is pretty 
> straightforward so this can't really be that hard a bug to fix I think 
> (hope). :-)

(XEN) IRQ states:
(XEN)     0:
(XEN)     1: guest
(XEN)     2:
(XEN)     4: inprogress
(XEN)     5: guest
(XEN)     9: guest
(XEN)    11: guest

No change before and after network freeze (#11 is the nic).
Hmm.

  Gerd

-- 
-mm seems unusually stable at present.
	-- akpm about 2.6.12-rc3-mm3