14 Nov
2004
14 Nov
'04
1:58 a.m.
I got the latest alsa-drivers from CVS, compiled and installed
them, and it's still freezing up. I can have the modules loaded
for as long as I like, but it's when I start jack that it seems
to have problems. Most recently, I started qjackctl, it worked
until I started Ardour, at which point qjackctl died. I killed
and restarted jackd, and as soon as I started jackd my computer
froze. Every time it freezes like this, my caps lock and scroll
lock lights blink together. I got the same -11 error message
again, but this time it happened a few minutes before the freeze,
the first time I started jack.
I ran xmms with the alsa output plugin and after a minute or 2
the audio stopped with the message on syslog:
kernel: ALSA usbusx2yaudio.c:211:
usb_submit_urb() returned -11
kernel: usb-uhci.c: uhci_submit_urb: pipesize for pipe f0000 is zero
kernel: ALSA usbusx2yaudio.c:211: usb_submit_urb() returned -90
kernel: usb-uhci.c: uhci_submit_urb: pipesize for pipe f0000 is zero
kernel: ALSA usbusx2yaudio.c:211: usb_submit_urb() returned -90
any ideas on what this means, or other useful tests I could run?
Thanks,
spencer
14 Nov
14 Nov
7:30 p.m.
Am Sonntag 14 November 2004 09:57 schrieb Spencer Russell:
I got the latest alsa-drivers from CVS, compiled and
installed
them, and it's still freezing up. I can have the modules loaded
for as long as I like, but it's when I start jack that it seems
to have problems. Most recently, I started qjackctl, it worked
until I started Ardour, at which point qjackctl died. I killed
and restarted jackd, and as soon as I started jackd my computer
froze. Every time it freezes like this, my caps lock and scroll
lock lights blink together. I got the same -11 error message
I think the blinking
is just a sign for a hard crash.
To know the exact reason, you have to set up a second machine and run a "serial
console"
or a "netconsole" on it. See kernel Document tree and linux-kernel list. An
archive site:
http://marc.theaimsgroup.com/?l=linux-kernel.
again, but this time it happened a few minutes before
the freeze,
the first time I started jack.
I ran xmms with the alsa output plugin and after a minute or 2
the audio stopped with the message on syslog:
kernel: ALSA usbusx2yaudio.c:211:
usb_submit_urb() returned -11
kernel: usb-uhci.c: uhci_submit_urb: pipesize for pipe f0000 is zero
kernel: ALSA usbusx2yaudio.c:211: usb_submit_urb() returned -90
kernel: usb-uhci.c: uhci_submit_urb: pipesize for pipe f0000 is zero
kernel: ALSA usbusx2yaudio.c:211: usb_submit_urb() returned -90
You might ask on
the linux-usb-devel list about this, an archive of it is at:
http://marc.theaimsgroup.com/?l=linux-usb-devel
Some chipsets are tricky. My via PIII box will only host us428 on the "extra"
USB-header thats on the mobo.
The "normal" one on the back of the case doesn't do it. (though the
"normal" doesn't crash neither)
Also you might file this all at:
https://bugtrack.alsa-project.org/alsa-bug
In any case please supply the outputs of lspci and lsusb.
regards, Karsten
16 Nov
16 Nov
9:06 p.m.
Am Sonntag 14 November 2004 09:57 schrieb Spencer
Russell:
> I got the latest alsa-drivers from CVS, compiled and installed
> them, and it's still freezing up. I can have the modules loaded
> for as long as I like, but it's when I start jack that it seems
> to have problems. Most recently, I started qjackctl, it worked
> until I started Ardour, at which point qjackctl died. I killed
> and restarted jackd, and as soon as I started jackd my computer
> froze. Every time it freezes like this, my caps lock and scroll
> lock lights blink together. I got the same -11 error message
interestingly, gerard van dongen and i witnessed the exact same
behaviour on the machines rented for our workshop on ardour at DEAF in
rotterdam last week. however, these machines weren't running ardour or
JACK at the time - any time they went into the X screensaver, it
appeared, they died in this way. they were running a reasonably recent
Gentoo distribution.
I think the blinking is just a sign for a hard crash.
is there evidence of this anywhere? neither gerard or i had ever seen
this pattern of flashing LEDs.
--p
9:43 p.m.
On Mon, 2004-11-15 at 03:51, Paul Davis wrote:
Some X screensavers that use opengl (and 3d graphics) can crash hard the
X subsystem.
I think kernel oops'es do that (blink the keyboard leds). At that point
there is not much you can do except power cycle or use the sysrq key if
that's enabled.
Hope rotterdam was fun!
-- Fernando
Am Sonntag 14
November 2004 09:57 schrieb Spencer Russell:
> I got the latest alsa-drivers from CVS, compiled and installed
> them, and it's still freezing up. I can have the modules loaded
> for as long as I like, but it's when I start jack that it seems
> to have problems. Most recently, I started qjackctl, it worked
> until I started Ardour, at which point qjackctl died. I killed
> and restarted jackd, and as soon as I started jackd my computer
> froze. Every time it freezes like this, my caps lock and scroll
> lock lights blink together. I got the same -11 error message
interestingly, gerard van dongen and i witnessed the exact same
behaviour on the machines rented for our workshop on ardour at DEAF in
rotterdam last week. however, these machines weren't running ardour or
JACK at the time - any time they went into the X screensaver, it
appeared, they died in this way. they were running a reasonably recent
Gentoo distribution. I think the
blinking is just a sign for a hard crash.
is there evidence of this anywhere? neither gerard or i had ever seen
this pattern of flashing LEDs.
7341
days inactive
7343
days old
linux-audio-dev@lists.linuxaudio.org
3 comments
4 participants
participants (4)
-
Fernando Lopez-Lezcano -
Karsten Wiese -
Paul Davis -
Spencer Russell