linux-kernel - Re: [APIC] Kernel panic, rsync corruption, intel q8200, 2.6.28-rc8

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 9 Feb 2009 21:31:09 +0000 (GMT)
From:	"Maciej W. Rozycki" <macro@...ux-mips.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	Sam Ruby <rubys@...ertwingly.net>, linux-kernel@...r.kernel.org,
	linux-acpi@...r.kernel.org, x86@...nel.org
Subject: Re: [APIC] Kernel panic, rsync corruption, intel q8200, 2.6.28-rc8

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! 
> > >>   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.
> 
> They sure are.  But it is ACPI which communicates with the BIOS to tell
> the kernel about the APIC, hwo it's wired up, etc.
> 
> Although in this case it looks like the problem might be with the
> mp-bios tables, which ACPI does not handle.  In which case it would be
> core x86 code which will have to fix this up, not ACPI.

 The message is misleading.  It predates the ACPI and has never been 
updated.  It applies equally to both MPS and ACPI systems.  Earlier 
bootstrap messages can be used to determine which configuration method has 
been used by the kernel on this system (many systems provide both).

  Maciej
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/