* trouble on ppc32?
@ 2006-02-20 23:12 Falko Schmidt
2006-02-21 15:17 ` Takashi Iwai
0 siblings, 1 reply; 5+ messages in thread
From: Falko Schmidt @ 2006-02-20 23:12 UTC (permalink / raw)
To: alsa-devel
Hello,
I'm using a 32bit PowerPC based RS/6000 (43p-140) trying to get at least
one sound card to work. All other 'machine-independent' drivers for
cards such as NICs and disk controllers work fine.
I tried four different sound cards on kernels 2.6.8 and 2.6.15 which
work fine on x86 and non-x86 machines (using the same kernel versions).
Are there known issues regarding ALSA drivers on ppc? Or might it be
faulty hardware on the system side?
I'd like to fix some of the drivers but I doubt that it's a driver
specific problem looking at the number of different cards used.
Any ideas are welcome.
Thanks a lot in advance,
Falko
-------------
Soundblaster 16 PnP (ISA):
-------------
pnp: Device 00:01.00 activated.
pnp: Device 00:01.00 disabled.
ALSA /usr/src/modules/alsa-driver/alsa-kernel/isa/sb/sb16.c:653: Sound Blaster 16 soundcard not found or device busy
ALSA /usr/src/modules/alsa-driver/alsa-kernel/isa/sb/sb16.c:657: In case, if you have AWE card, try snd-sbawe module
pnp: Device 00:01.00 activated.
pnp: Device 00:01.00 disabled.
ALSA /usr/src/modules/alsa-driver/alsa-kernel/isa/sb/sb16.c:653: Sound Blaster 16 soundcard not found or device busy
ALSA /usr/src/modules/alsa-driver/alsa-kernel/isa/sb/sb16.c:657: In case, if you have AWE card, try snd-sbawe module
-------------
Terratec DMX Xfire 1024 (PCI):
-------------
Feb 20 14:39:21 cyan kernel: ALSA /usr/src/modules/alsa-driver/alsa-kernel/pci/c
s46xx/cs46xx_lib.c:427: cs46xx: failure waiting for FIFO command to complete
Feb 20 14:43:20 cyan kernel: ALSA /usr/src/modules/alsa-driver/alsa-kernel/pci/c
s46xx/cs46xx_lib.c:427: cs46xx: failure waiting for FIFO command to complete
-------------
Soundblaster Live 512 (PCI):
-------------
Feb 20 21:54:43 cyan kernel: PCI: Enabling device 0000:01:03.0 (0104 -> 0105)
Feb 20 21:54:43 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba3f000)!!
Feb 20 21:54:59 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba21000)!!
Feb 20 21:54:59 cyan kernel: emu: failure page = 0
Feb 20 21:54:59 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba21000)!!
Feb 20 21:54:59 cyan kernel: emu: failure page = 0
Feb 20 21:55:13 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba21000)!!
Feb 20 21:55:13 cyan kernel: emu: failure page = 0
Feb 20 21:55:13 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba21000)!!
Feb 20 21:55:13 cyan kernel: emu: failure page = 0
Feb 20 21:55:13 cyan kernel: max memory size is 0x7fffffff (addr = 0x8baa1000)!!
Feb 20 21:55:13 cyan kernel: emu: failure page = 0
Feb 20 21:55:13 cyan kernel: max memory size is 0x7fffffff (addr = 0x8baa1000)!!
Feb 20 21:55:13 cyan kernel: emu: failure page = 0
-------------
S3 Sonic Vibes (PCI):
-------------
Feb 20 18:34:48 cyan kernel: PCI: Enabling device 0000:01:03.0 (0004 -> 0005)
Feb 20 18:34:48 cyan kernel: BIOS did not allocate DDMA channel A i/o, allocated
at 0x7a00
Feb 20 18:34:48 cyan kernel: BIOS did not allocate DDMA channel C i/o, allocated
at 0x7a10
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: trouble on ppc32?
2006-02-20 23:12 trouble on ppc32? Falko Schmidt
@ 2006-02-21 15:17 ` Takashi Iwai
2006-02-22 17:02 ` Falko Schmidt
0 siblings, 1 reply; 5+ messages in thread
From: Takashi Iwai @ 2006-02-21 15:17 UTC (permalink / raw)
To: Falko Schmidt; +Cc: alsa-devel
At Tue, 21 Feb 2006 00:12:40 +0100,
Falko Schmidt wrote:
>
> Hello,
>
> I'm using a 32bit PowerPC based RS/6000 (43p-140) trying to get at least
> one sound card to work. All other 'machine-independent' drivers for
> cards such as NICs and disk controllers work fine.
>
> I tried four different sound cards on kernels 2.6.8 and 2.6.15 which
> work fine on x86 and non-x86 machines (using the same kernel versions).
>
> Are there known issues regarding ALSA drivers on ppc? Or might it be
> faulty hardware on the system side?
>
> I'd like to fix some of the drivers but I doubt that it's a driver
> specific problem looking at the number of different cards used.
>
> Any ideas are welcome.
>
> Thanks a lot in advance,
>
> Falko
>
> -------------
> Soundblaster 16 PnP (ISA):
> -------------
>
> pnp: Device 00:01.00 activated.
> pnp: Device 00:01.00 disabled.
> ALSA /usr/src/modules/alsa-driver/alsa-kernel/isa/sb/sb16.c:653: Sound Blaster 16 soundcard not found or device busy
> ALSA /usr/src/modules/alsa-driver/alsa-kernel/isa/sb/sb16.c:657: In case, if you have AWE card, try snd-sbawe module
> pnp: Device 00:01.00 activated.
> pnp: Device 00:01.00 disabled.
> ALSA /usr/src/modules/alsa-driver/alsa-kernel/isa/sb/sb16.c:653: Sound Blaster 16 soundcard not found or device busy
> ALSA /usr/src/modules/alsa-driver/alsa-kernel/isa/sb/sb16.c:657: In case, if you have AWE card, try snd-sbawe module
Not sure what's wrong there, but you should check the pnp resources.
> -------------
> Terratec DMX Xfire 1024 (PCI):
> -------------
>
> Feb 20 14:39:21 cyan kernel: ALSA /usr/src/modules/alsa-driver/alsa-kernel/pci/c
> s46xx/cs46xx_lib.c:427: cs46xx: failure waiting for FIFO command to complete
> Feb 20 14:43:20 cyan kernel: ALSA /usr/src/modules/alsa-driver/alsa-kernel/pci/c
> s46xx/cs46xx_lib.c:427: cs46xx: failure waiting for FIFO command to complete
cs46xx might be problematic, possibly related with BIOS
initialization. The FIFO error appears also with some other devices
even on i386, especially after suspend.
> -------------
> Soundblaster Live 512 (PCI):
> -------------
>
> Feb 20 21:54:43 cyan kernel: PCI: Enabling device 0000:01:03.0 (0104 -> 0105)
> Feb 20 21:54:43 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba3f000)!!
> Feb 20 21:54:59 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba21000)!!
> Feb 20 21:54:59 cyan kernel: emu: failure page = 0
> Feb 20 21:54:59 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba21000)!!
> Feb 20 21:54:59 cyan kernel: emu: failure page = 0
> Feb 20 21:55:13 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba21000)!!
> Feb 20 21:55:13 cyan kernel: emu: failure page = 0
> Feb 20 21:55:13 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba21000)!!
> Feb 20 21:55:13 cyan kernel: emu: failure page = 0
> Feb 20 21:55:13 cyan kernel: max memory size is 0x7fffffff (addr = 0x8baa1000)!!
> Feb 20 21:55:13 cyan kernel: emu: failure page = 0
> Feb 20 21:55:13 cyan kernel: max memory size is 0x7fffffff (addr = 0x8baa1000)!!
> Feb 20 21:55:13 cyan kernel: emu: failure page = 0
It's not the fault of driver but because of ppc's dma_alloc_coherent().
It doesn't allocate memories in the given coherent_dma_mask.
> -------------
> S3 Sonic Vibes (PCI):
> -------------
>
> Feb 20 18:34:48 cyan kernel: PCI: Enabling device 0000:01:03.0 (0004 -> 0005)
> Feb 20 18:34:48 cyan kernel: BIOS did not allocate DDMA channel A i/o, allocated
> at 0x7a00
> Feb 20 18:34:48 cyan kernel: BIOS did not allocate DDMA channel C i/o, allocated
> at 0x7a10
Likely BIOS-related problem. Hard to fix.
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: trouble on ppc32?
2006-02-21 15:17 ` Takashi Iwai
@ 2006-02-22 17:02 ` Falko Schmidt
2006-02-24 18:52 ` Takashi Iwai
0 siblings, 1 reply; 5+ messages in thread
From: Falko Schmidt @ 2006-02-22 17:02 UTC (permalink / raw)
To: alsa-devel
On Tue, Feb 21, 2006 at 04:17:48PM +0100, Takashi Iwai wrote:
> > -------------
> > Soundblaster Live 512 (PCI):
> > -------------
> >
> > Feb 20 21:54:43 cyan kernel: PCI: Enabling device 0000:01:03.0 (0104 -> 0105)
> > Feb 20 21:54:43 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba3f000)!!
> > Feb 20 21:54:59 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba21000)!!
> > Feb 20 21:54:59 cyan kernel: emu: failure page = 0
> > Feb 20 21:54:59 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba21000)!!
> > Feb 20 21:54:59 cyan kernel: emu: failure page = 0
> > Feb 20 21:55:13 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba21000)!!
> > Feb 20 21:55:13 cyan kernel: emu: failure page = 0
> > Feb 20 21:55:13 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba21000)!!
> > Feb 20 21:55:13 cyan kernel: emu: failure page = 0
> > Feb 20 21:55:13 cyan kernel: max memory size is 0x7fffffff (addr = 0x8baa1000)!!
> > Feb 20 21:55:13 cyan kernel: emu: failure page = 0
> > Feb 20 21:55:13 cyan kernel: max memory size is 0x7fffffff (addr = 0x8baa1000)!!
> > Feb 20 21:55:13 cyan kernel: emu: failure page = 0
>
> It's not the fault of driver but because of ppc's dma_alloc_coherent().
> It doesn't allocate memories in the given coherent_dma_mask.
That sounds interesting. Thanks for pointing it out.
Falko
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: trouble on ppc32?
2006-02-22 17:02 ` Falko Schmidt
@ 2006-02-24 18:52 ` Takashi Iwai
2006-02-28 15:41 ` Falko Schmidt
0 siblings, 1 reply; 5+ messages in thread
From: Takashi Iwai @ 2006-02-24 18:52 UTC (permalink / raw)
To: Falko Schmidt; +Cc: alsa-devel
At Wed, 22 Feb 2006 18:02:01 +0100,
Falko Schmidt wrote:
>
> On Tue, Feb 21, 2006 at 04:17:48PM +0100, Takashi Iwai wrote:
> > > -------------
> > > Soundblaster Live 512 (PCI):
> > > -------------
> > >
> > > Feb 20 21:54:43 cyan kernel: PCI: Enabling device 0000:01:03.0 (0104 -> 0105)
> > > Feb 20 21:54:43 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba3f000)!!
> > > Feb 20 21:54:59 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba21000)!!
> > > Feb 20 21:54:59 cyan kernel: emu: failure page = 0
> > > Feb 20 21:54:59 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba21000)!!
> > > Feb 20 21:54:59 cyan kernel: emu: failure page = 0
> > > Feb 20 21:55:13 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba21000)!!
> > > Feb 20 21:55:13 cyan kernel: emu: failure page = 0
> > > Feb 20 21:55:13 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba21000)!!
> > > Feb 20 21:55:13 cyan kernel: emu: failure page = 0
> > > Feb 20 21:55:13 cyan kernel: max memory size is 0x7fffffff (addr = 0x8baa1000)!!
> > > Feb 20 21:55:13 cyan kernel: emu: failure page = 0
> > > Feb 20 21:55:13 cyan kernel: max memory size is 0x7fffffff (addr = 0x8baa1000)!!
> > > Feb 20 21:55:13 cyan kernel: emu: failure page = 0
> >
> > It's not the fault of driver but because of ppc's dma_alloc_coherent().
> > It doesn't allocate memories in the given coherent_dma_mask.
>
> That sounds interesting. Thanks for pointing it out.
Does the patch below have any influence? It's a blind-shot, though...
Takashi
diff --git a/arch/powerpc/kernel/iommu.c b/arch/powerpc/kernel/iommu.c
index 946f321..b77caa7 100644
--- a/arch/powerpc/kernel/iommu.c
+++ b/arch/powerpc/kernel/iommu.c
@@ -546,6 +546,7 @@ void *iommu_alloc_coherent(struct iommu_
return NULL;
/* Alloc enough pages (and possibly more) */
+ again:
ret = (void *)__get_free_pages(flag, order);
if (!ret)
return NULL;
@@ -556,6 +557,15 @@ void *iommu_alloc_coherent(struct iommu_
if (mapping == DMA_ERROR_CODE) {
free_pages((unsigned long)ret, order);
ret = NULL;
+ } else if (dev->coherent_dma_mask &&
+ mapping >= dev->coherent_dma_mask) {
+ iommu_free(tbl, mapping, npages);
+ free_pages((unsigned long)ret, order);
+ if (! (flag & __GFP_DMA)) {
+ flag |= __GFP_DMA;
+ goto again;
+ }
+ ret = NULL;
} else
*dma_handle = mapping;
return ret;
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: trouble on ppc32?
2006-02-24 18:52 ` Takashi Iwai
@ 2006-02-28 15:41 ` Falko Schmidt
0 siblings, 0 replies; 5+ messages in thread
From: Falko Schmidt @ 2006-02-28 15:41 UTC (permalink / raw)
To: alsa-devel
On Fri, Feb 24, 2006 at 07:52:04PM +0100, Takashi Iwai wrote:
> At Wed, 22 Feb 2006 18:02:01 +0100,
> Falko Schmidt wrote:
> >
> > On Tue, Feb 21, 2006 at 04:17:48PM +0100, Takashi Iwai wrote:
> > > > -------------
> > > > Soundblaster Live 512 (PCI):
> > > > -------------
> > > >
> > > > Feb 20 21:54:43 cyan kernel: PCI: Enabling device 0000:01:03.0 (0104 -> 0105)
> > > > Feb 20 21:54:43 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba3f000)!!
> > > > Feb 20 21:54:59 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba21000)!!
> > > > Feb 20 21:54:59 cyan kernel: emu: failure page = 0
> > > > Feb 20 21:54:59 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba21000)!!
> > > > Feb 20 21:54:59 cyan kernel: emu: failure page = 0
> > > > Feb 20 21:55:13 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba21000)!!
> > > > Feb 20 21:55:13 cyan kernel: emu: failure page = 0
> > > > Feb 20 21:55:13 cyan kernel: max memory size is 0x7fffffff (addr = 0x8ba21000)!!
> > > > Feb 20 21:55:13 cyan kernel: emu: failure page = 0
> > > > Feb 20 21:55:13 cyan kernel: max memory size is 0x7fffffff (addr = 0x8baa1000)!!
> > > > Feb 20 21:55:13 cyan kernel: emu: failure page = 0
> > > > Feb 20 21:55:13 cyan kernel: max memory size is 0x7fffffff (addr = 0x8baa1000)!!
> > > > Feb 20 21:55:13 cyan kernel: emu: failure page = 0
> > >
> > > It's not the fault of driver but because of ppc's dma_alloc_coherent().
> > > It doesn't allocate memories in the given coherent_dma_mask.
> >
> > That sounds interesting. Thanks for pointing it out.
>
> Does the patch below have any influence? It's a blind-shot, though...
>
>
> Takashi
>
>
> diff --git a/arch/powerpc/kernel/iommu.c b/arch/powerpc/kernel/iommu.c
> index 946f321..b77caa7 100644
> --- a/arch/powerpc/kernel/iommu.c
> +++ b/arch/powerpc/kernel/iommu.c
> @@ -546,6 +546,7 @@ void *iommu_alloc_coherent(struct iommu_
> return NULL;
>
> /* Alloc enough pages (and possibly more) */
> + again:
> ret = (void *)__get_free_pages(flag, order);
> if (!ret)
> return NULL;
> @@ -556,6 +557,15 @@ void *iommu_alloc_coherent(struct iommu_
> if (mapping == DMA_ERROR_CODE) {
> free_pages((unsigned long)ret, order);
> ret = NULL;
> + } else if (dev->coherent_dma_mask &&
> + mapping >= dev->coherent_dma_mask) {
> + iommu_free(tbl, mapping, npages);
> + free_pages((unsigned long)ret, order);
> + if (! (flag & __GFP_DMA)) {
> + flag |= __GFP_DMA;
> + goto again;
> + }
> + ret = NULL;
> } else
> *dma_handle = mapping;
> return ret;
>
2.6.15 kernels currently won't boot on my machine. I'll get back to you
once I solved that. Thanks a lot so far.
Falko
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2006-02-28 15:41 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-02-20 23:12 trouble on ppc32? Falko Schmidt
2006-02-21 15:17 ` Takashi Iwai
2006-02-22 17:02 ` Falko Schmidt
2006-02-24 18:52 ` Takashi Iwai
2006-02-28 15:41 ` Falko Schmidt
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.