FC1 x86_64 oops

[Peter J. Stieber]

Hardware:
Motherboard: Tyan S2850 Tomcat K8S
  On board video: ATI RAGE XL PCI w/ 8MB video RAM
  On board network: dual Broadcom BCM5705 Gigabit Ethernet
RAM: 1GB
Processor: Opteron 146
HD: Maxtor 80GB 7200 RPM IDE ULTRA ATA133

Running FC1: 2.4.22-1.2188.nptl (x86_64)


I'm getting crash messages and I was wondering if someone could
tell me the cause? The system doesn't hang, but I'm worried. It seems
to have happened twice last night. The following was generated in
the terminal windows (logged in under GNOME).


Message from syslogd at localhost at Wed May 12 23:27:04 2004 ...
localhost kernel: Oops: 0000

Message from syslogd at localhost at Wed May 12 23:27:04 2004 ...
localhost kernel: RIP [<ffffffff80284890>]{strlen+0} RSP <000001002e6d37e0>

Message from syslogd at localhost at Wed May 12 23:27:04 2004 ...
localhost kernel: CR2: 0000000000000000

Message from syslogd at localhost at Thu May 13 03:47:51 2004 ...
localhost kernel: Oops: 0000

Message from syslogd at localhost at Thu May 13 03:47:51 2004 ...
localhost kernel: RIP [<ffffffff80284890>]{strlen+0} RSP <000001002359b7e0>

Message from syslogd at localhost at Thu May 13 03:47:51 2004 ...
localhost kernel: CR2: 0000000000000000


I have atteched /var/log/messages from this time period. Are the
"hda: dma_timer_expiry: dma status == 0x24" lines cause for concern?

I also have to core files that are only 64 bytes in the home directory
of the account that was logged in.

How can I tell what is causing the problem?

TIA,
Pete
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: messages.txt
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20040513/9dfc8209/attachment-0001.txt>