All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gregor Waltz <gregor.waltz@raritan.com>
To: linux-mips@linux-mips.org
Subject: Re: Toshiba JMR 3927 working setup?
Date: Thu, 17 Jan 2008 11:50:32 -0500	[thread overview]
Message-ID: <478F8758.1010105@raritan.com> (raw)
In-Reply-To: <20080117.010459.51867104.anemo@mba.ocn.ne.jp>

Atsushi Nemoto wrote:
> Hmm.  The puts() in arch/mips/jmr3927/common/puts.c looks usable even
> on kernel entry.  You can verify if it can really be used on
> start_kernel(), then start tracking down the problem.
>
> ---
> Atsushi Nemoto
>   

puts() has helped, but I wish that I had something to dump the stack. Is 
kgdb easy to set up?

In main.c, init_IRQ() eventually uses kmalloc:
arch_init_irq() -> txx9_irq_init() -> ioremap() -> __get_vm_area_node() 
-> kmalloc_node()...
malloc_sizes is not yet initialized, though, which means that cs_cachep 
is zero for all entries. My system reboots when it reaches 
cpu_cache_get() in mm/slab.c where cachep is zero.

It seems to me that kmem_cache_init() ought to be run before any 
kmallocs. kmem_cache_init() seems to require mem_init(). After I moved 
mem_init and kmem_cache_init before init_IRQ(), it gets down to 
pidhash_init() before rebooting, which I am looking into now.


What ought to be done to fix the init_IRQ()/kmalloc problem?

Thanks

  reply	other threads:[~2008-01-17 16:50 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-04 16:45 Toshiba JMR 3927 working setup? Gregor Waltz
2008-01-04 17:21 ` Thiemo Seufer
2008-01-04 18:40   ` Gregor Waltz
2008-01-04 18:51     ` Florian Lohoff
2008-01-04 19:23       ` Gregor Waltz
2008-01-04 19:23     ` Thiemo Seufer
2008-01-04 22:27       ` Gregor Waltz
2008-01-05 14:42         ` Atsushi Nemoto
2008-01-07 12:21           ` Ralf Baechle
2008-01-07 15:34             ` Atsushi Nemoto
2008-01-05 15:07     ` Atsushi Nemoto
2008-01-11 17:49       ` Gregor Waltz
2008-01-12 12:17         ` Atsushi Nemoto
2008-01-15 15:50           ` Gregor Waltz
2008-01-15 15:50             ` Gregor Waltz
2008-01-15 16:14             ` Thiemo Seufer
2008-01-15 20:05               ` Gregor Waltz
2008-01-15 23:14                 ` Thiemo Seufer
2008-01-16 15:28                   ` Gregor Waltz
2008-01-16 16:04                     ` Atsushi Nemoto
2008-01-17 16:50                       ` Gregor Waltz [this message]
2008-01-18  1:05                         ` Atsushi Nemoto
2008-01-05 14:45 ` Ralf Baechle
2008-01-08 23:54   ` Gregor Waltz
2008-01-09  0:17     ` Thiemo Seufer
2008-02-04  1:14     ` M. Warner Losh
  -- strict thread matches above, loose matches on Subject: below --
2008-01-25 16:50 Max Okumoto
2008-01-26  5:08 ` Atsushi Nemoto
2008-01-28 16:36   ` Gregor Waltz
2008-01-29 13:50     ` Atsushi Nemoto
2008-03-06 15:49   ` Ralf Baechle

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=478F8758.1010105@raritan.com \
    --to=gregor.waltz@raritan.com \
    --cc=linux-mips@linux-mips.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 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.