From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Tony Mantler <nicoya@ubb.ca>, linux-kernel@vger.kernel.org
Subject: Re: CONFIG_MK6 = lsof hangs unkillable
Date: Fri, 20 Jan 2006 21:31:04 +0100 [thread overview]
Message-ID: <20060120203104.GA31803@stusta.de> (raw)
In-Reply-To: <20060120044407.432eae02.akpm@osdl.org>
On Fri, Jan 20, 2006 at 04:44:07AM -0800, Andrew Morton wrote:
> Tony Mantler <nicoya@ubb.ca> wrote:
> >
> > I'm having trouble running lsof on 2.6.15.1 when the kernel is
> > compiled with CONFIG_MK6. When run as root, lsof will segfault, and
> > when run as a user lsof will hang unkillable.
> >
> > The same kernel, same machine, but compiled with CONFIG_MK7 runs just
> > lsof just fine.
>
> That's creepy. CONFIG_MK6 hardly does anything. The main thing it does is
> feed `-march=k6' into the compiler. MK7 uses `-march=athlon'.
>...
CONFIG_MK7 results in a bigger L1_CACHE_SHIFT than CONFIG_MK6.
AFAIR it wouldn't be the first time that changing L1_CACHE_SHIFT would
hide a real bug visible with a different L1_CACHE_SHIFT.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-01-20 20:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 4:43 CONFIG_MK6 = lsof hangs unkillable Tony Mantler
2006-01-16 22:58 ` Tony Mantler
2006-02-17 1:45 ` Brandon Low
2006-01-20 12:44 ` Andrew Morton
2006-01-20 20:31 ` Adrian Bunk [this message]
2006-01-20 22:41 ` Andrew Morton
2006-01-20 22:47 ` Tony Mantler
2006-01-20 23:39 ` Tony Mantler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060120203104.GA31803@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicoya@ubb.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.