From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Zhenyu Wu <y030729@njupt.edu.cn>
Cc: linux-kernel@vger.kernel.org
Subject: Re: About kernel panic!
Date: Mon, 20 Dec 2004 20:21:23 +1100 [thread overview]
Message-ID: <41C69993.5000704@yahoo.com.au> (raw)
In-Reply-To: <303535658.02371@njupt.edu.cn>
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
next prev parent reply other threads:[~2004-12-20 9:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 9:40 About kernel panic! Zhenyu Wu
2004-12-20 9:21 ` Nick Piggin [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-20 13:43 Zhenyu Wu
2004-12-20 14:40 ` Jan Dittmer
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=41C69993.5000704@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=y030729@njupt.edu.cn \
/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.