[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- <!--x-content-type: text/plain -->
- <!--x-date: Sat, 30 Jul 2005 21:42:27 -0400 -->
- <!--x-from-r13: havpeba ng znqubevmbaf.pbz (W. Vrezna) -->
- <!--x-message-id: C52158F3-39B9-44D0-857C-[email protected] -->
- <!--x-reference: [email protected] -->
- <!--x-reference: [email protected] --> "http://www.w3.org/TR/html4/loose.dtd">
- <!--x-subject: [ale] kernel message/Seg. fault -->
- <li><em>date</em>: Sat, 30 Jul 2005 21:42:27 -0400</li>
- <li><em>from</em>: unicron at madhorizons.com (I. Herman)</li>
- <li><em>in-reply-to</em>: <<a href="msg00425.html">[email protected]</a>></li>
- <li><em>references</em>: <<a href="msg00398.html">[email protected]</a>> <<a href="msg00425.html">[email protected]</a>></li>
- <li><em>subject</em>: [ale] kernel message/Seg. fault</li>
Izzie
On Jul 29, 2005, at 8:02 AM, Geoffrey wrote:
> unicron at madhorizons.com wrote:
>
>> Some of you more seasoned folks...can you help me decipher this one:
>>
>
> 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
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> <a rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale";>http://www.ale.org/mailman/listinfo/ale</a>
>
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--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>
<li><strong><a name="00425" href="msg00425.html">[ale] kernel message/Seg. fault</a></strong>
<ul><li><em>From:</em> esoteric at 3times25.net (Geoffrey)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00437.html">[ale] Anyone have a spare gmail invite?</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00439.html">[ale] [/.] Novell give SCO the big one</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00425.html">[ale] kernel message/Seg. fault</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00401.html">[ale] Versioning backup solution</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00438"><strong>Date</strong></a></li>
<li><a href="threads.html#00438"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>