[lkml]   [2005]   [Jul]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Tracking a bug in x86-64
On Tue, 2005-07-05 at 14:12 -0700, Andrew Morton wrote:
> Bongani Hlope <> wrote:
> >
> > I haven't tested 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
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-07-06 10:22    [W:0.037 / U:6.056 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site