snd-ymfpci fails to load at boot, works fine later

Bug #51281 reported by Sebastian Dröge
10
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.17 (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: linux-source-2.6.17

Hi,
currently the snd-ymfpci module fails to load with an
0000:00:0e.0 Multimedia audio controller: Yamaha Corporation YMF-744B [DS-1S Audio Controller] (rev 02)
at boot or better it fails to work with the card is the module is loaded but the soundcard simply not available.
The (IMHO) relevant output is:
[17179587.224000] PCI: Enabling device 0000:00:0e.0 (0004 -> 0007)
[17179587.224000] ACPI: PCI Interrupt 0000:00:0e.0[A] -> GSI 17 (level, low) -> IRQ 201
[17179588.204000] NET: Registered protocol family 17
[17179588.244000] PCI: Enabling device 0000:00:11.5 (0000 -> 0001)
[17179588.244000] ACPI: PCI Interrupt 0000:00:11.5[C] -> GSI 22 (level, low) -> IRQ 193
[17179588.244000] PCI: Setting latency timer of device 0000:00:11.5 to 64
[17179588.756000] codec_read: codec 0 is not valid [0xfe0000]
[17179588.764000] codec_read: codec 0 is not valid [0xfe0000]
[17179588.768000] codec_read: codec 0 is not valid [0xfe0000]
[17179588.776000] codec_read: codec 0 is not valid [0xfe0000]

When rmmod'ing and reloading the module by hand later it works fine and only this is printed to the kernel log:
[17179628.772000] ACPI: PCI Interrupt 0000:00:0e.0[A] -> GSI 17 (level, low) -> IRQ 201

Bye

Revision history for this message
Sebastian Dröge (slomo) wrote :

Oh, maybe I should note that this is on latest edgy with 2.6.17-3.4

Revision history for this message
Sebastian Dröge (slomo) wrote :

this was fixed with -5

Changed in linux-source-2.6.17:
status: Unconfirmed → Fix Released
Revision history for this message
Sebastian Dröge (slomo) wrote :

Ok, the bug re-appeared with the same kernel version... so I think it is most probably some kind of timing problem somewhere...

Changed in linux-source-2.6.17:
status: Fix Released → Unconfirmed
Daniel T Chen (crimsun)
Changed in linux-source-2.6.17:
importance: Untriaged → Low
status: Unconfirmed → In Progress
Revision history for this message
Sergio Zanchetta (primes2h) wrote :

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task.

Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . You should be able to test your bug using the LiveCD. Please let us know your results. Thanks.

Changed in linux-source-2.6.17:
status: In Progress → Invalid
Changed in linux:
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".

Thanks,

Changed in linux:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.