Hi all,
For the past 24 hours, my system has been oopsing every so often. The
problem is not reproducible on command, but it does seem to be inevitable
after a few hours. I can't seem to get through a kernel compile without it
happening.
In the first oops attachment, the Enlightenment WM was doing something when
the oops happened.
In the second oops attachment, I had rebooted and used WindowMaker instead
of Enlightenment just to make sure there wasn't something about
Enlightenment that was causing the problem. I downloaded 2.6.11 and was in
the process of making a new kernel when the oops happened. I believe that
the bash invocation for the make caused the oops.
I never had this problem before. It appears to have started after a Debian
update (I use Debian/testing), but perhaps the update just coincided with
hardware failure. The system is an aging dual Celeron PII/333.
I've never sent in an oops report before. From oops-tracing.txt, man
ksymoops and the ksymoops output, I need /proc/ksyms, but it appears that
file has disappeared from the kernel. However, judging by the actual text
of the oops report, it appears that the object translation was performed
automatically. I'm seeing things that look like function names, so perhaps
the man page, oops-tracing.txt, and ksymoops output are all out of date?
Pete
--
Every theory is killed sooner or later, but if the theory has good in it,
that good is embodied and continued in the next theory. -- Albert Einstein
GPG Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D
On Mon, 2005-05-09 at 13:24 -0400, Peter Jay Salzman wrote:
> I've never sent in an oops report before. From oops-tracing.txt, man
> ksymoops and the ksymoops output, I need /proc/ksyms, but it appears that
> file has disappeared from the kernel. However, judging by the actual text
> of the oops report, it appears that the object translation was performed
> automatically. I'm seeing things that look like function names, so perhaps
> the man page, oops-tracing.txt, and ksymoops output are all out of date?
Yes, they are. I finally posted a patch which corrects the docs, post
2.6.11.
Anyway these two traces appear to have nothing to do with one another.
Random Oopses like this usually indicate failing hardware. Try memtest.
Lee