public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: 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: Sun, 12 Nov 2006 15:10:16 +0100	[thread overview]
Message-ID: <20061112141016.GA5297@stusta.de> (raw)
In-Reply-To: <1163339868.3293.126.camel@laptopd505.fenrus.org>

On Sun, Nov 12, 2006 at 02:57:48PM +0100, Arjan van de Ven wrote:
> On Sun, 2006-11-12 at 14:37 +0100, Adrian Bunk wrote:
> > On Sun, Nov 12, 2006 at 02:16:16PM +0100, Arjan van de Ven wrote:
> > > 
> > > > Some APIC-related bugs in the kernel Bugzilla that have been reported or 
> > > > confirmed during the last 12 months (I only looked at "apic" in the 
> > > > subject, there might be more related bugs in the Bugzilla):
> > > > 
> > > > #5038 Fast running system clock with IO-APIC enabled
> > > 
> > > This is a UP machine. NotInteresting(tm) wrt APIC.
> > >... 
> > 
> > Currently it's a supported configuration.
> 
> define "supported"; we have code to try it and it's great if it works.
> But if it doesn't... you're out of luck.
> 
> We KNOW it can't work on a sizable amount of machines.  This is why it
> is a config option; you can enable it if YOUR machine is KNOWN to work,
> and you get some gains. But it's also understood that it often it won't
> work. So any sensible distro (since they have to aim for a wide
> audience) disables this option ...

Nowadays, many distributions only ship CONFIG_SMP=y kernels...

> > We must either handle such cases or explicitely disable the APIC on all 
> > UP machines 
> 
> that'd be the same as setting the config option off...

Except for the common case of CONFIG_SMP=y kernels on UP machines...

> > > I think that's a mistake. But oh well, I suspect in practice ACPI/BIOS
> > > cause it to be turned off automatic most of the time.
> > 
> > I'd doubt the latter. Even on my cheap Asus board running an i386
> > AMD Athlon XP with 1.8 GHz the APIC is both used and working without any
> > problems.
> 
> "it works on my one machine so it works for everyone". That's simply not
> true. We KNOW it can't work everywhere on UP, especially on i386. SMM
> assumptions; people gluing the apic pins to the reset line, we've seen
> it all. 
> That it works for you is great. But that doesn't mean it automatically
> works for everyone.

You miss my point.

You said you'd suspect it to be turned off automatic most of the time, 
and that's the point I think you might be wrong at.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2006-11-12 14:10 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 [this message]
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
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=20061112141016.GA5297@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=alex@hausnet.ru \
    --cc=arjan@infradead.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --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