Re: 2.6.20.7 locking up hard on boot

["Marcos Pinto" <markybob@gmail.com>]

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/