From: gmate.amit@gmail.com (Kumar amit mehta)
To: kernelnewbies@lists.kernelnewbies.org
Subject: kernel build error
Date: Mon, 1 Apr 2013 23:19:51 -0700 [thread overview]
Message-ID: <20130402061951.GA3353@gmail.com> (raw)
In-Reply-To: <CAGdaada1MaVvpLvGRLLGUA7Xc2a-6ChXKNZcDtEWxE7igai9mg@mail.gmail.com>
On Tue, Apr 02, 2013 at 10:04:31AM +0700, Mulyadi Santosa wrote:
> Could you paste roughly 20-30 lines of boot messages when you hit the hung
> point? Kernel config alone usually can't help much
I'm trying this on a Virtual Machine using VMware Player. When the VM boots up,
it throws lots of messages on the console and then gets stuck. I'd like to know,
how I can capture all those console logs till it hits the hung point.
-Amit
next prev parent reply other threads:[~2013-04-02 6:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-17 15:28 kernel build error Kumar amit mehta
2013-03-18 4:21 ` Mulyadi Santosa
2013-03-19 5:28 ` Kumar amit mehta
2013-03-19 14:43 ` Mulyadi Santosa
2013-03-20 6:56 ` Kumar amit mehta
2013-03-20 7:07 ` Kumar amit mehta
2013-03-20 9:48 ` Ben Wu
2013-03-20 9:49 ` wake_lock in linux kernel Ben Wu
2013-03-21 4:34 ` Yuva Raj
2013-03-20 17:32 ` kernel build error Valdis.Kletnieks at vt.edu
2013-03-21 6:16 ` Kumar amit mehta
2013-03-22 3:41 ` Mulyadi Santosa
2013-03-22 10:17 ` Kumar amit mehta
2013-03-24 5:49 ` Mulyadi Santosa
2013-03-25 5:04 ` Kumar amit mehta
2013-03-25 7:36 ` Mulyadi Santosa
[not found] ` <20130331044544.GA3291@gmail.com>
2013-04-02 3:04 ` Mulyadi Santosa
2013-04-02 6:19 ` Kumar amit mehta [this message]
2013-04-02 13:40 ` Mulyadi Santosa
-- strict thread matches above, loose matches on Subject: below --
2019-08-22 12:27 Kernel " James David Lyons
2016-04-26 6:30 Kernel Build error Harinath maddelal
2016-04-26 6:43 ` Khem Raj
2016-04-26 7:10 ` Harinath maddelal
2016-04-26 14:17 ` Khem Raj
2005-05-12 22:30 Kernel build error mcnernbm
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=20130402061951.GA3353@gmail.com \
--to=gmate.amit@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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 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.