Thanks Mulyadi, Briones and everyone. I ll keep a watch for the pitfalls. Once again many thanks for the help. --Pradeep On Wed, May 27, 2009 at 5:25 AM, archieval briones <steiner_07@xxxxxxxxx> wrote: > I am a kernel newbie also but I can recommend taking note of the scheduling > policy that you used in creating your threads. If possible add some delay in > some threads to see if they will be preempted by the others or not. Examine > if the priorities of the threads are the same, static and dynamic priority. > And also take note of the code sections that might sleep. If you are coding > interrupt handlers, use spin locks in the interrupt handlers and codes > running in task context. > > I hope I helped a bit >_< > > Registered Linux User #478208 > > --- On Tue, 5/26/09, pradeep singh <pradeep.rautela@xxxxxxxxx> wrote: > > From: pradeep singh <pradeep.rautela@xxxxxxxxx> > Subject: Debugging race conditions? > To: "kernelnewbie" <kernelnewbies@xxxxxxxxxxxx> > Cc: "kernelmentors" <kernel-mentors@xxxxxxxxxxx> > Date: Tuesday, May 26, 2009, 4:57 PM > > Hi All, > > I am having a tough time debugging concurrency issues it seems. > I find myself flabbergasted at debugging panic because of race issues. > > I would like to ask people here, if they have any advice on how to > properly approach these specific set of panics? > How do they do it? > Are there any rules of thumbs which can help me? > > Thanks in Advance > --Pradeep > -- > Pradeep > _______________________________________________ > Kernel-mentors mailing list > Kernel-mentors@xxxxxxxxxxx > http://selenic.com/mailman/listinfo/kernel-mentors > > -- Pradeep -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
