From: Danny ter Haar <dth@dth.net>
To: Len Brown <lenb@kernel.org>
Cc: Gabriel C <nix.or.die@googlemail.com>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: Update: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not:
Date: Tue, 31 Jul 2007 03:10:05 +0200 [thread overview]
Message-ID: <20070731011005.GA22245@dth.net> (raw)
In-Reply-To: <200707301330.54640.lenb@kernel.org>
Quoting Len Brown (lenb@kernel.org):
> Please attach the output from acpidump to
> http://bugzilla.kernel.org/show_bug.cgi?id=7880
done
also on : http://www.dth.net/kernel/acpidump_output_via_c3_5000
> We'll likely be able to tell from it if that patch
> has any real effect on your system, or if you test
> result was from some unrelated event.
Reverting the patch didn't make a real difference, it only took
longer (eg 16 minutes before lockup in stead of 2-3 minutes)
> Also, please test with CONFIG_X86_ACPI_CPUFREQ=n
> to remove the acpi-cpufreq driver (and thus this patch)
> from your kernel. If it still fails, then we know
> that this driver (and this patch) are not related
> to the failure.
Will do.
This machine(firewall) is solar powered so i tried to let it
consume as less power as possible
This is in my startup script at the moment:
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
> Hmmm, okay, the "big hammer" works. Please see
> if any of these smaller hammers work:
>
> pnpacpi=off
> acpi=noirq
> notsc
More testing to do, however, sunday i'm going abroad for a while,
all stuff will be in storage. If i cant find in the next few days
(packing everything in moving boxes) it might take a while before
i can test again. Sorry for that.
Danny
--
next prev parent reply other threads:[~2007-07-31 1:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 19:38 ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not dth
2007-07-28 23:42 ` Bartlomiej Zolnierkiewicz
2007-07-29 0:30 ` Danny ter Haar
2007-07-29 1:23 ` Danny ter Haar
2007-07-29 2:48 ` Gabriel C
2007-07-29 3:30 ` Danny ter Haar
2007-07-29 3:54 ` Gabriel C
2007-07-30 2:54 ` Update: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not: Danny ter Haar
2007-07-30 17:30 ` Len Brown
2007-07-31 1:10 ` Danny ter Haar [this message]
2007-07-31 4:00 ` Danny ter Haar
2007-07-31 14:30 ` Danny ter Haar
2007-08-01 0:44 ` Danny ter Haar
2007-08-01 20:03 ` Update: ACPI problems: 2.6.22-git17 working, 2.6.23-rc1* is not: (was ide not working) Danny ter Haar
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=20070731011005.GA22245@dth.net \
--to=dth@dth.net \
--cc=bzolnier@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nix.or.die@googlemail.com \
/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.