* Bug Report: 2.6.38 causes loop / lockup at boot
@ 2011-05-01 0:38 Markus
0 siblings, 0 replies; only message in thread
From: Markus @ 2011-05-01 0:38 UTC (permalink / raw)
To: linux-kernel
Summary: A vanilla net-install of Arch Linux or Debian Testing will result in an unbootable system
Keywords: Kernel, Boot, Lockup, Loop, ACPI
Kernel Version: 2.6.38.2 to .4
Environment: An old laptop (Gericom Overdose T2, around 2001) with a SiS 630 board, Pentium 3 1.26GHz, ACPI 1.0B compliant
Description:
After a fresh net-install of Arch Linux (i686), when the system is booted from harddisk for the first time, it will loop these messages over and over, effectively making the system unusable. The messages never make it into a log (and because they run by very fast, this is all I could glean). Happens with both kernels 2.6.38.2 and 2.6.38.3:
[<c11ec???>] ? acpi_add_single_object
[<c11ec???>] ? acpi_device_suspend
For 2.6.38.4, the messages change slightly:
[<c11ec???>] ? acpi_add_single_object
[<c11ed???>] ? unregister_acpi_bus_type
Something similar happens after installing Debian Stable (i386 LXDE) and updating to Testing, except that the messages don't loop, but there's only about 10 of them before the system freezes up completely.
Fedora 15 beta with 2.6.38 booted fine.
------------------------------------
Hope this is the right address. Feel free to contact me, but I'm a relative noob.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2011-05-01 0:38 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-05-01 0:38 Bug Report: 2.6.38 causes loop / lockup at boot Markus
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.