udev: BUG: spinlock bad magic on CPU#0, udevd/447 (Tainted:P )

[Antonio Olivares]

Dear List Users,

I have successfully installed Fedora 5 on a
shuttleX machine, AMD 2700 XP processor.  I updated to
kernel-2.6.17-1.2157_FC5 and everything was working
beautifully and then all of a sudden the machine
froze.  Could not CTRL+ALT+BACKSPACE, could not
shutdown.  I was surfing the net and this happened.  I
decided to reset.  When I reset the machine it gave me
the message

Starting 
  udev:  BUG: spinlock bad magic on CPU#0, udevd/447  
(Tainted:P    )
 lock: c06e07d4, .magic: c06eo7d4, .owner:{weird
symbol goes here} ...
  Bug: spinlock lockup on CPU#0, udev/447 cobeo7d4
(Tainted:  P).

It stayed there leaving me no choice but to press and
hold the power button till it shutdown.  I let it stay
off for a little and I turned it back on and it let me
through with no error message as the previous one.

What does this error mean?

Is the CPU dying little by little?

Thanks for your valuable time,

Antonio

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

[John Wendel]

Antonio Olivares wrote:
> Dear List Users,
>
> I have successfully installed Fedora 5 on a
> shuttleX machine, AMD 2700 XP processor.  I updated to
> kernel-2.6.17-1.2157_FC5 and everything was working
> beautifully and then all of a sudden the machine
> froze.  Could not CTRL+ALT+BACKSPACE, could not
> shutdown.  I was surfing the net and this happened.  I
> decided to reset.  When I reset the machine it gave me
> the message
>
> Starting 
>   udev:  BUG: spinlock bad magic on CPU#0, udevd/447  
> (Tainted:P    )
>  lock: c06e07d4, .magic: c06eo7d4, .owner:{weird
> symbol goes here} ...
>   Bug: spinlock lockup on CPU#0, udev/447 cobeo7d4
> (Tainted:  P).
>
> It stayed there leaving me no choice but to press and
> hold the power button till it shutdown.  I let it stay
> off for a little and I turned it back on and it let me
> through with no error message as the previous one.
>
> What does this error mean?
>
> Is the CPU dying little by little?
>
> Thanks for your valuable time,
>
> Antonio

Your hardware is probably just fine. You've been bitten by a bad 
kernel version or bad video driver. Are you running ATI driver?

For your system (I have same one here), I'd build a plain vanilla, 
single CPU kernel with the tarball from kernel.org (2.6.17.7). Mine is 
rock solid with this version.

Just my 2 cents worth.

John

[Antonio Olivares]

--- John Wendel  wrote:
> Antonio Olivares wrote:
> > Dear List Users,
> >
> > I have successfully installed Fedora 5 on a
> > shuttleX machine, AMD 2700 XP processor.  I
>
> updated to
> > kernel-2.6.17-1.2157_FC5 and everything was
>
> working
> > beautifully and then all of a sudden the machine
> > froze.  Could not CTRL+ALT+BACKSPACE, could not
> > shutdown.  I was surfing the net and this
>
> happened.  I
> > decided to reset.  When I reset the machine it
>
> gave me
> > the message
> >
> > Starting 
> >   udev:  BUG: spinlock bad magic on CPU#0,
>
> udevd/447
> > (Tainted:P    )
> >  lock: c06e07d4, .magic: c06eo7d4, .owner:{weird
> > symbol goes here} ...
> >   Bug: spinlock lockup on CPU#0, udev/447 cobeo7d4
> > (Tainted:  P).
> >
> > It stayed there leaving me no choice but to press
>
> and
> > hold the power button till it shutdown.  I let it
>
> stay
> > off for a little and I turned it back on and it
>
> let me
> > through with no error message as the previous one.
> >
> > What does this error mean?
> >
> > Is the CPU dying little by little?
> >
> > Thanks for your valuable time,
> >
> > Antonio
>
> Your hardware is probably just fine. You've been
> bitten by a bad 
> kernel version or bad video driver. Are you running
> ATI driver?

No, it has via 8237 integrated video card.  Another
machine I have has ATI Radeon 7000 and it is working
fine.
> For your system (I have same one here), I'd build a
> plain vanilla, 
> single CPU kernel with the tarball from kernel.org
> (2.6.17.7). Mine is 
> rock solid with this version.
>
> Just my 2 cents worth.
>
> John
>
> -- 
> fedora-list mailing list
> [e-mail]
> To unsubscribe:
> https://www.redhat.com/mailman/listinfo/fedora-list

I'll cross my fingers and hope that this does not
happen.  If it happens, I'll follow your advice and
get a vanilla kernel.

Thanks,

Antonio

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

[James Wilkinson]

Antonio Olivares wrote:
> I have successfully installed Fedora 5 on a shuttleX machine, AMD
>    2700 XP processor.  I updated to kernel-2.6.17-1.2157_FC5 and
>    everything was working beautifully and then all of a sudden the
>    machine froze.  Could not CTRL+ALT+BACKSPACE, could not shutdown.
>    I was surfing the net and this happened.  I decided to reset.  When
>    I reset the machine it gave me the message
>
> Starting udev:  BUG: spinlock bad magic on CPU#0, udevd/447  (Tainted:P    )
> lock: c06e07d4, .magic: c06eo7d4, .owner:{weird symbol goes here} ...
> Bug: spinlock lockup on CPU#0, udev/447 cobeo7d4 (Tainted:  P).

That "Tainted: P" bit means a "proprietary module has been loaded". Has
it? You say:
> No, it has via 8237 integrated video card.  Another
> machine I have has ATI Radeon 7000 and it is working
> fine.

It's possible that you've got something like a VMWare module or
something else loaded. If so, and the problem repeats, try again without
the module loaded. (Kernel bugs can't be properly debugged without the
source code, including the source code to any proprietary modules).

Note that you'll have to stop the module loading at bootup -- merely
unloading it isn't good enough.

If you *haven't* loaded any proprietary drivers, then there's probably
something wrong with your PC's memory. Try memtest86 for starters.

Incidentally, putting something like "{weird symbol goes here}" in a bug
report can *really* *really* annoy whoever's trying to debug the
problem. Usually that's the one bit of data that they really need to
sort out what's going on.

Hope this helps,

James.