From: Ivan Gyurdiev <ivg2-HmMyXyqgL2CVc3sceRu5cw@public.gmane.org>
To: hgfelger-9nAOAgdJVo4b1SvskN2V4Q@public.gmane.org,
liste-9nAOAgdJVo4b1SvskN2V4Q@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: 2.5.75 - ACPI and sound lockups
Date: Sun, 13 Jul 2003 06:02:49 -0400 [thread overview]
Message-ID: <200307130602.49710.ivg2@cornell.edu> (raw)
In-Reply-To: <Pine.LNX.4.33.0307131238520.561-100000-KnfdeQs3A3X/9pzu0YdTqQ@public.gmane.org>
On Sunday 13 July 2003 06:43, liste-9nAOAgdJVo4b1SvskN2V4Q@public.gmane.org wrote:
> Salut Ivan,
salut
> my first look says, that IRQ 3,7,10 and 11 (which is the one, that bit
> you, I think) has to be level and not edge.
> As irq 11 is shared, this is no good!
>
> May you please get the information you provided for 2.5.74 for the
> 2.4-kernel you mentioned, too (including ACPI-version from
> /proc/acpi/info)?
You mean the 2.4 kernels, which I mentioned work fine?
Every 2.4 kernel I've tried with ACPI works ok (that's the 2.4 in-kernel code,
no patches). Should I try the latest 2.4 kernel?
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps1
next prev parent reply other threads:[~2003-07-13 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-13 3:06 2.5.75 - ACPI and sound lockups Ivan Gyurdiev
[not found] ` <200307122306.14036.ivg2-HmMyXyqgL2CVc3sceRu5cw@public.gmane.org>
2003-07-13 10:43 ` liste-9nAOAgdJVo4b1SvskN2V4Q
[not found] ` <Pine.LNX.4.33.0307131238520.561-100000-KnfdeQs3A3X/9pzu0YdTqQ@public.gmane.org>
2003-07-13 10:02 ` Ivan Gyurdiev [this message]
2003-07-13 17:09 ` Ivan Gyurdiev
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=200307130602.49710.ivg2@cornell.edu \
--to=ivg2-hmmyxyqgl2cvc3sceru5cw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=hgfelger-9nAOAgdJVo4b1SvskN2V4Q@public.gmane.org \
--cc=liste-9nAOAgdJVo4b1SvskN2V4Q@public.gmane.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