From: Jurriaan <thunder7@xs4all.nl>
To: ramands <ramands@indiatimes.com>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
linux-kernel@vger.kernel.org, linux-newbie@vger.kernel.org
Subject: Re: Re: OOPS in Kmalloc
Date: Thu, 24 Apr 2003 11:57:34 +0200 [thread overview]
Message-ID: <20030424095734.GA13735@middle.of.nowhere> (raw)
In-Reply-To: <200304240813.NAA23499@WS0005.indiatimes.com>
From: ramands <ramands@indiatimes.com>
Date: Thu, Apr 24, 2003 at 02:15:06PM +0530
> hello randy
> as i am new to kernel level programing
> i do not know how to decode a oops . could you tell me how to do it
read the (copious) documentation in /usr/src/linux/Documentation
> i will mail the exact oops messages in next mail
no need for that, read the docs first.
> right now i am debugging by using printk only
>
Good luck,
Jurriaan
--
Because Hawk and Fisher were who you turned to when you'd tried every-
thing else, including closing your eyes and hoping it would just go away.
Simon R Green - Beyond the Blue Moon
Debian (Unstable) GNU/Linux 2.5.68 3940 bogomips load av: 0.10 0.05 0.06
next prev parent reply other threads:[~2003-04-24 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 8:45 Re: OOPS in Kmalloc ramands
2003-04-24 9:57 ` Jurriaan [this message]
2003-04-24 17:20 ` Randy.Dunlap
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=20030424095734.GA13735@middle.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-newbie@vger.kernel.org \
--cc=ramands@indiatimes.com \
--cc=rddunlap@osdl.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).