mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Zhenyu Wu" <y030729@njupt.edu.cn>
To: nickpiggin@yahoo.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Re: About kernel panic!
Date: Mon, 20 Dec 2004 21:43:22 +0800	[thread overview]
Message-ID: <303550202.05721@njupt.edu.cn> (raw)

Do you mean that there is something wrong with my Kernel Code? So, i have to use a
new kernel code, but i can't understand why.

Thanks and Best,


>From: Nick Piggin <nickpiggin@yahoo.com.au>
>Reply-To: 
>To: Zhenyu Wu <y030729@njupt.edu.cn>
>Subject: Re: About kernel panic!
>Date:Mon, 20 Dec 2004 20:21:23 +1100
>
>Zhenyu Wu wrote:
> > Hello, Everyone,
> > 
> > I think i have met lots of troubles when i am programming in the kernel, so,
i
> > want to get
> > some help.
> > 
> > One of my troubles is that, sometimes, the program can work well, but
sometimes,
> > there are
> > kernel panics. So, does someone else meet such questions, what is the major
> > reasons? From the
> > indication of the log messages, i can find the messages on allocting the
memory, i
> > remember, 
> > i use the kmalloc to do it, but is there something wrong? 
> > 
> 
> Yes, there is something wrong with your kernel code. The oops will
> tell you what went wrong.
> 
> Reading Documentation/oops-tracing.txt is a good start.
> 
> Nick
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>



             reply	other threads:[~2004-12-20 12:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-20 13:43 Zhenyu Wu [this message]
2004-12-20 14:40 ` Jan Dittmer
  -- strict thread matches above, loose matches on Subject: below --
2004-12-20  9:40 Zhenyu Wu
2004-12-20  9:21 ` Nick Piggin

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=303550202.05721@njupt.edu.cn \
    --to=y030729@njupt.edu.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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

Powered by JetHome