public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Dave Jones <davej@redhat.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
	Adrian Bunk <bunk@stusta.de>, Andrew Morton <akpm@osdl.org>,
	David Howells <dhowells@redhat.com>,
	Neil Brown <neilb@cse.unsw.edu.au>,
	"bugme-daemon@kernel-bugs.osdl.org" 
	<bugme-daemon@bugzilla.kernel.org>,
	linux-kernel@vger.kernel.org, alex@hausnet.ru, mingo@redhat.com
Subject: Re: [Bugme-new] [Bug 7495] New: Kernel periodically hangs.
Date: Mon, 13 Nov 2006 03:07:56 +0100	[thread overview]
Message-ID: <200611130307.57110.ak@suse.de> (raw)
In-Reply-To: <20061112214540.GB31649@redhat.com>


> Andi has a nice patch in the suse kernel which adds heuristics to disable
> apic on systems where it isn't likely to work.  It DTRT in at least
> one problem case that I know of.   The actual fall-out from enabling
> 'run SMP kernels on UP i686' for FC6 has mostly been a non-event.
> Literally a handful of cases, that will likely all get caught and worked
> around by Andi's patch or similar.

I haven't pushed that recently because i was busy with other things, but
needs to be revisited yes.

One broken case that still happens is that the patch assumes working
SMBIOS. When there is no year in SMBIOS it will turn off APIC because
it assumes it is a very old system. But sometimes new systems who would
like APIC have illegal or broken SMBIOS year. On very new systems it isn't
a problem again because those tend to have multiple cores.

That could be probably a bit more clever. It's always difficult to
navigate around all kinds of BIOS bugs.

-Andi

  reply	other threads:[~2006-11-13  2:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200611111129.kABBTWgp014081@fire-2.osdl.org>
2006-11-11 18:00 ` [Bugme-new] [Bug 7495] New: Kernel periodically hangs Andrew Morton
2006-11-11 18:10   ` Arjan van de Ven
2006-11-11 18:19     ` Andrew Morton
2006-11-12 11:50       ` Arjan van de Ven
2006-11-12 12:53         ` Adrian Bunk
2006-11-12 13:16           ` Arjan van de Ven
2006-11-12 13:37             ` Adrian Bunk
2006-11-12 13:57               ` Arjan van de Ven
2006-11-12 14:10                 ` Adrian Bunk
2006-11-12 14:16                   ` Arjan van de Ven
2006-11-12 15:21                     ` Adrian Bunk
2006-11-12 15:50                       ` Arjan van de Ven
2006-11-12 15:59                       ` Patrick McFarland
2006-11-12 16:07                         ` Arjan van de Ven
2006-11-12 16:47                         ` Adrian Bunk
2006-11-12 21:45                     ` Dave Jones
2006-11-13  2:07                       ` Andi Kleen [this message]
2006-11-12 19:18             ` Ingo Oeser
2006-11-12 19:34               ` Andrew Morton
2006-11-12 20:32               ` Arjan van de Ven
2006-11-13  6:42   ` Neil Brown
2006-11-13 11:22     ` David Howells

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=200611130307.57110.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=alex@hausnet.ru \
    --cc=arjan@infradead.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=bunk@stusta.de \
    --cc=davej@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=neilb@cse.unsw.edu.au \
    /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