Hi!
Yes, please make sure that you have CONFIG_KALLSYM and CONFIG_FRAME_POINTER
enabled. However, I guess you already do have them enabled, because probably
you would not have seen any stacktrace otherwise. I do not know what else to
enable.
BTW: Is your system a nommu one?
-Michi
On 09
if i enable CONFIG_KALLSYMS, will it be useful
On Sun, Jun 27, 2010 at 9:00 AM, Harishkumar V wrote:
> Hi,
>
> is any kernel option to enable capture stack trace for code struck in x86.
> how to capture this on x86.
>
>
> i can cross verify the option with the ARM kernel configuration.
>
> On Sun
Hi,
is any kernel option to enable capture stack trace for code struck in x86.
how to capture this on x86.
i can cross verify the option with the ARM kernel configuration.
On Sun, Jun 27, 2010 at 8:52 AM, Harishkumar V wrote:
> Hi,
>
> is any kernel option to enable to capture stack trace in x8
On Sun, Jun 27, 2010 at 01:34, Robert P. J. Day wrote:
>
> i'm looking for a simple example of a PCI driver that uses DMA. can
> anyone point to one in the current kernel source tree that would make
> a good example that isn't stupidly complicated or obscure? thanks.
NE2000 compatible card? th
On Sun, Jun 27, 2010 at 08:52, Usman S. Ansari wrote:
> Don't understand what you are saying.
>
You said by yourself that kmalloc fixed the situation, right? Actually
it's quite clear once you think deeper about it (unless I am really
fooled).
Or try using "static"
--
regards,
Mulyadi San
Hi,
is any kernel option to enable to capture stack trace in x86. how to capture
this on x86.
i can cross verify the option with the ARM kernel configuration.
On Sat, Jun 26, 2010 at 9:40 PM, Michael Blizek <
mic...@michaelblizek.twilightparadox.com> wrote:
> Hi!
>
> On 17:15 Sat 26 Jun , H
--- On Fri, 6/25/10, Mulyadi Santosa wrote:
> From: Mulyadi Santosa
> Subject: Re: Accessing kernel memory from multiple modules
> To: "Usman S. Ansari"
> Cc: "Linux Kernel List"
> Date: Friday, June 25, 2010, 9:01 PM
> Dear Usman...
>
> Sorry if I can't give complete explanation, but hopeful
2010/6/26 Mulyadi Santosa :
> Dear Usman...
>
> Sorry if I can't give complete explanation, but hopefully it's enough...
>
> On Sat, Jun 26, 2010 at 02:31, Usman S. Ansari wrote:
>> I have two kernel modules running.
>>
>> Module 1:
>> - struct a
>> {
>> int val1;
>> char *buffer
>> ...
>>
i'm looking for a simple example of a PCI driver that uses DMA. can
anyone point to one in the current kernel source tree that would make
a good example that isn't stupidly complicated or obscure? thanks.
rday
--
Robe
Am 26.06.2010 13:40, schrieb Robert P. J. Day:
> On Sat, 26 Jun 2010, Mulyadi Santosa wrote:
>
>> Hi...
>>
>> On Sat, Jun 26, 2010 at 03:53, Chris wrote:
>>> I read the pages 83-90 in the LDD3 and the sources
>>> (http://lxr.linux.no/#linux+v2.6.34/include/linux/proc_fs.h).
>>>
>>> Now, I am a li
Hi!
On 17:15 Sat 26 Jun , Harishkumar V wrote:
> Hi,
>
> this is the one, i am getting in the console,
...
This is only the stack trace of the softlockup check, not the code which got
stuck. I am not sure whether generating that stack trace on arm is possible.
Can you reproduce this on x86 o
On Sat, 26 Jun 2010, Mulyadi Santosa wrote:
> Hi...
>
> On Sat, Jun 26, 2010 at 03:53, Chris wrote:
> > I read the pages 83-90 in the LDD3 and the sources
> > (http://lxr.linux.no/#linux+v2.6.34/include/linux/proc_fs.h).
> >
> > Now, I am a little confused. The struct proc_dir_entry contains a
>
On Sat, 26 Jun 2010, Mulyadi Santosa wrote:
> Hi...
>
> On Sat, Jun 26, 2010 at 07:35, Brian Paterni wrote:
> > What I'm wondering though, is how production drivers handle the
> > creation of these special /dev/* files? "Real" kernel drivers do
> > not depend on specialized scripts to handle this
Hi,
this is the one, i am getting in the console,
BUG: soft lockup - CPU#0 stuck for 61s! [linphone-3:764]
Modules linked in:
Pid: 764, comm: linphone-3
CPU: 0Not tainted (2.6.28-rc9 #14)
PC is at handle_IRQ_event+0x28/0x74
LR is at handle_level_irq+0x94/0xec
pc : []lr : []
Hi!
On 12:13 Sat 26 Jun , Harishkumar V wrote:
> Hi,
>
> I am facing "BUG: soft lockup - CPU#0 stuck for 61s!" problem. when i
> browsed through google, it appears to be general problem, but there is no
> workaround/solution exists. Any pointers how to trace this or fix this would
> be helpfu
16 matches
Mail list logo
