public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: Stelian Pop <stelian.pop-A5NNTvo2L0pl57MIdRCFDg@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Crash with fs corruption on 2.4.23-rc1 + CONFIG_ACPI_PROCESSOR
Date: Fri, 14 Nov 2003 13:47:13 +0100	[thread overview]
Message-ID: <20031114124713.GK32464@poupinou.org> (raw)
In-Reply-To: <20031113161857.GM26911-sxQ6dllMCJFOpCWnugOeNx8pCrqmY5it@public.gmane.org>

On Thu, Nov 13, 2003 at 05:18:57PM +0100, Stelian Pop wrote:
> Hi,
> 
> Something is going very strange on my Transmeta powered Vaio C1VE laptop.
> This is with a RedHat Fedora core 1 installation, kernel compiled 
> with gcc 3.2.3.
> 
> If I compile a recent kernel (tried 2.4.23-rc1, and plain stock 2.4.22)
> with CONFIG_ACPI_PROCESSOR enabled, I get a bunch of oopses in the
> next 10-30 seconds.
> 
> When compiled statically into the kernel, the init scripts are 
> succesfuly ran, I can log in then I get an oops in the next 10 to 
> 30 seconds. Most often the oops is a BUG at page_alloc.c:188,
> but not always.
> 
> When compiled as a module, all goes well if the module is not loaded,
> and the crash happens moments after the loading of processor.o
> 
> After the oops, the / filesystem (ext3) gets corrupted and a manual
> fsck is required to solve some block duplication errors.
> 
> A 2.6.0-test9 compiled with CONFIG_ACPI_PROCESSOR on does not seem
> to have this problem.
> 
> Attached you'll find the .config and dmesg in case it is useful...
> 

Have you a decoded oops?

-- 
Ducrot Bruno

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


-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/

  parent reply	other threads:[~2003-11-14 12:47 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 [this message]
     [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

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=20031114124713.GK32464@poupinou.org \
    --to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=stelian.pop-A5NNTvo2L0pl57MIdRCFDg@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