linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: Re: OOPS in Kmalloc
@ 2003-04-24  8:45 ramands
  2003-04-24  9:57 ` Jurriaan
  2003-04-24 17:20 ` Randy.Dunlap
  0 siblings, 2 replies; 6+ messages in thread
From: ramands @ 2003-04-24  8:45 UTC (permalink / raw)
  To: Randy.Dunlap; +Cc: linux-kernel, linux-newbie

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 !


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Re: OOPS in Kmalloc
  2003-04-24  8:45 Re: OOPS in Kmalloc ramands
@ 2003-04-24  9:57 ` Jurriaan
  2003-04-24 17:20 ` Randy.Dunlap
  1 sibling, 0 replies; 6+ messages in thread
From: Jurriaan @ 2003-04-24  9:57 UTC (permalink / raw)
  To: ramands; +Cc: Randy.Dunlap, linux-kernel, linux-newbie

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: OOPS in Kmalloc
  2003-04-24  8:45 Re: OOPS in Kmalloc ramands
  2003-04-24  9:57 ` Jurriaan
@ 2003-04-24 17:20 ` Randy.Dunlap
  1 sibling, 0 replies; 6+ messages in thread
From: Randy.Dunlap @ 2003-04-24 17:20 UTC (permalink / raw)
  To: ramands; +Cc: linux-kernel, linux-newbie


| ; 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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: OOPS in Kmalloc
  2003-04-24  4:16 ramands
@ 2003-04-24  4:34 ` Randy.Dunlap
  0 siblings, 0 replies; 6+ messages in thread
From: Randy.Dunlap @ 2003-04-24  4:34 UTC (permalink / raw)
  To: ramands; +Cc: linux-kernel, linux-newbie

> 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




^ permalink raw reply	[flat|nested] 6+ messages in thread

* OOPS in Kmalloc
@ 2003-04-24  4:16 ramands
  2003-04-24  4:34 ` Randy.Dunlap
  0 siblings, 1 reply; 6+ messages in thread
From: ramands @ 2003-04-24  4:16 UTC (permalink / raw)
  To: linux-kernel, linux-newbie; +Cc: whitnl73, ray, sneakums

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 

Raman


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 !


^ permalink raw reply	[flat|nested] 6+ messages in thread

* oops in kmalloc
@ 2003-04-23  3:41 ramands
  0 siblings, 0 replies; 6+ messages in thread
From: ramands @ 2003-04-23  3:41 UTC (permalink / raw)
  To: linux-kernel, linux-newbie
  Cc: whitnl73, ray, sneakums, marcus, martin.zwickel

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 

Raman


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 !


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2003-04-24 17:09 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-04-24  8:45 Re: OOPS in Kmalloc ramands
2003-04-24  9:57 ` Jurriaan
2003-04-24 17:20 ` Randy.Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2003-04-24  4:16 ramands
2003-04-24  4:34 ` Randy.Dunlap
2003-04-23  3:41 oops in kmalloc ramands

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).