lkml.org 
[lkml]   [2004]   [Jan]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.6.1-mm2
Andrew Morton wrote:
> "Prakash K. Cheemplavam" <PrakashKC@gmx.de> wrote:
>
>>>>kernel: Badness in pci_find_subsys at drivers/pci/search.c:132
>>>>
>>>>Any ideas? Or do you need detailed kernel config and dmesg? I thought
>>>>you might have an idea which atch caused this... My and his system are
>>>>quite differnt. Major Common element seems only use of Athlon XP. He has
>>>>VIA KT based system and I have nforce2. I thought it might be APIC, but
>>>>I also got a lock up without APIC. (Though it seems more stable without
>>>>APIC.)
>>>
>>>
>>>If you could send us the stack backtrace that would help. Make sure that
>>>you have CONFIG_KALLSYMS enabled. If you have to type it by hand, just the
>>>symbol names will suffice - leave out the hex numbers.
>>
>>Sorry, I am a noob about such things. Above option is enabled in my
>>config, but I dunno how get the stack backtrace. Could you point to me
>>to something helpful?
>
>
> When the kernel prints that `badness' message it then prints a stack
> backtrace. That's what we want.

But how to get that? When the machine locks up, I don't see anything
written and only *sometimes* I got above message in the log -whcih I
can only see afterwards. But there is nothing else realted to it in the
log...

Prakash
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:00    [W:1.060 / U:0.476 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site