public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jesse@phiwumbda.org (Jesse F. Hughes)
To: linux-kernel@vger.kernel.org
Subject: Update: Semaphore errors w/intel8x0, but NOT due to ACPI
Date: Fri, 27 Feb 2004 22:51:53 +0100	[thread overview]
Message-ID: <87hdxckx6u.fsf@phiwumbda.org> (raw)
In-Reply-To: <87u11eam7c.fsf@phiwumbda.org> (Jesse F. Hughes's message of "Wed, 25 Feb 2004 22:22:31 +0100")


I recompiled my 2.6.3 kernel without any ACPI support but with APM
support (as a module) to see if, as Jaroslav suggested, the semaphore
errors I get are due to ACPI.  I'm afraid they aren't.  After some
hours of the laptop being on, but the soundcard unused, I tried to
play a sound.  Nothing came out.  The usual semaphore errors were in
the syslog.

Please help.  I'm at wit's end with this bug, which has been with me
since November.

I have appended part of my previous post for diagnosis.  

jesse@phiwumbda.org (Jesse F. Hughes) writes:

> Hey ho.
>
> I have been having problems with my intel8x0 soundcard on my NEC Versa
> P520 laptop for some time now, and I think that the problems began
> when I upgraded the BIOS for this thing.  (I also upgraded from
> Slackware 9.0 to 9.1 around the same time, but I think that's
> irrelevant.)
>
> Every so often, when I boot, I get the following error message.
>
> syslog.1:Feb 16 15:32:52 euclid kernel: ALSA /usr/src/sound/alsa-driver-1.0.2c/pci/intel8x0.c:1969: AC'97 warm reset still in progress? [0x6]
>
> Most of the time, the card is fine on bootup, but at some time, the
> card sputters a bit and then just gives up, with the following error.
>
> Feb 25 17:19:50 euclid kernel: ALSA sound/pci/intel8x0.c:591: codec_write 0: semaphore is not ready for register 0x2c
> Feb 25 17:19:50 euclid kernel: ALSA sound/pci/intel8x0.c:607: codec_read 0: semaphore is not ready for register 0x2c
>
> In both cases, I can't get the card to work without a reboot.

[...]


-- 
Jesse F. Hughes
"[I]t's the damndest thing.  There's something wrong with every last
one of you, and I *never* thought that was a possibility.  But now I
feel it's the only reasonable conclusion." --JSH sees some sorta light

      reply	other threads:[~2004-02-27 21:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-25 21:22 ACPI and semaphore headaches with intel8x0 soundcard Jesse F. Hughes
2004-02-27 21:51 ` Jesse F. Hughes [this message]

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=87hdxckx6u.fsf@phiwumbda.org \
    --to=jesse@phiwumbda.org \
    --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