All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@hp.com>
To: Akio Takebe <takebe_akio@jp.fujitsu.com>
Cc: "Magenheimer,
	Dan (HP Labs Fort Collins)" <dan.magenheimer@hp.com>,
	"Tian, Kevin" <kevin.tian@intel.com>,
	"Xu, Anthony" <anthony.xu@intel.com>,
	xen-devel <xen-devel@lists.xensource.com>,
	xen-ia64-devel@lists.xensource.com
Subject: Re: [Xen-ia64-devel] RE: Help? Red Hat fails, Suse/Debian both work fine
Date: Thu, 02 Mar 2006 10:24:00 -0700	[thread overview]
Message-ID: <1141320240.27443.30.camel@localhost> (raw)
In-Reply-To: <2CC63E0C90481Ctakebe_akio@jp.fujitsu.com>


   A little bit of data in case it sparks some debug ideas.  Enabling
tracing in xenstored shows that the difference between the working and
non-working case are exhibited pretty quickly.  There's definitely
communication occurring through the mmap'd kmem page, but it's missing
some important chunks.  For instance, here's the first few messages
logged in the working case:

CREATE connection 0x6000000000022678
IN  0x6000000000022678 07:15:03 DIRECTORY (device )
OUT 0x6000000000022678 07:15:03 ERROR (ENOENT )
IN  0x6000000000022678 07:15:03 DIRECTORY (backend )
OUT 0x6000000000022678 07:15:03 ERROR (ENOENT )
IN  0x6000000000022678 07:15:03 WATCH (device A000000100D20520 )
CREATE watch 0x60000000000229a8
OUT 0x6000000000022678 07:15:03 WATCH (OK )
IN  0x6000000000022678 07:15:03 WATCH (backend A000000100D20500 )
CREATE watch 0x60000000000228c8
OUT 0x6000000000022678 07:15:03 WATCH_EVENT (device A000000100D20520 )
OUT 0x6000000000022678 07:15:03 WATCH (OK )
OUT 0x6000000000022678 07:15:03 WATCH_EVENT (backend A000000100D20500 )
CREATE connection 0x6000000000022748
IN  0x6000000000022748 07:15:03 WATCH (@introduceDomain domlist )
CREATE watch 0x60000000000234c8
OUT 0x6000000000022748 07:15:03 WATCH (OK )

In the failing case, I see:

CREATE connection 0x6000000000026388
IN  0x6000000000026388 07:07:47 DIRECTORY (device )
OUT 0x6000000000026388 07:07:47 ERROR (ENOENT )
CREATE connection 0x60000000000265d8
IN  0x60000000000265d8 07:07:47 WATCH (@introduceDomain domlist )
CREATE watch 0x6000000000026d78
OUT 0x60000000000265d8 07:07:47 WATCH (OK )

Note that only the lines dealing with A000000100D20520 are missing.

The next absent chunk comes after about 300 lines of identical trace
between the working and failing case.  This block is missing when it
fails:

OUT 0x6000000000022678 07:15:14 WATCH_EVENT (backend/vbd/1/769 A000000100D20500 )
IN  0x6000000000022678 07:15:14 DIRECTORY (backend/vbd/1/769 )
OUT 0x6000000000022678 07:15:14 WATCH_EVENT (backend/vbd/1/769/domain A000000100D20500 )
OUT 0x6000000000022678 07:15:14 WATCH_EVENT (backend/vbd/1/769/frontend A000000100D20500 )
OUT 0x6000000000022678 07:15:14 WATCH_EVENT (backend/vbd/1/769/dev A000000100D20500 )
OUT 0x6000000000022678 07:15:14 WATCH_EVENT (backend/vbd/1/769/state A000000100D20500 )
OUT 0x6000000000022678 07:15:14 WATCH_EVENT (backend/vbd/1/769/params A000000100D20500 )
OUT 0x6000000000022678 07:15:14 WATCH_EVENT (backend/vbd/1/769/mode A000000100D20500 )
OUT 0x6000000000022678 07:15:14 WATCH_EVENT (backend/vbd/1/769/frontend-id A000000100D20500 )
OUT 0x6000000000022678 07:15:14 WATCH_EVENT (backend/vbd/1/769/type A000000100D20500 )
OUT 0x6000000000022678 07:15:14 DIRECTORY (domain frontend dev state params mode frontend-id type )
IN  0x6000000000022678 07:15:14 READ (backend/vbd/1/769/state )
OUT 0x6000000000022678 07:15:14 READ (1)
IN  0x6000000000022678 07:15:14 READ (backend/vbd/1/769/frontend-id )
OUT 0x6000000000022678 07:15:14 READ (1)
IN  0x6000000000022678 07:15:14 READ (backend/vbd/1/769/frontend )
OUT 0x6000000000022678 07:15:14 READ (/local/domain/1/device/vbd/769)
IN  0x6000000000022678 07:15:14 DIRECTORY (/local/domain/1/device/vbd/769 )
OUT 0x6000000000022678 07:15:14 DIRECTORY (virtual-device backend-id state backend )
IN  0x6000000000022678 07:15:14 READ (backend/vbd/1/769/frontend-id )
OUT 0x6000000000022678 07:15:14 READ (1)
IN  0x6000000000022678 07:15:14 READ (backend/vbd/1/769/frontend )
OUT 0x6000000000022678 07:15:14 READ (/local/domain/1/device/vbd/769)
IN  0x6000000000022678 07:15:14 DIRECTORY (/local/domain/1/device/vbd/769 )
OUT 0x6000000000022678 07:15:14 DIRECTORY (virtual-device backend-id state backend )
IN  0x6000000000022678 07:15:14 WATCH (backend/vbd/1/769/physical-device E000000008E31C90 )
CREATE watch 0x600000000000cad8
OUT 0x6000000000022678 07:15:14 WATCH (OK )
IN  0x6000000000022678 07:15:14 READ (backend/vbd/1/769/state )
OUT 0x6000000000022678 07:15:14 WATCH_EVENT (backend/vbd/1/769/physical-device E000000008E31C90 )
OUT 0x6000000000022678 07:15:14 READ (1)
IN  0x6000000000022678 07:15:14 WRITE (backend/vbd/1/769/state 2)
OUT 0x6000000000022678 07:15:14 WATCH_EVENT (backend/vbd/1/769/state A000000100D20500 )
OUT 0x6000000000022678 07:15:14 WRITE (OK )
IN  0x6000000000022678 07:15:14 WATCH (/local/domain/1/device/vbd/769/state E00000001D3AB1A0 )
CREATE watch 0x600000000000cda8
OUT 0x6000000000022678 07:15:14 WATCH (OK )
IN  0x6000000000022678 07:15:14 DIRECTORY (backend/vbd/1/769/domain )
OUT 0x6000000000022678 07:15:14 WATCH_EVENT (/local/domain/1/device/vbd/769/state E00000001D3AB1A0 )
OUT 0x6000000000022678 07:15:14 DIRECTORY ()
IN  0x6000000000022678 07:15:14 DIRECTORY (backend/vbd/1/769/frontend )
OUT 0x6000000000022678 07:15:14 DIRECTORY ()
IN  0x6000000000022678 07:15:14 DIRECTORY (backend/vbd/1/769/dev )
OUT 0x6000000000022678 07:15:14 DIRECTORY ()
IN  0x6000000000022678 07:15:14 DIRECTORY (backend/vbd/1/769/state )
OUT 0x6000000000022678 07:15:14 DIRECTORY ()
IN  0x6000000000022678 07:15:14 DIRECTORY (backend/vbd/1/769/params )
OUT 0x6000000000022678 07:15:14 DIRECTORY ()
IN  0x6000000000022678 07:15:14 DIRECTORY (backend/vbd/1/769/mode )
OUT 0x6000000000022678 07:15:14 DIRECTORY ()
IN  0x6000000000022678 07:15:14 DIRECTORY (backend/vbd/1/769/frontend-id )
OUT 0x6000000000022678 07:15:14 DIRECTORY ()
IN  0x6000000000022678 07:15:14 DIRECTORY (backend/vbd/1/769/type )
OUT 0x6000000000022678 07:15:14 DIRECTORY ()
IN  0x6000000000022678 07:15:14 READ (backend/vbd/1/769/physical-device )
OUT 0x6000000000022678 07:15:14 ERROR (ENOENT )
IN  0x6000000000022678 07:15:14 DIRECTORY (backend/vbd/1/769/state )
OUT 0x6000000000022678 07:15:14 DIRECTORY ()
IN  0x6000000000022678 07:15:14 READ (/local/domain/1/device/vbd/769/state )
OUT 0x6000000000022678 07:15:14 READ (1)

If I mmap and dump the kva page in a test program, it looks like it's
working correctly.  I can see and decode the send and receive rings and
see the index values.  Thanks,

	Alex

-- 
Alex Williamson                             HP Linux & Open Source Lab

  reply	other threads:[~2006-03-02 17:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-02  5:43 Help? Red Hat fails, Suse/Debian both work fine Tian, Kevin
2006-03-02  6:04 ` [Xen-ia64-devel] " Yoshi.Oguchi
2006-03-02  8:26 ` [Xen-devel] " Keir Fraser
2006-03-02 15:18 ` Akio Takebe
2006-03-02 17:24   ` Alex Williamson [this message]
2006-03-02 18:41     ` [Xen-ia64-devel] " Ewan Mellor
2006-03-02 18:56       ` Alex Williamson
2006-03-02 20:27         ` RE: [Xen-devel] " Keir Fraser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1141320240.27443.30.camel@localhost \
    --to=alex.williamson@hp.com \
    --cc=anthony.xu@intel.com \
    --cc=dan.magenheimer@hp.com \
    --cc=kevin.tian@intel.com \
    --cc=takebe_akio@jp.fujitsu.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-ia64-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.