linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "mike zheng" <mail4mz@gmail.com>
To: "Kim Phillips" <kim.phillips@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Kernel Oops when run ifconfig on MPC8360MDS board
Date: Mon, 20 Oct 2008 21:23:28 -0700	[thread overview]
Message-ID: <5c9cd53b0810202123x32488ba7vb3c70daa8d09aef@mail.gmail.com> (raw)
In-Reply-To: <20081020195009.6bf54d5a.kim.phillips@freescale.com>

On 10/20/08, Kim Phillips <kim.phillips@freescale.com> wrote:
> On Mon, 20 Oct 2008 15:00:33 -0700
> "mike zheng" <mail4mz@gmail.com> wrote:
>
> > I have following kernel Oops when I run ifconfig to setup the UEC0 of
> > MPC8360MDS board. There is no hardware problem, the UEC0 runs well
> > under Uboot.
>
> does this occur on vanilla u-boot and kernel versions?  if so, which
> ones, and on what board revision?
>
The kernel Oops happened under Linux when I try to use "ifconfig" to
setup the eth0. Under Uboot, the UEC0 works fine. I am able to do
ping, tftp via the ethernet port.


> > Call backtrace:
> > C0126890 C00D59D0 C00D761C C012F400 C0130DD4 C01746B4 C017712C
> > C0127770 C004D8B0 C0005ABC 00000000 10001214 100023C4 0FEC4E00
> > 00000000
>
> might want to turn on verbose debugging while you're at it.

Which flag shall I turned on? I am not formaliar to the network driver. Thanks!
>
> Kim
>

  reply	other threads:[~2008-10-21  4:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20 22:00 Kernel Oops when run ifconfig on MPC8360MDS board mike zheng
2008-10-21  0:50 ` Kim Phillips
2008-10-21  4:23   ` mike zheng [this message]
2008-10-21  4:26     ` mike zheng
2008-10-21 15:51       ` mike zheng

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=5c9cd53b0810202123x32488ba7vb3c70daa8d09aef@mail.gmail.com \
    --to=mail4mz@gmail.com \
    --cc=kim.phillips@freescale.com \
    --cc=linuxppc-dev@ozlabs.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).