From: Eric Sharkey <sharkey@netrics.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: problem with ALSA on AMD64 w/VIA chipset
Date: Mon, 22 Nov 2004 13:26:38 -0500 [thread overview]
Message-ID: <E1CWIta-0001s1-00@mastermind.netrics.internal> (raw)
In-Reply-To: Your message of "Mon, 22 Nov 2004 18:17:19 +0100." <s5hu0rhvm5c.wl@alsa2.suse.de>
> > This happens with both 64 and 32 bit kernels, and no amount of
> > twiddling with kernel parameters (ACPI/CPU frequency scaling, apic,
> > preemption, etc.) seems to make any difference.
>
> Hmm, I just thought of cpurfreq, but your report sounds that it's not
> the case. Could you unload powernow-k8 module just to be sure?
I've spent a good deal of time trying to track this down over the
last couple of months. I've compiled and booted under more configurations
than I care to count. I'm absolutely certain that with a kernel
with no power management support at all, and all power management turned
off in the bios, the problem still persists.
> I think you'd better to ask this on LKML, since the symptom looks like
> the kernel core problem.
Hmm. Ok.
If there's something you can think of that I could do to gather more
information to help diagnose the problem, please let me know.
Thanks,
Eric
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
prev parent reply other threads:[~2004-11-22 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 15:30 problem with ALSA on AMD64 w/VIA chipset Eric Sharkey
2004-11-22 17:17 ` Takashi Iwai
2004-11-22 18:26 ` Eric Sharkey [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=E1CWIta-0001s1-00@mastermind.netrics.internal \
--to=sharkey@netrics.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.