Re: [ALSA] 2.6.21 loading of module snd_ymfpci takes 2 minutes

At Thu, 26 Apr 2007 12:12:48 +0200,
Santiago Garcia Mantinan wrote:

I have just upgraded from 2.6.20 to 2.6.21, when I rebooted I thought the
computer had halted after loading snd_ymfpci, but what happens is that it
takes 2 minutes (120 seconds mesured with time) for the driver to load, but
then works as expected.

After making a diff between the 2.6.20 and 2.6.21 versions of the ymfpci
driver I decided to replace the ymfpci_main.c from 2.6.21 with the one from
2.6.20, it compiled with a few warnings and then worked ok, like it used to
work, without the two minutes delay.

It's because the recent ymfpci driver tries to request_firmware() at
first. And since no files are found, it just waits for certain time.
A workaround is to install the firmware files from alsa-firmware
1.0.14rc* package.

I'll fix the codes on 2.6.22 not to make external firmwares
mandatory via Kconfig option.


Takashi

These are the messages I get from the kernel when I load the driver:
PCI: Enabling device 0000:00:0a.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:00:0a.0[A] -> Link [LNKD] -> GSI 9 (level, low) -> IRQ 9

This is the info I got for the sound card, which is integrated on the
motherboard:

Card: Yamaha DS-1L (YMF740C)
Chip: Asahi Kasei AK4543

lspci:
00:0a.0 0401: 1073:000c (rev 03)
Subsystem: 1033:804b
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR+
Latency: 64 (1250ns min, 6250ns max)
Interrupt: pin A routed to IRQ 9
Region 0: Memory at e8108000 (32-bit, non-prefetchable) [size=32K]
Capabilities: <access denied>

/proc/asound/cards:
0 [YMF740C ]: YMF740C - Yamaha DS-1L (YMF740C)
Yamaha DS-1L (YMF740C) at 0xe8108000, irq 9

Hope that helps to diagnose the problem, if you need any other info don't
hesitate to contact me.

Regards...
--
Santiago García Mantiñán
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: [PATCH] RTC: Add mmap method to rtc character driver
    ... driver was there, and its infrastructure lent itself rather easily toward adding ... open that driver and send it a UIE or PIE ioctl, it will start ticking ... More majordomo info at http://vger.kernel.org/majordomo-info.html ... Please read the FAQ at http://www.tux.org/lkml/ ...
    (Linux-Kernel)
  • Re: Net: e1000 driver: TX Hang message
    ... It receives packets but keeps on giving "Tx hang" ... > the same piece of code is in the 2.6.13.2 kernel's e1000 driver. ... > More majordomo info at http://vger.kernel.org/majordomo-info.html ... > Please read the FAQ at http://www.tux.org/lkml/ ...
    (Linux-Kernel)
  • Re: MODULE_LICENSE usage
    ... GPL, so that others are free to distribute and modify the driver. ... After asking the FSF for advice and working through their FAQ, ... More majordomo info at http://vger.kernel.org/majordomo-info.html ...
    (Linux-Kernel)
  • Re: [RFC PATCH] move drm to pci_request_irq
    ... Actually, this is the exit path, I felt like it could be safer if it was ... should probably be done in each driver. ... More majordomo info at http://vger.kernel.org/majordomo-info.html ... Please read the FAQ at http://www.tux.org/lkml/ ...
    (Linux-Kernel)
  • zd1211b question.
    ... the building of that driver. ... Am I blind, don't know how to run grep, or does the xconfig script need more ... Thus spake the master programmer: ... More majordomo info at http://vger.kernel.org/majordomo-info.html ...
    (Linux-Kernel)