linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Mantler <nicoya@ubb.ca>
To: Andrew Morton <akpm@osdl.org>
Cc: Adrian Bunk <bunk@stusta.de>, linux-kernel@vger.kernel.org
Subject: Re: CONFIG_MK6 = lsof hangs unkillable
Date: Fri, 20 Jan 2006 16:47:15 -0600	[thread overview]
Message-ID: <8BD55BB2-E4C4-4E73-970B-0C4FD4EDD19B@ubb.ca> (raw)
In-Reply-To: <20060120144114.08f0c340.akpm@osdl.org>


On 20-Jan-06, at 4:41 PM, Andrew Morton wrote:

> Adrian Bunk <bunk@stusta.de> wrote:
>>
>> 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.
>>
>
> hm, OK.  Well that's something we can ask Tony to eliminate, by  
> patching
> his Kconfig.cpu to make CONFIG_MK6 have the larger L1_CACHE_SHIFT  
> (and/or
> vice versa).

Just tested that a few seconds ago, actually.

CONFIG_MK6 with CONFIG_L1_CACHE_SHIFT=6 results in the same crash.

I'm going to twiddle the configs again and see if I can make a  
CONFIG_MK7 kernel with -march=k6


Cheers - Tony 'Nicoya' Mantler :)

--
Tony 'Nicoya' Mantler -- Master of Code-fu -- nicoya@ubb.ca
--  http://nicoya.feline.pp.se/  --  http://www.ubb.ca/  --


  reply	other threads:[~2006-01-20 22:47 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
2006-01-20 22:41     ` Andrew Morton
2006-01-20 22:47       ` Tony Mantler [this message]
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=8BD55BB2-E4C4-4E73-970B-0C4FD4EDD19B@ubb.ca \
    --to=nicoya@ubb.ca \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).