From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754488AbZBCSpl (ORCPT ); Tue, 3 Feb 2009 13:45:41 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752637AbZBCSpb (ORCPT ); Tue, 3 Feb 2009 13:45:31 -0500 Received: from vanadium.sabren.com ([67.19.173.84]:32887 "EHLO vanadium.sabren.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752445AbZBCSpa (ORCPT ); Tue, 3 Feb 2009 13:45:30 -0500 X-Greylist: delayed 2975 seconds by postgrey-1.27 at vger.kernel.org; Tue, 03 Feb 2009 13:45:30 EST Message-ID: <49888526.60803@intertwingly.net> Date: Tue, 03 Feb 2009 12:55:50 -0500 From: Sam Ruby User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: Andrew Morton CC: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org Subject: Re: [APIC] Kernel panic, rsync corruption, intel q8200, 2.6.28-rc8 References: <4978767D.4060700@intertwingly.net> <20090130000758.1dff0113.akpm@linux-foundation.org> In-Reply-To: <20090130000758.1dff0113.akpm@linux-foundation.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Andrew Morton wrote: > On Thu, 22 Jan 2009 08:37:01 -0500 Sam Ruby wrote: > >> 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, > > Join the ever-growing noapic club :( > > I assume this is an ACPI problem. Or at least, a BIOS problem which > ACPI can solve for us. My understanding is that APCI and APIC are two different things. >> 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. > > Yes, it might be unrelated. There are no kernel messages when it happens? I see no messages to /var/log/messages while doing the following (which involves rsync'ing a 2618793984 byte file from an NTFS to ext3 drive on the same machine: rubys@rubix4:~/tmp$ rsync /mnt/shared/windows7_7000.iso . rubys@rubix4:~/tmp$ openssl md5 windows7_7000.iso MD5(windows7_7000.iso)= 953b9ac92d58f5edef525004bcce048d rubys@rubix4:~/tmp$ rsync /mnt/shared/windows7_7000.iso . rubys@rubix4:~/tmp$ openssl md5 windows7_7000.iso MD5(windows7_7000.iso)= 695328ef1280708eb73303656f6ef0b2 >> 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. > > It'd be best to raise a report against ACPI?BIOS (I think) at > bugzilla.kernel.org, please. Once again, I'm talking about apic not acpi... does this advice still hold? > If any previous kernel version worked OK, please be sure to note that. I don't believe that's the case. > Thanks. - Sam Ruby