[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+icZUVMY76bRFgUumZy0G-FFM=80iwfSFSopHMwHRYfgKjLjA@mail.gmail.com>
Date: Sat, 12 Jan 2013 11:13:14 +0100
From: Sedat Dilek <sedat.dilek@...il.com>
To: Joe Perches <joe@...ches.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
Randy Dunlap <rdunlap@...radead.org>,
akpm@...ux-foundation.org, mm-commits@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-fsdevel@...r.kernel.org, linux-next@...r.kernel.org
Subject: Re: mmotm 2013-01-11-15-47 uploaded (x86 asm-offsets broken)
On Sat, Jan 12, 2013 at 3:29 AM, Joe Perches <joe@...ches.com> wrote:
> On Sat, 2013-01-12 at 13:17 +1100, Stephen Rothwell wrote:
>> On Fri, 11 Jan 2013 17:43:06 -0800 Randy Dunlap <rdunlap@...radead.org> wrote:
>> >
>> > b0rked.
>> >
>> > Some (randconfig?) causes this set of errors:
>
> I guess that's when CONFIG_HZ is not an even divisor of 1000.
> I suppose this needs to be worked on a bit more.
>
>
I remember this patch from Joe come up with a pending patch in
net-next.git#master [1] (I mention this as I have not seen hit it in
latest Linux-Next whereas this latest mmotm includes it [2]).
$ grep "config HZ_" kernel/Kconfig.hz
config HZ_100
config HZ_250
config HZ_300
config HZ_1000
As I see Randy has in his kernel-config:
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
CONFIG_HZ_300=y
# CONFIG_HZ_1000 is not set
CONFIG_HZ=300
So there is a problem for the value "300" (only)?
Regards,
- Sedat -
[1] http://git.kernel.org/?p=linux/kernel/git/davem/net-next.git;a=commitdiff;h=c10d73671ad30f54692f7f69f0e09e75d3a8926a
[2] http://git.cmpxchg.org/?p=linux-mmotm.git&a=search&h=HEAD&st=commit&s=softirq
> --
> To unsubscribe from this list: send the line "unsubscribe linux-next" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
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