What am I doing wrong?

What am I doing wrong?

[Paul Gardiner]

I create the initial repository with

     git-clone /<full-path>/<name>.git/ <folder>

That works fine, but then I can't fetch. git-fetch gives the error
"fatal: 'origin': unable to chdir or not a git archive"
"fatal: The remote end hung up unexpectedly"

P.

Re: What am I doing wrong?

[Michael J Gruber]

Paul Gardiner venit, vidit, dixit 16.05.2008 13:25:
> I create the initial repository with
> 
>      git-clone /<full-path>/<name>.git/ <folder>
> 
> That works fine, but then I can't fetch. git-fetch gives the error
> "fatal: 'origin': unable to chdir or not a git archive"
> "fatal: The remote end hung up unexpectedly"
> 
> P.

Are you trying to clone a bare repository?
Or is your repo maybe at /<full-path>/<name> with a .git subdir?

Michael

Re: What am I doing wrong?

[Paul Gardiner]

Michael J Gruber wrote:
> Paul Gardiner venit, vidit, dixit 16.05.2008 13:25:
>> I create the initial repository with
>>
>>      git-clone /<full-path>/<name>.git/ <folder>
>>
>> That works fine, but then I can't fetch. git-fetch gives the error
>> "fatal: 'origin': unable to chdir or not a git archive"
>> "fatal: The remote end hung up unexpectedly"
>>
>> P.
> 
> Are you trying to clone a bare repository?
> Or is your repo maybe at /<full-path>/<name> with a .git subdir?

Yes, a bare repository.

P.

Re: What am I doing wrong?

[Michael J Gruber]

Paul Gardiner venit, vidit, dixit 16.05.2008 14:32:
> Michael J Gruber wrote:
>> Paul Gardiner venit, vidit, dixit 16.05.2008 13:25:
>>> I create the initial repository with
>>>
>>>      git-clone /<full-path>/<name>.git/ <folder>
>>>
>>> That works fine, but then I can't fetch. git-fetch gives the error
>>> "fatal: 'origin': unable to chdir or not a git archive"
>>> "fatal: The remote end hung up unexpectedly"
>>>
>>> P.
>> Are you trying to clone a bare repository?
>> Or is your repo maybe at /<full-path>/<name> with a .git subdir?
> 
> Yes, a bare repository.

Then, maybe the full list of command lines (including cd and git-fetch) 
would be helpful in order to track this down.

Michael

Re: What am I doing wrong?

[Paul Gardiner]

Michael J Gruber wrote:
> Paul Gardiner venit, vidit, dixit 16.05.2008 14:32:
>> Michael J Gruber wrote:
>>> Paul Gardiner venit, vidit, dixit 16.05.2008 13:25:
>>>> I create the initial repository with
>>>>
>>>>      git-clone /<full-path>/<name>.git/ <folder>
>>>>
>>>> That works fine, but then I can't fetch. git-fetch gives the error
>>>> "fatal: 'origin': unable to chdir or not a git archive"
>>>> "fatal: The remote end hung up unexpectedly"
>>>>
>>>> P.
>>> Are you trying to clone a bare repository?
>>> Or is your repo maybe at /<full-path>/<name> with a .git subdir?
>>
>> Yes, a bare repository.
> 
> Then, maybe the full list of command lines (including cd and git-fetch) 
> would be helpful in order to track this down.

Ok, sorry, thought it was probable something really obvious. Here's the
sequence (using git version 1.5.4).

$ git-clone /big/git/paul.git/ epage
Initialized empty Git repository in /home/paul/epage/.git/
719749 bolcks
$ cd epage
$ git-fetch
fatal: 'origin': unable to chdir or not a git archive
fatal: The remote end hung up unexpectedly



P.

Re: What am I doing wrong?

[Johannes Schindelin]

Hi,

On Fri, 16 May 2008, Paul Gardiner wrote:

> Michael J Gruber wrote:
> > Paul Gardiner venit, vidit, dixit 16.05.2008 14:32:
> > > Michael J Gruber wrote:
> > > > Paul Gardiner venit, vidit, dixit 16.05.2008 13:25:
> > > > > I create the initial repository with
> > > > >
> > > > >      git-clone /<full-path>/<name>.git/ <folder>
> > > > >
> > > > > That works fine, but then I can't fetch. git-fetch gives the error
> > > > > "fatal: 'origin': unable to chdir or not a git archive"
> > > > > "fatal: The remote end hung up unexpectedly"
> > > > >
> > > > > P.
> > > > Are you trying to clone a bare repository?
> > > > Or is your repo maybe at /<full-path>/<name> with a .git subdir?
> > >
> > > Yes, a bare repository.
> > 
> > Then, maybe the full list of command lines (including cd and git-fetch)
> > would be helpful in order to track this down.
> 
> Ok, sorry, thought it was probable something really obvious. Here's the
> sequence (using git version 1.5.4).
> 
> $ git-clone /big/git/paul.git/ epage
> Initialized empty Git repository in /home/paul/epage/.git/
> 719749 bolcks

Something tells me that this is not a copy/paste ;-)

> $ cd epage
> $ git-fetch
> fatal: 'origin': unable to chdir or not a git archive
> fatal: The remote end hung up unexpectedly

Is there a "[remote "origin"]" section in .git/config?  What Git version 
is this, anyway?

Ciao,
Dscho

Re: What am I doing wrong?

[Michael J Gruber]

Johannes Schindelin venit, vidit, dixit 16.05.2008 15:40:
> Hi,
> 
> On Fri, 16 May 2008, Paul Gardiner wrote:
> 
>> Michael J Gruber wrote:
>>> Paul Gardiner venit, vidit, dixit 16.05.2008 14:32:
>>>> Michael J Gruber wrote:
>>>>> Paul Gardiner venit, vidit, dixit 16.05.2008 13:25:
>>>>>> I create the initial repository with
>>>>>>
>>>>>>      git-clone /<full-path>/<name>.git/ <folder>
>>>>>>
>>>>>> That works fine, but then I can't fetch. git-fetch gives the error
>>>>>> "fatal: 'origin': unable to chdir or not a git archive"
>>>>>> "fatal: The remote end hung up unexpectedly"
>>>>>>
>>>>>> P.
>>>>> Are you trying to clone a bare repository?
>>>>> Or is your repo maybe at /<full-path>/<name> with a .git subdir?
>>>> Yes, a bare repository.
>>> Then, maybe the full list of command lines (including cd and git-fetch)
>>> would be helpful in order to track this down.
>> Ok, sorry, thought it was probable something really obvious. Here's the
>> sequence (using git version 1.5.4).
>>
>> $ git-clone /big/git/paul.git/ epage
>> Initialized empty Git repository in /home/paul/epage/.git/
>> 719749 bolcks
> 
> Something tells me that this is not a copy/paste ;-)

Let's just hope that's not units of boelkstoff ;)

>> $ cd epage
>> $ git-fetch
>> fatal: 'origin': unable to chdir or not a git archive
>> fatal: The remote end hung up unexpectedly
> 
> Is there a "[remote "origin"]" section in .git/config?  What Git version 
> is this, anyway?

1.5.4

Could git trip over that trailing slash? git 1.5.5.1 certainly doesn't.

BTW: The above shows something that confused me initially about cloning: 
git reports the creation of an empty repo, nothing else. But it does 
much more, of course, just without reporting.

Michael

Re: What am I doing wrong?

[Paul Gardiner]

Michael J Gruber wrote:
> Johannes Schindelin venit, vidit, dixit 16.05.2008 15:40:
>> Hi,
>>
>> On Fri, 16 May 2008, Paul Gardiner wrote:
>>
>>> Michael J Gruber wrote:
>>>> Paul Gardiner venit, vidit, dixit 16.05.2008 14:32:
>>>>> Michael J Gruber wrote:
>>>>>> Paul Gardiner venit, vidit, dixit 16.05.2008 13:25:
>>>>>>> I create the initial repository with
>>>>>>>
>>>>>>>      git-clone /<full-path>/<name>.git/ <folder>
>>>>>>>
>>>>>>> That works fine, but then I can't fetch. git-fetch gives the error
>>>>>>> "fatal: 'origin': unable to chdir or not a git archive"
>>>>>>> "fatal: The remote end hung up unexpectedly"
>>>>>>>
>>>>>>> P.
>>>>>> Are you trying to clone a bare repository?
>>>>>> Or is your repo maybe at /<full-path>/<name> with a .git subdir?
>>>>> Yes, a bare repository.
>>>> Then, maybe the full list of command lines (including cd and git-fetch)
>>>> would be helpful in order to track this down.
>>> Ok, sorry, thought it was probable something really obvious. Here's the
>>> sequence (using git version 1.5.4).
>>>
>>> $ git-clone /big/git/paul.git/ epage
>>> Initialized empty Git repository in /home/paul/epage/.git/
>>> 719749 bolcks
>>
>> Something tells me that this is not a copy/paste ;-)
> 
> Let's just hope that's not units of boelkstoff ;)
> 
>>> $ cd epage
>>> $ git-fetch
>>> fatal: 'origin': unable to chdir or not a git archive
>>> fatal: The remote end hung up unexpectedly
>>
>> Is there a "[remote "origin"]" section in .git/config?  What Git 
>> version is this, anyway?
> 
> 1.5.4
> 
> Could git trip over that trailing slash? git 1.5.5.1 certainly doesn't.

The documentation suggests having the trailing slash, and I think I
tried without, but I'll try again just in case.

> BTW: The above shows something that confused me initially about cloning: 
> git reports the creation of an empty repo, nothing else. But it does 
> much more, of course, just without reporting.

Oh yeah, I realise the fetch is already done by the clone, and that
git-fetch wouldn't bring anything new in right after the clone, but
there are other pushers for that repo.

P.

Re: What am I doing wrong?

[Paul Gardiner]

Johannes Schindelin wrote:
> Hi,
> 
> On Fri, 16 May 2008, Paul Gardiner wrote:
> 
>> Michael J Gruber wrote:
>>> Paul Gardiner venit, vidit, dixit 16.05.2008 14:32:
>>>> Michael J Gruber wrote:
>>>>> Paul Gardiner venit, vidit, dixit 16.05.2008 13:25:
>>>>>> I create the initial repository with
>>>>>>
>>>>>>      git-clone /<full-path>/<name>.git/ <folder>
>>>>>>
>>>>>> That works fine, but then I can't fetch. git-fetch gives the error
>>>>>> "fatal: 'origin': unable to chdir or not a git archive"
>>>>>> "fatal: The remote end hung up unexpectedly"
>>>>>>
>>>>>> P.
>>>>> Are you trying to clone a bare repository?
>>>>> Or is your repo maybe at /<full-path>/<name> with a .git subdir?
>>>> Yes, a bare repository.
>>> Then, maybe the full list of command lines (including cd and git-fetch)
>>> would be helpful in order to track this down.
>> Ok, sorry, thought it was probable something really obvious. Here's the
>> sequence (using git version 1.5.4).
>>
>> $ git-clone /big/git/paul.git/ epage
>> Initialized empty Git repository in /home/paul/epage/.git/
>> 719749 bolcks
> 
> Something tells me that this is not a copy/paste ;-)

The "big" bit you mean? :-) It just happened to be the name
chosen for the mount of a large disc when added to the
server.

>> $ cd epage
>> $ git-fetch
>> fatal: 'origin': unable to chdir or not a git archive
>> fatal: The remote end hung up unexpectedly
> 
> Is there a "[remote "origin"]" section in .git/config?  What Git version 
> is this, anyway?

No, not in /home/paul/epage/.git/config. There's just a [core] section. 
I guess that's the problem. I thought git-clone set that up automatically.

It's v1.5.4

P.

Re: What am I doing wrong?

[Kevin Ballard]

On May 16, 2008, at 10:56 AM, Paul Gardiner wrote:

>>> Ok, sorry, thought it was probable something really obvious.  
>>> Here's the
>>> sequence (using git version 1.5.4).
>>>
>>> $ git-clone /big/git/paul.git/ epage
>>> Initialized empty Git repository in /home/paul/epage/.git/
>>> 719749 bolcks
>> Something tells me that this is not a copy/paste ;-)
>
> The "big" bit you mean? :-) It just happened to be the name
> chosen for the mount of a large disc when added to the
> server.

No, I think it's the "bolcks" :P

-Kevin Ballard

-- 
Kevin Ballard
http://kevin.sb.org
kevin@sb.org
http://www.tildesoft.com

Re: What am I doing wrong?

[Paul Gardiner]

Kevin Ballard wrote:
> On May 16, 2008, at 10:56 AM, Paul Gardiner wrote:
> 
>>>> Ok, sorry, thought it was probable something really obvious. Here's the
>>>> sequence (using git version 1.5.4).
>>>>
>>>> $ git-clone /big/git/paul.git/ epage
>>>> Initialized empty Git repository in /home/paul/epage/.git/
>>>> 719749 bolcks
>>> Something tells me that this is not a copy/paste ;-)
>>
>> The "big" bit you mean? :-) It just happened to be the name
>> chosen for the mount of a large disc when added to the
>> server.
> 
> No, I think it's the "bolcks" :P

:-) Oh yeah, I left two letters out!

P.

Re: What am I doing wrong?

[Johannes Schindelin]

Hi,

On Fri, 16 May 2008, Paul Gardiner wrote:

> I create the initial repository with
> 
>     git-clone /<full-path>/<name>.git/ <folder>
> 
> That works fine, but then I can't fetch. git-fetch gives the error
> "fatal: 'origin': unable to chdir or not a git archive"
> "fatal: The remote end hung up unexpectedly"

Did you chdir into <folder> before trying to fetch?

Ciao,
Dscho

Re: What am I doing wrong?

[Paul Gardiner]

Johannes Schindelin wrote:
> Hi,
> 
> On Fri, 16 May 2008, Paul Gardiner wrote:
> 
>> I create the initial repository with
>>
>>     git-clone /<full-path>/<name>.git/ <folder>
>>
>> That works fine, but then I can't fetch. git-fetch gives the error
>> "fatal: 'origin': unable to chdir or not a git archive"
>> "fatal: The remote end hung up unexpectedly"
> 
> Did you chdir into <folder> before trying to fetch?

Yes, it wasn't that... well to be fair I forgot to chdir
the first time, but it warned me about that.

P.

What am i doing wrong?

[Neil Jones]

Im developing ASoC Driver for an SoC (I2S based).

When testing playback with aplay, I get 1 buffers worth of data played
back (10 periods) then playback stops due to a XRUN when my dma list
wraps back to the start because the available data >= stop_threshold ??

Here are my logs, interrupts are occurring at the correct time and my
buffer pointer increments by period size each time.

Any help would be appreciated

Aplay log:

# /usr/bin/aplay -vvv /var/sample96KHz_edit.wav
Playing WAVE '/var/sample96KHz_edit.wav' : Signed 16 bit Little Endian,
Rate 96000 Hz, Stereo
Plug PCM: Route conversion PCM (sformat=S16_LE)
  Transformation table:
    0 <- 0*0.5 + 1*0.5
Its setup is:
  stream       : PLAYBACK
  access       : RW_INTERLEAVED
  format       : S16_LE
  subformat    : STD
  channels     : 2
  rate         : 96000
  exact rate   : 96000 (96000/1)
  msbits       : 16
  buffer_size  : 48000
  period_size  : 4096
  period_time  : 42666
  tstamp_mode  : NONE
  period_step  : 1
  avail_min    : 4096
  period_event : 0
  start_threshold  : 48000
  stop_threshold   : 48000
  silence_threshold: 0
  silence_size : 0
  boundary     : 1572864000
Slave: Hardware PCM card 0 'Metamorph-Base' device 0 subdevice 0
Its setup is:
  stream       : PLAYBACK
  access       : MMAP_INTERLEAVED
  format       : S16_LE
  subformat    : STD
  channels     : 1
  rate         : 96000
  exact rate   : 96000 (96000/1)
  msbits       : 16
  buffer_size  : 48000
  period_size  : 4096
  period_time  : 42666
  tstamp_mode  : NONE
  period_step  : 1
  avail_min    : 4096
  period_event : 0
  start_threshold  : 48000
  stop_threshold   : 48000
  silence_threshold: 0
  silence_size : 0
  boundary     : 1572864000
Max peak (8192 samples): 0x00002594 ######               29%
Max peak (8192 samples): 0x00000df8 ###                  10%
Max peak (8192 samples): 0x00007fff #################### 99%
Max peak (8192 samples): 0x00006074 ################     75%
Max peak (8192 samples): 0x00003bff ##########           46%
Max peak (8192 samples): 0x00003e7b ##########           48%
Max peak (8192 samples): 0x00001abf #####                20%
Max peak (8192 samples): 0x000009e0 ##                   7%
Max peak (8192 samples): 0x000067df #################    81%
Max peak (8192 samples): 0x00001b45 #####                21%
Max peak (8192 samples): 0x00000b91 ##                   9%
Max peak (5888 samples): 0x000044a5 ###########          53%
underrun!!! (at least 83.448 ms long)
Status:
  state       : XRUN
  trigger_time: 4784.5629989
  tstamp      : 4784.88220967
  delay       : 0
  avail       : 48000
  avail_max   : 48000


Kernel Log:

PCM DMA IRQ: status 100000, timestamp 4483380 ms, 
ALSA sound/core/pcm_lib.c:250: period_update: pcmC0D0p:0:
pos=0x1000/0x1000/0xbb80, hwptr=0x0, hw_base=0x0, hw_intr=0x0
PCM DMA IRQ: status 120000, timestamp 4483430 ms, 
ALSA sound/core/pcm_lib.c:250: period_update: pcmC0D0p:0:
pos=0x2000/0x1000/0xbb80, hwptr=0x1000, hw_base=0x0, hw_intr=0x1000
PCM DMA IRQ: status 120000, timestamp 4483480 ms, 
ALSA sound/core/pcm_lib.c:250: period_update: pcmC0D0p:0:
pos=0x3000/0x1000/0xbb80, hwptr=0x2000, hw_base=0x0, hw_intr=0x2000
PCM DMA IRQ: status 120000, timestamp 4483530 ms, 
ALSA sound/core/pcm_lib.c:250: period_update: pcmC0D0p:0:
pos=0x4000/0x1000/0xbb80, hwptr=0x3000, hw_base=0x0, hw_intr=0x3000
PCM DMA IRQ: status 120000, timestamp 4483580 ms, 
ALSA sound/core/pcm_lib.c:250: period_update: pcmC0D0p:0:
pos=0x5000/0x1000/0xbb80, hwptr=0x4000, hw_base=0x0, hw_intr=0x4000
PCM DMA IRQ: status 120000, timestamp 4483630 ms, 
ALSA sound/core/pcm_lib.c:250: period_update: pcmC0D0p:0:
pos=0x6000/0x1000/0xbb80, hwptr=0x5000, hw_base=0x0, hw_intr=0x5000
PCM DMA IRQ: status 120000, timestamp 4483680 ms, 
ALSA sound/core/pcm_lib.c:250: period_update: pcmC0D0p:0:
pos=0x7000/0x1000/0xbb80, hwptr=0x6000, hw_base=0x0, hw_intr=0x6000
PCM DMA IRQ: status 120000, timestamp 4483730 ms, 
ALSA sound/core/pcm_lib.c:250: period_update: pcmC0D0p:0:
pos=0x8000/0x1000/0xbb80, hwptr=0x7000, hw_base=0x0, hw_intr=0x7000
PCM DMA IRQ: status 120000, timestamp 4483790 ms, 
ALSA sound/core/pcm_lib.c:250: period_update: pcmC0D0p:0:
pos=0x9000/0x1000/0xbb80, hwptr=0x8000, hw_base=0x0, hw_intr=0x8000
PCM DMA IRQ: status 120000, timestamp 4483840 ms, 
ALSA sound/core/pcm_lib.c:250: period_update: pcmC0D0p:0:
pos=0xa000/0x1000/0xbb80, hwptr=0x9000, hw_base=0x0, hw_intr=0x9000
PCM DMA IRQ: status 120000, timestamp 4483890 ms, 
ALSA sound/core/pcm_lib.c:250: period_update: pcmC0D0p:0:
pos=0x0/0x1000/0xbb80, hwptr=0xa000, hw_base=0x0, hw_intr=0xa000
ALSA sound/core/pcm_lib.c:160: XRUN: pcmC0D0p:0
-
This message is subject to Imagination Technologies' e-mail terms: http://www.imgtec.com/e-mail.htm

Imagination Technologies Ltd is a limited company registered in England No:  1306335 
Registered Office: Imagination House, Home Park Estate, Kings Langley, Hertfordshire, WD4 8LZ.  

Email to and from the company may be monitored for compliance and other administrative purposes.  
-

Re: What am i doing wrong?

[Mark Brown]

On Wed, Oct 28, 2009 at 05:33:51PM -0000, Neil Jones wrote:
> Im developing ASoC Driver for an SoC (I2S based).

> When testing playback with aplay, I get 1 buffers worth of data played
> back (10 periods) then playback stops due to a XRUN when my dma list
> wraps back to the start because the available data >= stop_threshold ??

> Here are my logs, interrupts are occurring at the correct time and my
> buffer pointer increments by period size each time.

> Any help would be appreciated

Posting your driver code would make it easier to advise you.

Re: What am i doing wrong?

[jassi brar]

On Thu, Oct 29, 2009 at 2:33 AM, Neil Jones <neil.jones@imgtec.com> wrote:
> PCM DMA IRQ: status 100000, timestamp 4483380 ms,
> ALSA sound/core/pcm_lib.c:250: period_update: pcmC0D0p:0:
> pos=0x1000/0x1000/0xbb80, hwptr=0x0, hw_base=0x0, hw_intr=0x0
> PCM DMA IRQ: status 120000, timestamp 4483430 ms,
> ALSA sound/core/pcm_lib.c:250: period_update: pcmC0D0p:0:
> pos=0x2000/0x1000/0xbb80, hwptr=0x1000, hw_base=0x0, hw_intr=0x1000
> PCM DMA IRQ: status 120000, timestamp 4483480 ms,
> ALSA sound/core/pcm_lib.c:250: period_update: pcmC0D0p:0:
> pos=0x3000/0x1000/0xbb80, hwptr=0x2000, hw_base=0x0, hw_intr=0x2000
> PCM DMA IRQ: status 120000, timestamp 4483530 ms,
> ALSA sound/core/pcm_lib.c:250: period_update: pcmC0D0p:0:
> pos=0x4000/0x1000/0xbb80, hwptr=0x3000, hw_base=0x0, hw_intr=0x3000
> PCM DMA IRQ: status 120000, timestamp 4483580 ms,
> ALSA sound/core/pcm_lib.c:250: period_update: pcmC0D0p:0:
> pos=0x5000/0x1000/0xbb80, hwptr=0x4000, hw_base=0x0, hw_intr=0x4000
> PCM DMA IRQ: status 120000, timestamp 4483630 ms,
> ALSA sound/core/pcm_lib.c:250: period_update: pcmC0D0p:0:
> pos=0x6000/0x1000/0xbb80, hwptr=0x5000, hw_base=0x0, hw_intr=0x5000
> PCM DMA IRQ: status 120000, timestamp 4483680 ms,
> ALSA sound/core/pcm_lib.c:250: period_update: pcmC0D0p:0:
> pos=0x7000/0x1000/0xbb80, hwptr=0x6000, hw_base=0x0, hw_intr=0x6000
> PCM DMA IRQ: status 120000, timestamp 4483730 ms,
> ALSA sound/core/pcm_lib.c:250: period_update: pcmC0D0p:0:
> pos=0x8000/0x1000/0xbb80, hwptr=0x7000, hw_base=0x0, hw_intr=0x7000
> PCM DMA IRQ: status 120000, timestamp 4483790 ms,
> ALSA sound/core/pcm_lib.c:250: period_update: pcmC0D0p:0:
> pos=0x9000/0x1000/0xbb80, hwptr=0x8000, hw_base=0x0, hw_intr=0x8000

> PCM DMA IRQ: status 120000, timestamp 4483840 ms,
> ALSA sound/core/pcm_lib.c:250: period_update: pcmC0D0p:0:
> pos=0xa000/0x1000/0xbb80, hwptr=0x9000, hw_base=0x0, hw_intr=0x9000
> PCM DMA IRQ: status 120000, timestamp 4483890 ms,
> ALSA sound/core/pcm_lib.c:250: period_update: pcmC0D0p:0:
> pos=0x0/0x1000/0xbb80, hwptr=0xa000, hw_base=0x0, hw_intr=0xa000

Missing IRQ@0xb000 after 0xa000?
Timestamp corresponds to 4800 period size but IRQs to 4096
Check that your DMA driver and snd_pcm_ops.pointer function returns
correct position.

Also, try setting constraint on buffer size to be an integral multiple
of period size, i.e, if
you don't take care of last shorter period elapsed than expected by ALSA

What am I doing wrong?

[Ed Tomlinson]

Hi

This process used to work.  I am not sure what is going wrong now and/or 
what requirements have changed.  I'd really appriecate another set of eyes 
looking at this.

The sending volume has:
# btrfs subvol list -pqu /snap 
ID 258 gen 416417 parent 5 top level 5 parent_uuid - uuid 
6447cef2-9b1a-c146-8dc3-b759ed2dd694 path homevol
ID 749 gen 399865 parent 258 top level 258 parent_uuid 
6447cef2-9b1a-c146-8dc3-b759ed2dd694 uuid 
c309c50a-8558-a242-86bd-d64b7f6ca0cd path homevol/backup
ID 750 gen 401012 parent 258 top level 258 parent_uuid 
6447cef2-9b1a-c146-8dc3-b759ed2dd694 uuid 
d29ffd19-8ca1-e248-ace0-fc174902f1f3 path 
homevol/backup.2015-27-6_07-04_22:00

The recieving volume has:
# btrfs subvol list -pquR /backup | grep 
c309c50a-8558-a242-86bd-d64b7f6ca0cd
ID 3698 gen 3116 parent 5 top level 5 parent_uuid - received_uuid 
c309c50a-8558-a242-86bd-d64b7f6ca0cd uuid 
18a46efa-3cc3-4742-925e-ea0681709592 path home/backup

But send/recieve is not working:
#  btrfs send -ve -p homevol/backup homevol/backup.2015-27-6_07-04_22:00 | 
btrfs receive -v /backup/home
At subvol homevol/backup.2015-27-6_07-04_22:00
At snapshot backup.2015-27-6_07-04_22:00
receiving snapshot backup.2015-27-6_07-04_22:00 
uuid=d29ffd19-8ca1-e248-ace0-fc174902f1f3, ctransid=401012 
parent_uuid=cb3ad856-ca0f-f744-b7c3-b33f2d5bc8d3, parent_ctransid=399865
ERROR: could not find parent subvolume

Yet the subvol homevol/backup has been sent (full) to and exists on /backup 
filesystem as can be seen in the two subvol lists, yet send/recieve cannot 
seem to find it for an incremental backup.  

Why?

TIA
Ed Tomlinson