From: Thomas Gleixner <tglx@linutronix.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Sam Ruby <rubys@intertwingly.net>,
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: Tue, 3 Feb 2009 22:03:25 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.0902032152180.22800@localhost.localdomain> (raw)
In-Reply-To: <20090203114849.b661f1ce.akpm@linux-foundation.org>
On Tue, 3 Feb 2009, Andrew Morton wrote:
> > >> [ 0.296001] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
> > >> [ 0.296001] Kernel panic - not syncing: IO-APIC + timer doesn't work!
Sigh.
> Not sure. Perhaps platform_i386/platform_x86_64 would be correct.
> Can the x86 maintainers please advise?
Yup. That's correct
@Sam: I just checked, that your machine has a serial port. That's a
good start :)
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.
Thanks,
tglx
next prev parent reply other threads:[~2009-02-03 21:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4978767D.4060700@intertwingly.net>
2009-01-30 8:07 ` [APIC] Kernel panic, rsync corruption, intel q8200, 2.6.28-rc8 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 [this message]
2009-02-04 3:28 ` Sam Ruby
2009-02-04 4:42 ` Len Brown
2009-02-09 23:50 ` Sam Ruby
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=alpine.LFD.2.00.0902032152180.22800@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=rubys@intertwingly.net \
--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