From: "Marcos Pinto" <markybob@gmail.com>
To: "Adrian Bunk" <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org, "Jan Beulich" <jbeulich@novell.com>,
"Alan Cox" <alan@redhat.com>,
"Bartlomiej Zolnierkiewicz" <bzolnier@gmail.com>,
"Greg Kroah-Hartman" <gregkh@suse.de>,
linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: 2.6.20.7 locking up hard on boot
Date: Fri, 20 Apr 2007 23:30:59 -0500 [thread overview]
Message-ID: <62eb359a0704202130p39cf24efu89dccc8437c30d25@mail.gmail.com> (raw)
In-Reply-To: <20070421013454.GB4016@stusta.de>
Yes, I just tried 2.6.20.3 with ACPI enabled and it booted perfectly.
I'm hoping this means you know what's wrong? :-)
Thanks again,
Marcos
On 4/20/07, Adrian Bunk <bunk@stusta.de> wrote:
> On Fri, Apr 20, 2007 at 07:47:13PM -0500, Marcos Pinto wrote:
> > I'm not subscribed, so please personally CC me any answers/comments.
> > Thank you.
> >
> > While booting, (AMD64 Turion x2) 2.6.20.7 kernel locks up hard. The
> > last kernel that I tried, 2.6.18.8, worked perfectly without any
> > trickery. 2.6.20.7 only boots up with "acpi=off" being added to the
> > kernel line. Note that 2.6.18.8 works perfectly with acpi on, which
> > is really the
> > only way I can run this box because with "acpi=off" it overheats and
> > freezes.
> > Please let me know if there's anything else that I could do to help with
> > this.
> >
> >
> > Here's what's on the screen when it happens:
> >
> > Brought up 2 CPUs
> > testing NMI watchdog ... OK.
> > Disabling vsyscall due to use of PM timer
> > time.c: Using 3.579545 MHz WALL PM GTOD PM timer.
> > time.c: Detected 1808.264 MHz processor.
> > migration_cost=281
> > NET: Registered protocol family 16
> > ACPI: bus type pci registered
> > PCI: Using MMCONFIG at e0000000
> > PCI: No mmconfig possible on device 00:18
> > PCI: No mmconfig possible on device 07:05
> > ACPI: Interpreter enabled
> > ACPI: Using IOAPIC for interrupt routing
> > ACPI: PCI Root Bridge [PCI0] (0000:00)
> > ACPI: Assume root bridge [\_SB_.PCI0] bus is 0
> > 0000:00:0d.0: cannot adjust BAR0 (not I/O)
> > 0000:00:0d.0: cannot adjust BAR1 (not I/O)
> >...
>
> Does 2.6.20.3 boot with ACPI enabled?
>
> cu
> Adrian
>
> --
>
> "Is there not promise of rain?" Ling Tan asked suddenly out
> of the darkness. There had been need of rain for many days.
> "Only a promise," Lao Er said.
> Pearl S. Buck - Dragon Seed
>
>
next prev parent reply other threads:[~2007-04-21 4:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-21 0:47 Marcos Pinto
2007-04-21 1:34 ` Adrian Bunk
2007-04-21 4:30 ` Marcos Pinto [this message]
2007-04-21 5:34 ` Greg KH
2007-04-21 10:36 ` Adrian Bunk
2007-04-21 10:54 ` Marcos Pinto
2007-04-22 2:00 ` Len Brown
2007-04-21 12:44 ` Bartlomiej Zolnierkiewicz
2007-04-23 8:06 ` Jan Beulich
2007-04-23 22:58 ` Marcos Pinto
2007-04-24 19:11 ` Marcos Pinto
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=62eb359a0704202130p39cf24efu89dccc8437c30d25@mail.gmail.com \
--to=markybob@gmail.com \
--cc=alan@redhat.com \
--cc=bunk@stusta.de \
--cc=bzolnier@gmail.com \
--cc=gregkh@suse.de \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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
all inboxes | Powered by JetHome®