From: Sam Ruby <rubys@intertwingly.net>
To: linux-kernel@vger.kernel.org
Subject: [APIC] Kernel panic, rsync corruption, intel q8200, 2.6.28-rc8
Date: Thu, 22 Jan 2009 08:37:01 -0500 [thread overview]
Message-ID: <4978767D.4060700@intertwingly.net> (raw)
Hardware summary: http://tinyurl.com/ap79ra
APIC details: http://intertwingly.net/stories/2009/01/22/
Note acpidump.err: Wrong checksum for OEMB!
Messages on boot using Intrepid, Jaunty Alpha 3, or Fedora 10:
[ 0.296001] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
[ 0.296001] Kernel panic - not syncing: IO-APIC + timer doesn't work!
Boot with apic=debug and send a report. Then try booting with the
'noapic' option.
[ 0.296001]
Able to get past this issue using "noapic", at which point things mostly
work, but rsync of large iso images result in corrupt files. Able to
copy those same files using Vista on the same machine, or using Hardy on
another machine. This problem may not be related to the above, but it
seems plausible to me that this might be an interrupt issue.
memtest86+ runs clean.
Quite willing to invest time in installing kernels or distributions on
fresh hard drives, run tests, obtain debug information, and report back.
More background here: http://intertwingly.net/blog/2009/01/20/noAPIC
Not subscribed, but will actively monitor the web archives for this
mailing list for the next several days.
- Sam Ruby
next reply other threads:[~2009-01-22 13:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 13:37 Sam Ruby [this message]
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
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=4978767D.4060700@intertwingly.net \
--to=rubys@intertwingly.net \
--cc=linux-kernel@vger.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