linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Surovegin <ebs@ebshome.net>
To: Ming Lei <mlei@Brocade.COM>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: RE: more info on kernel BUG at page_alloc.c:225
Date: Mon, 25 Aug 2003 18:37:08 -0700	[thread overview]
Message-ID: <5.1.0.14.2.20030825183409.00abbd20@mail.ebshome.net> (raw)
In-Reply-To: <7D17958F8536B640885BE12A446D548FCB2643@hq-ex-4.corp.brocad e.com>


At 06:30 PM 8/25/2003, Ming Lei wrote:
> > At 05:15 PM 8/22/2003, ming lei wrote:
> > >I should have said my version of linux2.4.19 is
> > >ppc440GP port, so the line number is line 220 in
> > >original linux 2.4.19 from kernel.org website. Be
> > >clear
> >
> > Hmm, it's still not clear what version you are using.
> > kernel.org 2.4.19 doesn't have 440GP support.
> > Are you using devel_2_4 or linuxppc-2.4 BK trees or MVL ?
>
>it's linuxppc-2.4.19 bk tree.

Hmm, URL ?

> > Another question, do you run your test on IBM reference
> > platform (Ebony) or
> > on your custom hw ?
>
>custom board for both 440 and 405.

Try your test on Ebony.
440GP uses DDR RAM which is very tricky to implement/layout correctly. It
looks like you have hardware problems.

Eugene.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

       reply	other threads:[~2003-08-26  1:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7D17958F8536B640885BE12A446D548FCB2643@hq-ex-4.corp.brocad e.com>
2003-08-26  1:37 ` Eugene Surovegin [this message]
2003-08-23  0:15 more info on kernel BUG at page_alloc.c:225 ming lei
2003-08-23  1:59 ` Eugene Surovegin
  -- strict thread matches above, loose matches on Subject: below --
2003-08-23  0:10 ming lei

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=5.1.0.14.2.20030825183409.00abbd20@mail.ebshome.net \
    --to=ebs@ebshome.net \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=mlei@Brocade.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;
as well as URLs for NNTP newsgroup(s).