* Chuck Harding <[email protected]> wrote:
> Which still exhibits the lockup of sox. I built a 2.6.12 vanilla kernel
> using the same .config as I used for 51-12 and the failure did not happen.
> just the process of booting up causes later invocations of sox to lockup
> in the D state. If I don't login to X and just run from a VT I can get
> it to lockup by running something like:
> $ for ((i=0;i<20;i++))
> >do
> >echo -ne "\r$i "
> >(play /usr/share/sounds/KDE_Beep_ShortBeep.wav &)
> >done
>
> after about 14 or so iterations of the loop and thereafter no more
> sound can be played.
tried it and cannot reproduce it, so i'll need the full backtrace of all
tasks in your system, whenever sox gets stuck, via:
echo t > /proc/sysrq-trigger
dmesg -s 10000000 > toingo.txt
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- Re: Real-Time Preemption, -RT-2.6.12-final-V0.7.50-24
- Re: Real-Time Preemption, -RT-2.6.12-final-V0.7.50-24
- Re: Real-Time Preemption, -RT-2.6.12-final-V0.7.50-45
- Re: Real-Time Preemption, -RT-2.6.12-final-V0.7.50-45
- Re: Real-Time Preemption, -RT-2.6.12-final-V0.7.50-45
- Re: Real-Time Preemption, -RT-2.6.12-final-V0.7.50-45
- Re: Real-Time Preemption, -RT-2.6.12-final-V0.7.50-45
- Re: Real-Time Preemption, -RT-2.6.12-final-V0.7.50-45
- Re: Real-Time Preemption, -RT-2.6.12-final-V0.7.50-45
- Re: Real-Time Preemption, -RT-2.6.12-final-V0.7.51-12
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |