Em Fri, May 18, 2001 at 03:02:18PM -0300, Rik van Riel escreveu:
> On Thu, 17 May 2001, Ingo Oeser wrote:
> > On Wed, May 16, 2001 at 08:02:06PM -0300, Rik van Riel wrote:
> > > I'm seeing a similar thing on 2.4.4-pre[23], but in a far less
> > > serious way. Using xmms the music stops after
On Thu, 17 May 2001, Ingo Oeser wrote:
> On Wed, May 16, 2001 at 08:02:06PM -0300, Rik van Riel wrote:
> > I'm seeing a similar thing on 2.4.4-pre[23], but in a far less
> > serious way. Using xmms the music stops after anything between
> > a few seconds and a minute, I suspect a race condition
On Thu, 17 May 2001, Ingo Oeser wrote:
On Wed, May 16, 2001 at 08:02:06PM -0300, Rik van Riel wrote:
I'm seeing a similar thing on 2.4.4-pre[23], but in a far less
serious way. Using xmms the music stops after anything between
a few seconds and a minute, I suspect a race condition
Em Fri, May 18, 2001 at 03:02:18PM -0300, Rik van Riel escreveu:
On Thu, 17 May 2001, Ingo Oeser wrote:
On Wed, May 16, 2001 at 08:02:06PM -0300, Rik van Riel wrote:
I'm seeing a similar thing on 2.4.4-pre[23], but in a far less
serious way. Using xmms the music stops after anything
device 6300 (rev 21)
On Thu, 17 May 2001, Ingo Oeser wrote:
> Date: Thu, 17 May 2001 13:58:08 +0200
> From: Ingo Oeser <[EMAIL PROTECTED]>
> To: Rik van Riel <[EMAIL PROTECTED]>
> Cc: virii <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
> Subject: Re: cmpci sound chip lock
On Wed, May 16, 2001 at 08:02:06PM -0300, Rik van Riel wrote:
> I'm seeing a similar thing on 2.4.4-pre[23], but in a far less
> serious way. Using xmms the music stops after anything between
> a few seconds and a minute, I suspect a race condition somewhere.
>
> Using mpg123 everything works
On Wed, May 16, 2001 at 08:02:06PM -0300, Rik van Riel wrote:
I'm seeing a similar thing on 2.4.4-pre[23], but in a far less
serious way. Using xmms the music stops after anything between
a few seconds and a minute, I suspect a race condition somewhere.
Using mpg123 everything works fine...
)
On Thu, 17 May 2001, Ingo Oeser wrote:
Date: Thu, 17 May 2001 13:58:08 +0200
From: Ingo Oeser [EMAIL PROTECTED]
To: Rik van Riel [EMAIL PROTECTED]
Cc: virii [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: cmpci sound chip lockup
On Wed, May 16, 2001 at 08:02:06PM -0300, Rik van Riel wrote
Hello,
This is known issue. cmpci driver included in the kernel is way too old.
I'm using newer driver (revision 4.14) and it works just fine. It was
announced on lkml long time ago. Last time I checked there was even newer
driver - 5.64. The one in the kernel has version 2.41. Is it possible
Just a "me, too" here. I see this when using the in-kernel driver. I'm
now using... 4.12, I think. At any rate, the error doesn't occur, or at
least occurs to rarely as to escape notice, with this driver. Might I
suggest the kernel's version be upgraded? The updated driver was posted
here on
On Wed, 16 May 2001, virii wrote:
> The attatched file is the format for reporting bugs.
Too bad my mailreader doesn't quote that thing .. oh well, lets
just replace your bugreport with mine ;)
I'm seeing a similar thing on 2.4.4-pre[23], but in a far less
serious way. Using xmms the music
The attatched file is the format for reporting bugs.
1) While playing mp3's on mpg123 it'll lock up for 3/4 seconds, and XMMS just stops
all together
2) May 16 05:46:10 virii kernel: cmpci: dma timed out??
May 16 06:05:43 virii kernel: cmpci: write: chip lockup? dmasz 65536 fragsz 1024
The attatched file is the format for reporting bugs.
1) While playing mp3's on mpg123 it'll lock up for 3/4 seconds, and XMMS just stops
all together
2) May 16 05:46:10 virii kernel: cmpci: dma timed out??
May 16 06:05:43 virii kernel: cmpci: write: chip lockup? dmasz 65536 fragsz 1024
On Wed, 16 May 2001, virii wrote:
The attatched file is the format for reporting bugs.
Too bad my mailreader doesn't quote that thing .. oh well, lets
just replace your bugreport with mine ;)
I'm seeing a similar thing on 2.4.4-pre[23], but in a far less
serious way. Using xmms the music
Just a me, too here. I see this when using the in-kernel driver. I'm
now using... 4.12, I think. At any rate, the error doesn't occur, or at
least occurs to rarely as to escape notice, with this driver. Might I
suggest the kernel's version be upgraded? The updated driver was posted
here on
Hello,
This is known issue. cmpci driver included in the kernel is way too old.
I'm using newer driver (revision 4.14) and it works just fine. It was
announced on lkml long time ago. Last time I checked there was even newer
driver - 5.64. The one in the kernel has version 2.41. Is it possible
16 matches
Mail list logo
