[ale] kernel message/Seg. fault

[I. Herman]

I think i figured it out.  It seems that the external USB drive i was  
using had some junk sectors on it.  I rebuilt the tree (ReiserFS) and  
all seems to be better now...still dunno jack bout the kernel "oops"  
tho.  Thanks for the response.

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.
>
> http://www.urbanmyth.org/linux/oops/slides.html
>
> 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
> http://www.ale.org/mailman/listinfo/ale
>