linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	William Lee Irwin III <wli@holomorphy.com>
Subject: Re: 2.6.0-test2-mm5
Date: Thu, 7 Aug 2003 19:07:56 -0300 (BRT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0308071905200.5090-100000@logos.cnet> (raw)
In-Reply-To: <20030807142807.3e4a284c.akpm@osdl.org>


On Thu, 7 Aug 2003, Andrew Morton wrote:

> Marcelo Tosatti <marcelo@conectiva.com.br> wrote:
> >
> > PCI: Using configuration type 1
> > 
> > 
> >  Locked up solid there. Want more info ? 
> 
> doh.  I don't even know who to lart for that one!
> 
> Could you please boot with "initcall_debug" and then resolve the final
> couple of addresses in System.map?  That'll narrow it down.

Heck it works with initcall_debug:

Red Hat Linux release 7.3 (Valhalla)
Kernel 2.6.0-test2-mm5 on an i686

I tried again without initcall_debug and it doesnt: 

Starting migration thread for cpu 7
CPUS done 16
zapping low mappings.
mtrr: v2.0 (20020519)
Initializing RT netlink socket
EISA bus registered
PCI: PCI BIOS revision 2.10 entry at 0xfd26c, last bus=15
PCI: Using configuration type 1
....

What additional info you guys want? 

Full output of both with/without initcall_debug boot messages or?

Odd, odd. 

--
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>

  reply	other threads:[~2003-08-07 22:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-07  5:37 2.6.0-test2-mm5 Andrew Morton
2003-08-07  6:31 ` 2.6.0-test2-mm5 Martin J. Bligh
2003-08-07  7:05   ` 2.6.0-test2-mm5 Andrew Morton
2003-08-07  8:29     ` 2.6.0-test2-mm5 Nick Piggin
2003-08-07  8:40       ` 2.6.0-test2-mm5 Nick Piggin
2003-08-07  8:43         ` 2.6.0-test2-mm5 Nick Piggin
2003-08-07 18:30           ` 2.6.0-test2-mm5 Martin J. Bligh
2003-08-07  8:44         ` 2.6.0-test2-mm5 Jens Axboe
2003-08-07  6:33 ` 2.6.0-test2-mm5 William Lee Irwin III
2003-08-07  6:44   ` 2.6.0-test2-mm5 Andrew Morton
2003-08-07  8:00 ` 2.6.0-test2-mm5 Christoph Hellwig
2003-08-07 21:21 ` 2.6.0-test2-mm5 Marcelo Tosatti
2003-08-07 21:24   ` 2.6.0-test2-mm5 William Lee Irwin III
2003-08-07 21:28   ` 2.6.0-test2-mm5 Andrew Morton
2003-08-07 22:07     ` Marcelo Tosatti [this message]
2003-08-08 20:51       ` 2.6.0-test2-mm5 Marcelo Tosatti
2003-08-08 21:36         ` 2.6.0-test2-mm5 William Lee Irwin III
2003-08-07 23:47 ` 2.6.0-test2-mm5 Martin J. Bligh
2003-08-08  0:16   ` 2.6.0-test2-mm5 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=Pine.LNX.4.44.0308071905200.5090-100000@logos.cnet \
    --to=marcelo@conectiva.com.br \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=wli@holomorphy.com \
    /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