Skip to contentSkip to conversation

OOPS in Kmalloc

DISCUSSION ramands 3 participants 3 messages Apr 24, 2003

lore
Share & tools
lore

ramands

author
#0 lore raw

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 i will mail the exact oops messages in next mail
right now i am debugging by using printk only

raman
"Randy.Dunlap" wrote:

> Hello,
> i am getting OOPS in Kmalloc .
>
> void **data;
> qset = 1000;
>
> dptr->data = kmalloc(qset * sizeof(char *), GFP_KERNEL); >
> what could the possible the cause of the error
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
As I am so fond of saying, it's almost always correct to indicate what kernel version one if referring to in a problem report.

Please decode the oops output and post it here.

~Randy

Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com

Buy The Best In BOOKS at http://www.bestsellers.indiatimes.com

Bid for for Air Tickets @ Re.1 on Air Sahara Flights. Just log on to http://airsahara.indiatimes.com and Bid Now !

#1 lore raw

From: ramands <[email protected]>
Date: Thu, Apr 24, 2003 at 02:15:06PM +0530

Quoted 3 lines

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

Quoted 1 line

i will mail the exact oops messages in next mail

no need for that, read the docs first.

Quoted 2 lines

right now i am debugging by using printk only

Good luck,
Jurriaan

Signature · 4 lines
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
#2 lore raw
In reply to ramands
| ; Hello,
| ; i am getting OOPS in Kmalloc .
| ;
| ; void **data;
| ; qset = 1000;
| ;
| ; dptr->data = kmalloc(qset * sizeof(char *), GFP_KERNEL);
| ;
| ; what could the possible the cause of the error
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| As I am so fond of saying, it's almost always correct to indicate what
| kernel version one if referring to in a problem report.
| 
| Please decode the oops output and post it here.

I can't reproduce this problem on Linux 2.5.68. However, I did initialize dptr before using it. Did you?

You see, I can't tell if you did or not because you didn't post a complete sample to reproduce the problem.

--
~Randy