DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:cc:content-type;
        b=agIdhjFG8lfkjczXQrXzo/hkQgZvS828Q5nibG2Q3fDoyFBjp4VWulRK0XsaZXGh1L
         ty7FyLay/t4GXxYVC8TyJtUuyW9X6rKavMRPP6aAwGcQJ800E+WLSAIapimYlaFujsCQ
         6GxH6OiEOt8Q1TLK1lQOt3C+1GXj/potdyRp4=
MIME-Version: 1.0
Date: Fri, 25 Dec 2009 02:11:17 +0100
Message-ID: <2d0a357f0912241711o97011od6c1750d7acf8b9e@mail.gmail.com>
Subject: [2.6.33-rc2] ACPI problems on HP nc6400 notebook
From: Sedat Dilek <sedat.dilek@googlemail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: len.brown@intel.com
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 882
Lines: 30

Hi,

I build linux-2.6.33-rc2 on a Debian/sid 32-bit host.
Unfortunately, this kernel falls in an unusable state (sort of loop)
and does not a normal startup.

With this setting (see below), I hoped to catch the early
boot-messages (but, no success):

# cat /etc/default/bootlogd
# Run bootlogd at startup ?
BOOTLOGD_ENABLE=Yes

Finally, I could take a picture [1].
It seems to be that latest ACPI patches are breaking my system (speculating).

Q: How can I log such early boot (error) messages to give a detailled log?

Hope this helps fixing the problem.

Kind Regards,
- Sedat -


[1] http://files.iniza.org/linux-kernel/DSCN2134.JPG
--
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/