From: Sam Ruby <rubys@intertwingly.net>
To: Len Brown <lenb@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org, x86@kernel.org,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: [APIC] Kernel panic, rsync corruption, intel q8200, 2.6.28-rc8
Date: Mon, 09 Feb 2009 18:50:35 -0500 [thread overview]
Message-ID: <4990C14B.7060802@intertwingly.net> (raw)
In-Reply-To: <alpine.LFD.2.00.0902032336000.5607@localhost.localdomain>
Len Brown wrote:
>>> Do you have a second computer around with a serial port ? If yes, then
>>> please add the following to the kernel command line:
>>>
>>> earlyprintk=serial,ttyS0,115200 apic=debug
>>>
>>> and connect the serial ports with a null modem cable. Fire up a
>>> terminal program on the second machine and capture the output.
>> I do have a second computer, and went out and bought a null modem adapter for
>> my serial cable and connected the two machines. I've tried installing minicom
>> and also connecting it to ttyS0 at 115200 baud on the second machine, but when
>> I boot the first machine I don't see any output on the terminal.
>
> /boot/grub/menu.lst:
>
> serial --unit=0 --speed=115200 --word=8 --parity=no --stop=1
> terminal --timeout=300 serial console
>
> is what I use.
>
> this will give you a prompt from grub even before the kernel boots
> so you can select (and edit) your kernel via menu over the serial line
> if you wish.
I've got that working now. I used minicom on the remote machine,
capturing the output. You can see me fumbling around, editing the
kernel command and booting here:
http://intertwingly.net/stories/2009/02/09/minicom.out
While it is difficult to make out what I did given line wrapping, etc,
what I started with was:
/boot/vmlinuz-2.6.27-11-generic
root=UUID=4fce230e-fe72-4685-aab0-294ef1c20efa ro noapic quiet splash
After editing, what I had was
/boot/vmlinuz-2.6.27-11-generic
root=UUID=4fce230e-fe72-4685-aab0-294ef1c20efa ro quiet splash
earlyprintk=serial,ttyS0,115200 apic=debug
As you can see, the last line I saw was "Starting up ...", after which
point the "MP-BIOS bug: 8254 timer not connected to IO-APIC" etc output
appeared on the monitor that is directly connected to the machine being
booted (i.e., this text did not appear on the minicom session).
> If this doesn't work, then the kernel earlyprintk is unlikely to work
> also.
At the moment, it looks like it works, but earlyprintk does not work for
me, at least not on Ubuntu 8.10, kernel 2.6.27-11-generic.
> Note that there may be some BIOS SETUP options related to the serial port
> -- worth checking.
>
> Also, in minicom, be sure to turn off HW flow control
>
> there is a fancy serial console document someplace on this,
> probably at http://tldp.org/
As I have managed to get grub to talk to the serial console, I did not
explore these options further. Please let me know if there is something
in particular I should explore.
> good luck,
> -Len
- Sam Ruby
next prev parent reply other threads:[~2009-02-09 23:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 13:37 [APIC] Kernel panic, rsync corruption, intel q8200, 2.6.28-rc8 Sam Ruby
2009-01-30 8:07 ` Andrew Morton
2009-02-03 17:55 ` Sam Ruby
2009-02-03 17:58 ` Sam Ruby
2009-02-03 19:48 ` Andrew Morton
2009-02-03 20:19 ` Sam Ruby
2009-02-03 21:03 ` Thomas Gleixner
2009-02-04 3:28 ` Sam Ruby
2009-02-04 4:42 ` Len Brown
2009-02-09 23:50 ` Sam Ruby [this message]
2009-02-10 2:10 ` yakui_zhao
2009-02-10 11:46 ` Sam Ruby
2009-02-11 1:42 ` yakui_zhao
2009-02-11 2:06 ` Sam Ruby
2009-02-11 19:26 ` Sam Ruby
2009-02-04 4:35 ` Len Brown
2009-02-09 21:31 ` Maciej W. Rozycki
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=4990C14B.7060802@intertwingly.net \
--to=rubys@intertwingly.net \
--cc=akpm@linux-foundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=tglx@linutronix.de \
--cc=x86@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