[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Errors



This message means that interrupts have been disabled for a 
long time (>0.1s). It seams unlikely that the Bluez stack 
would do this on purpose. You can try to disable the watchdog
in kernelconfig but probably the kernel will then hang 
instead because of the infinite loop. The watchdog prints
a kernel oops that can be used to decode where the software 
was looping.

Run something like ksymoops vmlinux -K -L -O -m System.map in
os/linux and copy paste the oops output.

/Mikael

-----Original Message-----
From: owner-dev-etrax@xxxxxxx.com">mailto:owner-dev-etrax@xxxxxxx.com] On
Behalf Of Murat Loo
Sent: Sunday, December 07, 2003 3:27 PM
To: dev-etrax
Subject: Errors



Hi,

We've compiled Bluez for developer board 82. However when we initiate a
device scan we get:

Oops: bitten by watchdog

What does this mean? Or sometimes the system reboots. What can cause
this?

Thanks in advance
Murat Loo


____________________________________________________________
Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail!
http://login.mail.lycos.com/r/referral?aid=27005