From: Dominik Brodowski <linux@brodo.de>
To: Alessandro Suardi <ALESSANDRO.SUARDI@oracle.com>
Cc: andrew.grover@intel.com, linux-kernel@vger.kernel.org
Subject: Re: Kernel 2.5.55 failed to boot with ACPI support
Date: Mon, 13 Jan 2003 00:08:46 +0100 [thread overview]
Message-ID: <20030112230846.GA5692@brodo.de> (raw)
In-Reply-To: <5028.1042412642@www10.gmx.net>
On Mon, Jan 13, 2003 at 12:04:02AM +0100, Alessandro Suardi wrote:
> Andrew Grover wrote:
>
> > > From: Ole J. Hagen [mailto:olehag_2001@yahoo.no]
> > > I just wanted to inform that kernel-2.5.55 failes to boot
> > > when ACPI support is
> > > compiled in the kernel.
> > >
> > > I have following configuration; Dell Optiplex GX-240, Pentium
> > > 4 (1.5 GHz), ATI RAGE 128.
> >
> > How exactly does it fail?
>
> My brand new Dell Latitude C640 oopses on boot in 2.5.56 if I
> have CPU_FREQ config'd in. ACPI without CPU_FREQ is okay - well,
> it screws my framebuffer screen (what 2.4.21-pre3 doesn't) when
> the ACPI code does its bootup printk's, but after that the
> screen recovers.
>
> ...
>
> Back on topic, if you're interested I can rebuild my 2.5.56 with
> CPU_FREQ and write down the backtrace of the oops.
Would be great if you could do that - and tell what oops it is (NULL pointer
dereference etc.), in case you still see that on your screen.
Dominik
next prev parent reply other threads:[~2003-01-12 22:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-12 22:48 Kernel 2.5.55 failed to boot with ACPI support Alessandro Suardi
[not found] ` <5028.1042412642@www10.gmx.net>
2003-01-12 23:08 ` Dominik Brodowski [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-13 0:51 Alessandro Suardi
2003-01-13 15:11 ` Dominik Brodowski
2003-01-10 21:10 Grover, Andrew
2003-01-11 2:07 ` Ole J. Hagen
2003-01-10 19:42 rotation James Simmons
2003-01-10 21:10 ` Kernel 2.5.55 failed to boot with ACPI support Ole J. Hagen
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=20030112230846.GA5692@brodo.de \
--to=linux@brodo.de \
--cc=ALESSANDRO.SUARDI@oracle.com \
--cc=andrew.grover@intel.com \
--cc=linux-kernel@vger.kernel.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 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.