LKML Archive on
help / color / mirror / Atom feed
From: Robert Fendt <>
Cc: Len Brown <>
Subject: Re: peculiar problem with 2.6, 8139too + ACPI
Date: Thu, 27 May 2004 15:45:09 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <1085102192.12349.508.camel@dhcppc4>

On 20 May 2004 21:16:32 -0400
Len Brown <> wrote:

> Please verify that the problem goes away when you exclude the
> acpi/processor module (CONFIG_ACPI_PROCESSOR) from the system.
> With the recent spate of C3 issues, we should make an easier way to
> disable C3 until it is fixed...

Sorry for the delay, but I could not do further tests before now. I have
now at least managed to get 2.6.6 to boot on the box (although it breaks
the synaptics mouse pad driver, but that's a different matter; this too
seems to be ACPI-related, though). The boot problem was the new cpufreq
detection mode producing a seg'fault during boot (and guess what: ACPI

So far I can confirm the following: 1) the problem still exists in 2.6.6
and 2) the problem can be switched on and off be (un)loading the
'processor' module. Test environment is still Debian-unstable, this time
with 2.6.6 vanilla kernel in Debian distro config (a.k.a. pretty bloated
but most things as modules).

I do not expect different results when disabling processor support
during kernel compile. Of course I can try this, if wanted. Any patch
suggestions to try out so far?


  reply	other threads:[~2004-05-27 13:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2004-05-15  1:36 ` Len Brown
2004-05-15 23:30   ` Robert Fendt
2004-05-17 10:30   ` Robert Fendt
2004-05-17 18:24     ` Len Brown
2004-05-17 19:10       ` Jeff Garzik
2004-05-20 23:53       ` Robert Fendt
2004-05-21  1:16         ` Len Brown
2004-05-27 13:45           ` Robert Fendt [this message]
2004-05-14 13:28 Robert Fendt

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: peculiar problem with 2.6, 8139too + ACPI' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).