Content-Type: text/plain; charset=UTF-8
Neither of those lines have anything that looks like it would trigger an
There are no KERN_ERR calls remotely close.
On Wed, Feb 2, 2011 at 11:20, Gabriel Beddingfield wrote:
Content-Type: text/html; charset=UTF-8
Neither of those lines have anything that looks like it=
would trigger an error.There are no KERN_ERR cal=
ls remotely close.
On Wed, Feb 2, 2011 at 11:20, Gabriel Beddingfield <email@example.com> wrote=
OK. =C2=A0Next step is to dig in to what these mean:
[ =C2=A0 46.508331] ALSA urb.c:480: frame 0 active: -75
[ =C2=A0 46.560332] ALSA urb.c:480: frame 0 active: -75
[ =C2=A0 98.971734] ALSA urb.c:146: timeout: still 7 active urbs..
[ =C2=A0104.970917] ALSA urb.c:146: timeout: still 2 active urbs..
[ =C2=A0121.260876] ALSA pcm.c:223: 4:2:1: usb_set_interface failed
Others might know what these mean.
Me? =C2=A0I don't. =C2=A0I'd have to inspect the kernel source code=
. =C2=A0urb.c and
pcm.c are file names in the kernel sources (possibly in the sound/
folder). =C2=A0The number after the colon (:) is a line number. =C2=A0So, i=
go to urb.c line 480, you see something like printk(KERN_ERR "frame:
%d active: %d", frame, active); =C2=A0The code around might give a clu=
what actually failed.