Messages in this thread | | | Subject | Re: Tracking a bug in x86-64 | From | Arjan van de Ven <> | Date | Wed, 06 Jul 2005 08:34:55 +0200 |
| |
On Tue, 2005-07-05 at 14:12 -0700, Andrew Morton wrote: > Bongani Hlope <bonganilinux@mweb.co.za> wrote: > > > > I haven't tested 2.6.12.2 but the problem was introduced around 2.6.11-mm1 and > > found its way to 2.6.12-rcX. First try to run the following command (this works for me) > > echo 0 > /proc/sys/kernel/randomize_va_space > > I got an email from Juan Gallego (cc'd), he says that command does not work for him though. > > > > Andrew, > > Should I log this on the kernel's bugzilla? > > Yes please. This is a tough one, and having one place to go to for the > info would be useful.
key for this one is to make sure we separate the cases carefully, and not end up with one big bucket of "something broke" that has a gazilion different and unrelated causes. For the cases where a vm layout thing is suspected of causing the breakage we also really need a /proc/<pid>/maps *at the time of the breakage* realistically for doing any kind of diagnostics.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |