Re: Ooops in btaudio?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



>  Invalid operand 0000
> =2E..
>  Call Trace [ hexadecimal stack trace which I know is meaningless here ]

It isn't meaningless, it is the only way to debug that problem.  See
Documentation/oops-tracing.txt (and Documentation/serial-console.txt
maybe ...).

>  <6>btaudio : buffer overrun

>  I do nothing with btaudio.

This simply can't happen if you don't use btaudio.  The message is
printed by the btaudio irq handler and you can never ever reach that
place in the code if you don't record something from btaudio.

  Gerd

-- 
#define	ENOCLUE 125 /* userland programmer induced race condition */





[Index of Archives]     [Linux DVB]     [Video Disk Recorder]     [Asterisk]     [Photo]     [DCCP]     [Netdev]     [Xorg]     [Util Linux NG]     [Xfree86]     [Free Photo Albums]     [Fedora Users]     [Fedora Women]     [ALSA Users]     [ALSA Devel]     [Linux USB]

Powered by Linux