mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Markus <progrox@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: Bug Report: 2.6.38 causes loop / lockup at boot
Date: Sun, 01 May 2011 02:38:32 +0200	[thread overview]
Message-ID: <op.vur1eiisl0p1sd@altair.fritz.box> (raw)

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.

                 reply	other threads:[~2011-05-01  0:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=op.vur1eiisl0p1sd@altair.fritz.box \
    --to=progrox@gmx.net \
    --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 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®