From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Sedat Dilek <sedat.dilek@googlemail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, len.brown@intel.com
Subject: Re: [2.6.33-rc2] ACPI problems on HP nc6400 notebook
Date: Thu, 24 Dec 2009 17:22:12 -0800 [thread overview]
Message-ID: <4B3413C4.6070602@gmail.com> (raw)
In-Reply-To: <2d0a357f0912241711o97011od6c1750d7acf8b9e@mail.gmail.com>
On 12/24/09 17:11, Sedat Dilek wrote:
> 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/
>
you can try(if you have the port)
ohci1394_dma=early or the usb
early logging located in kernel hacking.
but if this thing is hitting way early it
might be a bit more tricky.
if you can try a bisect from the bad
kernel to the good.
Justin P. Mattock
next prev parent reply other threads:[~2009-12-25 1:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-25 1:11 Sedat Dilek
2009-12-25 1:22 ` Justin P. Mattock [this message]
2009-12-25 8:48 ` Sedat Dilek
2009-12-25 11:15 ` Sedat Dilek
2009-12-25 12:32 ` Sedat Dilek
2009-12-25 15:28 ` Maciej Rutecki
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=4B3413C4.6070602@gmail.com \
--to=justinmattock@gmail.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sedat.dilek@googlemail.com \
/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®