mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adam Warner <lists@consulting.net.nz>
To: linux-kernel@vger.kernel.org
Subject: 2.4.22: ymfpci module segfaults
Date: Tue, 26 Aug 2003 16:38:50 +1200	[thread overview]
Message-ID: <pan.2003.08.26.04.38.45.393191@consulting.net.nz> (raw)

Hello LKML,

It is extremely likely that you missed this reported segmentation fault as
the original poster tried to inform the LKML via Google Groups:
<http://groups.google.com/groups?selm=3084ded.0307120145.7977806a%40posting.google.com>

2.4.22 has been a wonderful success--up to the point that my last box to
be upgraded hung when booting. I isolated it to the loading of the ymfpci
module. In a subsequent web search I was fortunate to come across the
above reply.

So I reverted the change:

--- drivers/sound/ymfpci.c.original     2003-08-26 15:41:11.000000000 +1200
+++ drivers/sound/ymfpci.c      2003-08-26 15:52:36.000000000 +1200
@@ -2472,7 +2472,7 @@
        }
 
        eid = ymfpci_codec_read(codec, AC97_EXTENDED_ID);
-       if (eid==0xFFFF) {
+       if (eid==0xFFFFFF) {
                printk(KERN_WARNING "ymfpci: no codec attached ?\n");
                goto out_kfree;
        }


Now I can load the ymfpci, soundcore and ac97_codec modules as before and
sound works fine. The kernel messages are:
ymfpci: YMF724F at 0xda000000 IRQ 19
ac97_codec: AC97 Audio codec, id: 0x8384:0x7605 (SigmaTel STAC9704)

lspci lists the sound card as:
00:09.0 Multimedia audio controller: Yamaha Corporation YMF-724F [DS-1Audio Controller] (rev 03)

I'd suggest Pete Zaitcev's advice is sound for 2.4:
<http://groups.google.com/groups?selm=fa.mdqtrfv.j44t8t%40ifi.uio.no>

"...for 2.4 I just removed the check. Consider that it was not working for
the whole life time of the driver, and not a single soul complained."

Regards,
Adam


                 reply	other threads:[~2003-08-26  4:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pan.2003.08.26.04.38.45.393191@consulting.net.nz \
    --to=lists@consulting.net.nz \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®