public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Crash with fs corruption on 2.4.23-rc1 + CONFIG_ACPI_PROCESSOR
Date: Mon, 17 Nov 2003 20:51:18 +0100	[thread overview]
Message-ID: <20031117195118.GX32464@poupinou.org> (raw)
In-Reply-To: <20031117102931.B60721-Y6VGUYTwhu0@public.gmane.org>

On Mon, Nov 17, 2003 at 10:31:36AM -0800, Nate Lawson wrote:
> On Mon, 17 Nov 2003, Ducrot Bruno wrote:
> > On Sat, Nov 15, 2003 at 02:48:11PM +0100, Stelian Pop wrote:
> > > On Sat, Nov 15, 2003 at 07:50:20AM +0100, Ducrot Bruno wrote:
> > >
> > > > I think the trouble come from C3, just need to check some values.  If you
> > > > can, it may be usefull that you disable C3, with something like that:
> > > >
> > > > +		acpi_fadt.plvl3_lat = 1234;
> > >
> > > And the patch works, your assumption was correct.
> > >
> > > Now, C3 seem to be reported as supported, 2.6 (correctly) doesn't
> > > promote to it, but 2.4 does. I can't find an obvious reason by reading
> > > the processor.c code (almost identical between 2.4/2.6...)
> >
> > No, 2.6 have some trouble, I guess, because C3 should be promoted.  I guess
> > you are using a USB bridge driver, which need to be rewrotten somehow, because
> > it does a lot of DMA transfers just to check if a device is plugged..
> > That affect all USB driver, but not EHCI IIRC.
> 
> BTW, you were right about USB causing huge numbers of BM events.  Without
> it in my kernel, things are quiet and C3 is used.  I just committed the
> driver (FreeBSD).  Playing mp3s also results in BM activity but that is
> expected.  I plan to add a quiesce method to our USB drivers so that ACPI
> can shut the polling off while idle.
> 

Well, easy to guess: each time C3 is problematic under Linux show that
it's either:
1/ USB bridge (need to be fixed in the usb driver, not acpi related imo),
2/ PIIX4 F-DMA errata deadlock is enabled (that is: C3 have to be disabled).
3/ PIIX4 ide workaround check is enabled.

1/ still need to be fixed.
2/ and 3/ have been fixed by Dominik Brodowski last year.

The trouble for Stelian seems to be different, though (and therefore more
interresting).


-- 
Ducrot Bruno

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.


-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl

      parent reply	other threads:[~2003-11-17 19:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-13 16:18 Crash with fs corruption on 2.4.23-rc1 + CONFIG_ACPI_PROCESSOR Stelian Pop
     [not found] ` <20031113161857.GM26911-sxQ6dllMCJFOpCWnugOeNx8pCrqmY5it@public.gmane.org>
2003-11-14 12:47   ` Ducrot Bruno
     [not found]     ` <20031114124713.GK32464-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-11-14 15:24       ` Stelian Pop
     [not found]         ` <20031114152403.GK29316-sxQ6dllMCJFOpCWnugOeNx8pCrqmY5it@public.gmane.org>
2003-11-15  6:50           ` Ducrot Bruno
     [not found]             ` <20031115065020.GO32464-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-11-15 12:54               ` Stelian Pop
2003-11-15 13:48               ` Stelian Pop
     [not found]                 ` <20031115134811.GA2630-Snhs3Gxj9njPHUqn3ntIkQ@public.gmane.org>
2003-11-17 13:18                   ` Ducrot Bruno
     [not found]                     ` <20031117131800.GQ32464-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-11-17 18:31                       ` Nate Lawson
     [not found]                         ` <20031117102931.B60721-Y6VGUYTwhu0@public.gmane.org>
2003-11-17 19:51                           ` Ducrot Bruno [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=20031117195118.GX32464@poupinou.org \
    --to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=nate-Y6VGUYTwhu0@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