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]
Message-ID: <20061112141016.GA5297@stusta.de>
Date:	Sun, 12 Nov 2006 15:10:16 +0100
From:	Adrian Bunk <bunk@...sta.de>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Andrew Morton <akpm@...l.org>, David Howells <dhowells@...hat.com>,
	Neil Brown <neilb@....unsw.edu.au>,
	"bugme-daemon@...nel-bugs.osdl.org" 
	<bugme-daemon@...zilla.kernel.org>, linux-kernel@...r.kernel.org,
	alex@...snet.ru, mingo@...hat.com
Subject: Re: [Bugme-new] [Bug 7495] New: Kernel periodically hangs.

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

-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ