Re: Please explain system errors
On Sun, 2015-06-28 at 15:07 -0700, briand@aracnet.com wrote:
> On Mon, 29 Jun 2015 05:09:09 +0800
> Bret Busby <bret.busby@gmail.com> wrote:
>
> > Hello.
> >
> > After returning to this computer after a couple of hours, and
> > switching to the terminal session, I found this;
> >
> > "
> > r
> > root@bret-apc01-debian6:~#
> > Message from syslogd@bret-apc01-debian6 at Jun 29 02:32:30 ...
> > kernel:[ 5453.781521] Oops: 0000 [#1] SMP
> >
> > Message from syslogd@bret-apc01-debian6 at Jun 29 02:32:30 ...
> > kernel:[ 5453.781529] last sysfs file:
> > /sys/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/sda7/stat
> >
> > Message from syslogd@bret-apc01-debian6 at Jun 29 02:32:30 ...
> > kernel:[ 5453.781841] Stack:
> >
> > Message from syslogd@bret-apc01-debian6 at Jun 29 02:32:30 ...
> > kernel:[ 5453.781881] Call Trace:
> >
> > Message from syslogd@bret-apc01-debian6 at Jun 29 02:32:30 ...
> > kernel:[ 5453.781988] Code: fe 4c 89 ef ff 50 18 89 c3 83 7c 24 0c 00
> > 74 5a 85 db 74 53 44 89 fd 83 f5 12 eb 1e 49 8b 85 b0 02 00 00 49 63
> > d6 31 c9 4c 89 ef <48> 8b b4 d0 98 00 00 00 89 ea e8 e9 f8 ff ff 41 ff
> > ce 41 83 fe
> >
> > Message from syslogd@bret-apc01-debian6 at Jun 29 02:32:30 ...
> > kernel:[ 5453.782107] CR2: 0000000000000098
> > "
> >
> > Could someone please explain this for me?
> >
>
> well i can tell you that a kernel oops is a bad thing. some code the kernel was executing didn't do what it was supposed to.
>
> even, worse news, it looks like it was generated talking to sda, i.e., a disk drive (but i might be wrong, it's not clear to me).
>
> I don't think this is something you can ignore. I would download some sort of stress test program and let it run for a few hours. For memory there is a memtest86. I'm not sure it includes a disk access tester or not, it's been a while since i used it.
memtest86 only tests the RAM. It doesn't check disks.
> in fact, it's probably worth it to run memtest anyway, just to make sure that this isn't a memory problem which is the most common cause of oopses.
If (A) the issue occurs predictably and (B) you have spare RAM sticks
around that are compatible it might be easier to swap it out and see if
it resolves the issue.
If A or B is false, then you're best off using the memtest.
>
>
> Good luck.
>
>
> Brian
>
>
Reply to: