On Thu, Feb 14, 2002 at 01:45:02PM +0100, Peter Surda wrote:
> > could you try the attached patch?
> Applied (by hand) and compiled, but I'm in the middle of compiling X right now
> so I'll have to wait a couple of hours 'till I can reboot. I'll report then.
Yes it fixed it indeed, I am unable to
On Thu, Feb 14, 2002 at 01:22:57PM +0100, Takashi Iwai wrote:
> Hi,
hi
> looks like you hit a known bug existing since long time..
> could you try the attached patch?
Applied (by hand) and compiled, but I'm in the middle of compiling X right now
so I'll have to wait a couple of hours 'till I can
Hi,
At Thu, 14 Feb 2002 12:42:48 +0100,
Peter Surda wrote:
>
> Hi!
>
> On Thu, Feb 14, 2002 at 11:56:45AM +0100, Erik Inge Bolsř wrote:
> > >> >After they happen, sound card remains silent and module blocked.
> > >> Decode the oopses with ksymoops, then we'll have a better chance of
> > >> figu
Hi!
On Thu, Feb 14, 2002 at 11:56:45AM +0100, Erik Inge Bolsř wrote:
> >> >After they happen, sound card remains silent and module blocked.
> >> Decode the oopses with ksymoops, then we'll have a better chance of
> >> figuring out what the problem is.
> >Attached, all 4 oopses thru ksymoops -dd.
On Thu, 14 Feb 2002, Peter Surda wrote:
>Hi!
>
>Finally an answer :-)
>
>On Thu, Feb 14, 2002 at 01:21:43AM +0100, Erik Inge Bolsø wrote:
>>
>> >After they happen, sound card remains silent and module blocked.
>> Decode the oopses with ksymoops, then we'll have a better chance of
>> figuring out
Hi!
Finally an answer :-)
On Thu, Feb 14, 2002 at 01:21:43AM +0100, Erik Inge Bolsř wrote:
>
> >After they happen, sound card remains silent and module blocked.
> Decode the oopses with ksymoops, then we'll have a better chance of
> figuring out what the problem is.
Attached, all 4 oopses thru
On Thu, 14 Feb 2002, Peter Surda wrote:
>After they happen, sound card remains silent and module blocked.
Decode the oopses with ksymoops, then we'll have a better chance of
figuring out what the problem is.
--
Erik I. Bolsø | email:
The UNIX philosophy basically involves giving you enough r
Hi!
I complained some time ago, several times, that 32kHz seems to produce oops on
my onboard ECS K7S5A. It seems it isn't exactly 32kHz producing this, but
buffer size combined with frequency. Because current cvs aviplay also manages
to cause oops on 44.1kHz. Zdenek, aviplay maintainer, told me
