linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Wed, 1 Aug 2007 02:44:23 +0200	[thread overview]
Message-ID: <20070801004423.GA16572@dth.net> (raw)
In-Reply-To: <200707301330.54640.lenb@kernel.org>

Quoting Len Brown (lenb@kernel.org):
> 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.

It wasn't enabled in any of the kernels i ran:

# grep X86_ACPI ../configs/config*
../configs/config-2.6.22-git14-c3-via5000-firewall:# CONFIG_X86_ACPI_CPUFREQ is not set
../configs/config-2.6.22-git17-c3-via5000-firewall:# CONFIG_X86_ACPI_CPUFREQ is not set
../configs/config-2.6.23-rc1-git5:# CONFIG_X86_ACPI_CPUFREQ is not set
../configs/config-2.6.23-rc1-git6:# CONFIG_X86_ACPI_CPUFREQ is not set
../configs/config-2.6.23-rc1-git9:# CONFIG_X86_ACPI_CPUFREQ is not set
../configs/config-2.6.23-rc1-mm1-c3-firewall:# CONFIG_X86_ACPI_CPUFREQ is not set

> Hmmm, okay, the "big hammer" works.  Please see
> if any of these smaller hammers work:
> 
> pnpacpi=off
> acpi=noirq
> notsc

_none_ of these options will work. The machine locks up solid.
And that's what i'm the most surprised about. The last time i withnessed
a solid kernel lockup without any panic/notification is _years_ ago.

I also tried a kernel without "CPU Frequency scaling", so it is not the
scaling up/down in Mhz of the cpu.
I've even just compiled/run a kernel with libata and even that one still 
locks up.

New round of git bisects i guess (this time powercycle instead of reboot
and wait few hours before ginving it "bisect good" )

Will report back.

Danny

-- 

  parent reply	other threads:[~2007-08-01  0:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070727193832.GA20289@dth.net>
     [not found] ` <200707290142.53689.bzolnier@gmail.com>
     [not found]   ` <20070729012324.GA29723@dth.net>
     [not found]     ` <46ABFFE4.3060703@googlemail.com>
     [not found]       ` <20070729033030.GA24636@dth.net>
2007-07-29  3:54         ` ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not 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
2007-07-31  4:00               ` Danny ter Haar
2007-07-31 14:30               ` Danny ter Haar
2007-08-01  0:44               ` Danny ter Haar [this message]
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=20070801004423.GA16572@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).