From: Daniel Mack <zonque@gmail.com>
To: Dr Nicholas J Bailey <nicholas.bailey@glasgow.ac.uk>
Cc: "tiwai@suse.de" <tiwai@suse.de>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Guido Aulisi <guido.aulisi@gmail.com>
Subject: Re: [PATCH v2] ALSA: snd-usb-usx2y: remove bogus frame checks
Date: Mon, 07 Oct 2013 17:11:44 +0200 [thread overview]
Message-ID: <5252CF30.7030002@gmail.com> (raw)
In-Reply-To: <27085905.a7dazzfD9V@arial>
On 07.10.2013 16:58, Dr Nicholas J Bailey wrote:
> For me, this patch alone fails in much the same way (possibly exactly the same
> way) as before the previous patch.
>
> From audacity (probably not much use unless you know the source code... I
> don't):
[...]
> nick@arial:/usr/src$ dmesg | tail
> [ 111.667015] usb 2-1.6.4: New USB device strings: Mfr=0, Product=0,
> SerialNumber=0
> [ 114.707156] Sequence Error!(hcd_frame=3 ep=8in;wait=1024,frame=0).
> [ 114.707156] Most probably some urb of usb-frame 1024 is still missing.
You certainly haven't booted a kernel which contains the patch we're
talking about here. The only occurance of the error message you quote
was removed by this patch, so a patched kernel can't possibly produce
what you see in your logs.
Please check your setup again and see what 'uname -a' says.
Daniel
next prev parent reply other threads:[~2013-10-07 15:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-02 15:49 [PATCH v2] ALSA: snd-usb-usx2y: remove bogus frame checks Daniel Mack
2013-10-03 10:25 ` [PATCH v2] ALSA: snd-usb-usx2y: remove bogus frame checks -- SUCCESS Dr Nicholas J Bailey
2013-10-07 7:35 ` Takashi Iwai
2013-10-06 8:29 ` [PATCH v2] ALSA: snd-usb-usx2y: remove bogus frame checks Guido Aulisi
2013-10-07 7:41 ` Takashi Iwai
2013-10-07 14:58 ` Dr Nicholas J Bailey
2013-10-07 15:11 ` Daniel Mack [this message]
2013-10-07 15:35 ` Takashi Iwai
2013-10-07 15:34 ` Daniel Mack
2013-10-07 16:20 ` Dr Nicholas J Bailey
2013-10-07 16:31 ` Dr Nicholas J Bailey
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=5252CF30.7030002@gmail.com \
--to=zonque@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=guido.aulisi@gmail.com \
--cc=nicholas.bailey@glasgow.ac.uk \
--cc=tiwai@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).