On Sat, 20 May 2006, Mel Gorman wrote:
Obviously. One option is to back out
have-x86_64-use-add_active_range-and-free_area_init_nodes.patch and see what
happens on Christian's machine.
I've disabled CONFIG_PM and backed out above patch (from -rc4-mm1), but
sadly, the error persists:
http://nerdbynature.de/bits/2.6.17-rc4-mm1/no-CONFIG_PM/
http://nerdbynature.de/bits/2.6.17-rc4-mm2.x/no-CONFIG_PM/
(the first one with the said patch backed out)
Thanks for your ideas,
Christian.
--
There's another way to survive. Mutual trust -- and help.
-- Kirk, "Day of the Dove", stardate unknown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
