Hi,
Just to confirm, you're saying that the box has run fine for some
time, you've upgraded nothing (in terms of hardware), but now it's
started having problems?
Corrupt RAM can cause all sorts of headaches, to help eliminate that,
I'd nip over to www.memtest.org, grab the latest bootable iso and run
that for a few hours.
It's a good place to start.
Deepak Shrestha wrote:
Hi
My FC5 box recently behaving weired. It hangs sometimes but cannot
determine the cause yet. Its very random but not so frequent. Today
since I restarted the machine, I got the Kernel panic message during
boot time and freezed. Since I don't know a way to dump the screen
output, I copied by hand and here it is:
+++++++++++++++++++++++
printing eip:
*pde = 00000000
Oops: 0002 [#1]
last sysfs file:
Modules linked in :
CPU: 0
EIP: 0060:[<c042ac14>] Not tainted VLI
EFLAGS: 00010286 (2.6.18-1.2239.fc5 #1)
EIP is at rcu_process_callbacks+0x7/0x1e
eax: 00000000 ebx: 00000000 ecx: fffb6d90 edx: 8d00b280
esi: c0789768 edi: 0000000a ebp: 00000048 esp: c0759fe4
ds: 007b es: 007b ss: 0068
Process swapper (pid: 1, ti=c0759000 task=d7e015b0 task.ti=d7e23000)
Stack: c041ffe4 00000001 c04202be d7e23ce8 d7e23000 00000046 c04053c9
Call Trace:
[<c041ffe4>] tasklet_action+0x37/0x57
[<c04202be>] __do softirq+0x35/0x75
[<c04053c9>] do_softirq+0x3e/0x99
=======================
Code: 89 46 28 eb 1b 0f ba 2d 00 b3 78 c0 00 19 c0 85 c0 75 0d 5b b8
fc b2 78 c0 5e 5f e9 42 57 ff ff 5b 5e 5f c3 ba 80 b2 78 c0 b8 e0 <6c>
66 c0 e8 a6 fe ff ff ba c0 b2 78 c0 b8 00 6d 66 c0 e9 97 fe
EIP: [<c042ac14>] rcu_process_callbacks+0x7/0x1e SS:ESP 0068:c0759fe4
<0>Kernel panic - not syncing: Fatal exception in interrupt
++++++++++++++++++++++++
after reboot, I trid in /var/log/message and some relevant messages I
found is:
======================
Dec 3 10:26:27 zeesrvr kernel: hdd: DMA timeout error
Dec 3 10:26:27 zeesrvr kernel: hdd: dma timeout error: status=0x58 {
DriveReady SeekComplete DataRequest }
Dec 3 10:26:27 zeesrvr kernel: hdd: task_in_intr: error=0x04 {
DriveStatusError }
Dec 3 10:26:27 zeesrvr kernel: hdd: task_in_intr: error=0x04 {
DriveStatusError }
Dec 3 10:26:28 zeesrvr kernel: hdd: task_in_intr: error=0x04 {
DriveStatusError }
Dec 3 10:26:28 zeesrvr kernel: hdd: task_in_intr: error=0x04 {
DriveStatusError }
Dec 3 10:26:28 zeesrvr kernel: ide1: reset: master: error (0x7f?)
Dec 3 10:26:58 zeesrvr kernel: hdd: DMA timeout error
Dec 3 10:26:58 zeesrvr kernel: hdd: dma timeout error: status=0x58 {
DriveReady SeekComplete DataRequest }
Dec 3 10:27:30 zeesrvr kernel: hdd: DMA timeout error
Dec 3 10:27:30 zeesrvr kernel: hdd: dma timeout error: status=0x58 {
DriveReady SeekComplete DataRequest }
Dec 3 10:28:01 zeesrvr kernel: hdd: DMA timeout error
Dec 3 10:28:01 zeesrvr kernel: hdd: dma timeout error: status=0x58 {
DriveReady SeekComplete DataRequest }
Dec 4 01:35:20 zeesrvr kernel: hdd: DMA timeout error
Dec 4 01:35:20 zeesrvr kernel: hdd: dma timeout error: status=0x58 {
DriveReady SeekComplete DataRequest }
Dec 4 01:35:20 zeesrvr kernel: hdd: task_in_intr: error=0x04 {
DriveStatusError }
Dec 4 01:35:20 zeesrvr kernel: hdd: task_in_intr: error=0x04 {
DriveStatusError }
Dec 4 01:35:22 zeesrvr kernel: hdd: task_in_intr: error=0x04 {
DriveStatusError }
Dec 4 01:35:22 zeesrvr kernel: hdd: task_in_intr: error=0x04 {
DriveStatusError }
Dec 4 01:35:22 zeesrvr kernel: ide1: reset: master: error (0x7f?)
Dec 4 01:35:52 zeesrvr kernel: hdd: DMA timeout error
Dec 4 01:35:52 zeesrvr kernel: hdd: dma timeout error: status=0x58 {
DriveReady SeekComplete DataRequest }
Dec 4 01:36:23 zeesrvr kernel: hdd: DMA timeout error
Dec 4 01:36:23 zeesrvr kernel: hdd: dma timeout error: status=0x58 {
DriveReady SeekComplete DataRequest }
Dec 4 01:36:54 zeesrvr kernel: hdd: DMA timeout error
Dec 4 01:36:54 zeesrvr kernel: hdd: dma timeout error: status=0x58 {
DriveReady SeekComplete DataRequest }
=========================
I have three dirves currently mounted in this box.
1st is fedora itself (ext3) hda
2nd is backup of ISO images (ext3) hdb
3rd is various backup files (ext3) hdd
According to message it seems like something wrong with my 3rd drive
but couldn't determine why this problem is happening.
Is this Drive Error?
can somebody interpret this message for me? I can't figure out if this
is hardware related error or the Fedora itself?
Thanks
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
