linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.0-test3-mm1
Date: Mon, 11 Aug 2003 07:35:31 -0700	[thread overview]
Message-ID: <94490000.1060612530@[10.10.2.4]> (raw)
In-Reply-To: <20030809203943.3b925a0e.akpm@osdl.org>

--Andrew Morton <akpm@osdl.org> wrote (on Saturday, August 09, 2003 20:39:43 -0700):

> . This kernel immediately triplefaults when compiled with gcc-2.95.3 and
>   CONFIG_KGDB.  It is due to compiling with "-ggdb" or "-gdwarf-2".  When
>   compiled with "-g" it works OK, but gdb screws that up.
> 
>   Moral: use a later gcc if you're a kgdb user.

Well, on the upside, 2.95.4 (Debian Woody) seems to work fine, so you don't 
have to drown yourself in the pit of slow treacle. However, after printing
"kgdb <20030806.1101.35> : port =3f8, IRQ=4, divisor =1", it spews out 
garbage to the serial console (looks like 8-bit data or something).
I didn't enable it on the cmd line, just compiled it in ... does that 
trigger it for you?

-----

Degredation on kernbench is still there:

Kernbench: (make -j N vmlinux, where N = 16 x num_cpus)
                              Elapsed      System        User         CPU
              2.6.0-test3       45.97      115.83      571.93     1494.50
          2.6.0-test3-mm1       46.43      122.78      571.87     1496.00

Quite a bit of extra sys time. I thought the suspected part of the sched
changes got backed out, but maybe I'm just not following it ...

------

4/4 split is still being wierd for me (same pattern as before). I think
it's just the rc script crapping out which causes the hostname not to
get set, or the rootfs to get remounted r/w.

M.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  parent reply	other threads:[~2003-08-11 14:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-10  3:39 2.6.0-test3-mm1 Andrew Morton
2003-08-10 17:41 ` 2.6.0-test3-mm1 Thomas Schlichter
2003-08-11 18:26   ` 2.6.0-test3-mm1 George Anzinger
2003-08-13 20:18     ` 2.6.0-test3-mm1 Sam Ravnborg
2003-08-13 20:58       ` 2.6.0-test3-mm1 Martin J. Bligh
2003-08-14  8:17       ` 2.6.0-test3-mm1 and the -g thing George Anzinger
2003-08-11 14:03 ` 2.6.0-test3-mm1 Luiz Capitulino
2003-08-11 14:35 ` Martin J. Bligh [this message]
2003-08-11 15:17   ` 2.6.0-test3-mm1 Con Kolivas
2003-08-11 18:05   ` 2.6.0-test3-mm1 William Lee Irwin III
2003-08-11 18:57     ` 2.6.0-test3-mm1 Martin J. Bligh
2003-08-11 21:55     ` 2.6.0-test3-mm1 Con Kolivas
2003-08-11 22:19       ` 2.6.0-test3-mm1 William Lee Irwin III
2003-08-11 18:39   ` 2.6.0-test3-mm1 Andrew Morton
2003-08-11 20:17     ` 2.6.0-test3-mm1 Martin J. Bligh
2003-08-11 22:16       ` 2.6.0-test3-mm1 William Lee Irwin III
2003-08-11 22:50         ` 2.6.0-test3-mm1 Martin J. Bligh
2003-08-11 23:00           ` 2.6.0-test3-mm1 Martin J. Bligh
2003-08-11 23:39           ` 2.6.0-test3-mm1 William Lee Irwin III

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='94490000.1060612530@[10.10.2.4]' \
    --to=mbligh@aracnet.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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