[no subject]

It's ugly when you get an oops.  If you're into kernel hacking, you can 
decode the oops with ksymoops.  Here's a pretty good link to oops debugging.

<a  rel="nofollow" href="http://www.urbanmyth.org/linux/oops/slides.html";>http://www.urbanmyth.org/linux/oops/slides.html</a>

The thing is, an oops is a bug in kernel code, usually.  It can be 
caused by faulty hardware though.

Unless you're pretty good at kernel debugging, it's best left to someone 
else.  If you know what device or process caused the oops, you can 
forward the output of ksymoops to them and they will determine if it's 
code or something else.

-- 
Until later, Geoffrey


</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="00438" href="msg00438.html">[ale] kernel message/Seg. fault</a></strong>
<ul><li><em>From:</em> unicron at madhorizons.com (I. Herman)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00398" href="msg00398.html">[ale] kernel message/Seg. fault</a></strong>
<ul><li><em>From:</em> unicron at madhorizons.com (unicron at madhorizons.com)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00424.html">[ale] Flat file post-processing - drop records based on</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00426.html">[ale] MP3's over the modem</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00398.html">[ale] kernel message/Seg. fault</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00438.html">[ale] kernel message/Seg. fault</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00425"><strong>Date</strong></a></li>
<li><a href="threads.html#00425"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>