> > > I don't think it was supposed to do that.
> > >
> > > Quite possibly it's something to do with the new debugging code - could
> > you
> > > please take a copy of the offending config, send it over and then try
> > > removing debug options, see if the crash goes away? CONFIG_DEBUG_PREEM
"Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
>
> > I don't think it was supposed to do that.
> >
> > Quite possibly it's something to do with the new debugging code - could you
> > please take a copy of the offending config, send it over and then try
> > removing debug options, see if the cr
On Sunday, 7 of August 2005 19:23, Andrew Morton wrote:
> "Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
> >
> > I get the following Oops after trying to start nscd from YaST on an
> > Athlon64-based box
> > (compiled with CONFIG_DEBUG_SPINLOCK=y):
> >
> > Unable to handle kernel NULL pointer d
"Rafael J. Wysocki" <[EMAIL PROTECTED]> wrote:
>
> I get the following Oops after trying to start nscd from YaST on an
> Athlon64-based box
> (compiled with CONFIG_DEBUG_SPINLOCK=y):
>
> Unable to handle kernel NULL pointer dereference at 0008 RIP:
> {kmem_cache_alloc+232}
> PGD 1
Hi,
I get the following Oops after trying to start nscd from YaST on an
Athlon64-based box
(compiled with CONFIG_DEBUG_SPINLOCK=y):
Unable to handle kernel NULL pointer dereference at 0008 RIP:
{kmem_cache_alloc+232}
PGD 1501a067 PUD 1501b067 PMD 0
Oops: [1] PREEMPT
CPU 0
Module
5 matches
Mail list logo
