linux-kernel - Re: [patch] Add insmod option to force the use of the backup timer.

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: <20070305190333.c01a7ffc.akpm@linux-foundation.org>
Date:	Mon, 5 Mar 2007 19:03:33 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Gerd Hoffmann <kraxel@...e.de>
Cc:	Dave Jones <davej@...hat.com>, linux-kernel@...r.kernel.org,
	Alex Williamson <alex.williamson@...com>,
	Kevin Stansell <kstansel@...ibm.com>
Subject: Re: [patch] Add insmod option to force the use of the backup timer.

On Thu, 01 Mar 2007 14:20:09 +0100 Gerd Hoffmann <kraxel@...e.de> wrote:

> Dave Jones wrote:
> > On Wed, Feb 28, 2007 at 11:23:46AM +0100, Gerd Hoffmann wrote:
> >  > The test which automatically enables the backup timer on some HP
> >  > machines doesn't trigger on other hardware which needs the backup
> >  > timer too.
> > 
> > Did you figure out *why* that test doesn't trigger?
> 
> I didn't, probably a slightly different hardware bug.
> 
> > Making that work seems a better solution to me than adding magic
> > options that users won't know they have to use.
> 
> Sure, that would be better.  I'll leave that to the ibm guys who own the
> hardware in question ;)
> 

Well, it doens't _have_ to be the IBM guys.  Anyone who can reproduce this
problem should be able to find the suitable magic to detect the broken
interrupt generation.

An automatic fix is much preferable to a module parameter which most people
won't even know exists.

Perhaps Alex can suggest some debugging steps we can take to work out
why the test isn't triggering?
-
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/