From: Rudy Zijlstra <rudy@grumpydevil.homelinux.org>
To: lrhorer@satx.rr.com
Cc: 'Linux RAID' <linux-raid@vger.kernel.org>
Subject: Re: Kernel 2.6.32-5-amd64 fails to boot.
Date: Tue, 01 Feb 2011 22:02:10 +0100 [thread overview]
Message-ID: <4D4874D2.601@grumpydevil.homelinux.org> (raw)
In-Reply-To: <1D.26.13137.882784D4@cdptpa-omtalb.mail.rr.com>
On 02/01/2011 09:52 PM, Leslie Rhorer wrote:
>> On 02/01/2011 09:23 PM, Leslie Rhorer wrote:
>>
>>
>>> doesn't boot, either. It gives a bit more detail in the output, but
>>>
>> nothing
>>
>>> illuminating. The old kernel (2.6.32-3-amd64) boots just fine.
>>>
>>>
>> Can you enable serial console and catch the console output that way?
>>
> Well, not easily. I don't have a serial terminal. I suppose I
> could set something up. You're suggesting I poke around to see what md is
> reporting? Also, I'm not sure why - if the keyboard console is failing -
> the serial console would work better.
>
>
>
Serial console can be captured to a file and then the output analysed.
So you can read afterwards the messages that are flying past.
What i do in such case, is that i take serial connector from a laptop,
and run a terminal emulater like minicom. And capture it to a file so i
can analyse what has been happening.
next prev parent reply other threads:[~2011-02-01 21:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 20:23 Kernel 2.6.32-5-amd64 fails to boot Leslie Rhorer
2011-02-01 20:43 ` Rudy Zijlstra
2011-02-01 20:52 ` Leslie Rhorer
2011-02-01 21:02 ` Rudy Zijlstra [this message]
2011-02-01 21:44 ` Leslie Rhorer
2011-02-01 22:46 ` Rudy Zijlstra
2011-02-02 7:00 ` Leslie Rhorer
2011-02-02 11:00 ` Justin Piszcz
2011-02-02 11:32 ` CoolCold
2011-02-02 17:00 ` Leslie Rhorer
2011-02-02 20:20 ` Leslie Rhorer
2011-02-03 3:27 ` Leslie Rhorer
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=4D4874D2.601@grumpydevil.homelinux.org \
--to=rudy@grumpydevil.homelinux.org \
--cc=linux-raid@vger.kernel.org \
--cc=lrhorer@satx.rr.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 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.