LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices


Reply
  Search this Thread
Old 01-26-2005, 11:25 AM   #1
Shalle
LQ Newbie
 
Registered: Jan 2005
Posts: 2

Rep: Reputation: 0
Kernel / Reiserfs fault..


This is the case.

I took alook at my syslog and found this:

Code:
Jan 25 15:46:55 shaolin kernel: hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 25 15:46:55 shaolin kernel: hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 25 18:52:14 shaolin kernel: hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 25 18:52:14 shaolin kernel: hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 25 18:57:17 shaolin kernel: hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 25 18:57:17 shaolin kernel: hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 25 19:04:16 shaolin kernel: hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 25 19:04:16 shaolin kernel: hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 25 19:08:37 shaolin kernel: hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 25 19:08:37 shaolin kernel: hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 25 19:10:23 shaolin kernel: hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 25 19:10:23 shaolin kernel: hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 25 19:10:24 shaolin kernel: hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 25 19:10:24 shaolin kernel: hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 25 19:10:49 shaolin kernel: hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 25 19:10:49 shaolin kernel: hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 25 19:10:49 shaolin kernel: hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 25 19:10:49 shaolin kernel: hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 25 19:10:49 shaolin kernel: hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 25 19:10:49 shaolin kernel: hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 25 19:11:10 shaolin kernel: hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 25 19:11:10 shaolin kernel: hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 25 19:11:10 shaolin kernel: hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 25 19:11:10 shaolin kernel: hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 25 19:11:10 shaolin kernel: hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 25 19:11:10 shaolin kernel: hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 25 19:11:10 shaolin kernel: hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 25 19:11:10 shaolin kernel: hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 25 19:11:10 shaolin kernel: ide1: reset: success
Jan 25 19:33:48 shaolin kernel: spurious 8259A interrupt: IRQ7.
Jan 26 05:42:55 shaolin kernel: hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Jan 26 05:42:55 shaolin kernel: hdd: dma_intr: error=0x84 { DriveStatusError BadCRC }
Jan 26 08:16:13 shaolin kernel: REISERFS: panic (device Null superblock): reiserfs[25835]: assertion !( ! (((((p_s_search_path))->path_elements +((p_s_search_path)->path_length))->pe_position)) ) failed at fs/reiserfs/stree.c:881:search_for_position_by_key: PAP-5170: position equals zero
Jan 26 08:16:13 shaolin kernel: 
Jan 26 08:16:13 shaolin kernel: ------------[ cut here ]------------
Jan 26 08:16:13 shaolin kernel: kernel BUG at fs/reiserfs/prints.c:362!
Jan 26 08:16:13 shaolin kernel: invalid operand: 0000 [#1]
Jan 26 08:16:13 shaolin kernel: PREEMPT 
Jan 26 08:16:13 shaolin kernel: Modules linked in:
Jan 26 08:16:13 shaolin kernel: CPU:    0
Jan 26 08:16:13 shaolin kernel: EIP:    0060:[<c01a10bd>]    Not tainted
Jan 26 08:16:13 shaolin kernel: EFLAGS: 00010282   (2.6.8.1) 
Jan 26 08:16:13 shaolin kernel: EIP is at reiserfs_panic+0x51/0x76
Jan 26 08:16:13 shaolin kernel: eax: 00000105   ebx: c0311c5d   ecx: c035b9f8   edx: c035b9f8
Jan 26 08:16:13 shaolin kernel: esi: 00000000   edi: 0000012c   ebp: 00000160   esp: d2c4e874
Jan 26 08:16:13 shaolin kernel: ds: 007b   es: 007b   ss: 0068
Jan 26 08:16:13 shaolin kernel: Process fsavd (pid: 25835, threadinfo=d2c4e000 task=da707870)
Jan 26 08:16:13 shaolin kernel: Stack: c031d500 c0311c5d c040c880 dffb9400 d2c4e97c d2c4e97c c01ab838 00000000 
Jan 26 08:16:13 shaolin kernel:        c0322d80 000064eb 00000371 c0301df7 00000001 00000000 00010046 00001000 
Jan 26 08:16:13 shaolin kernel:        c0400000 c0105a98 00000000 c03d6a00 00000001 c035b748 c03d6a00 00000000 
Jan 26 08:16:13 shaolin kernel: Call Trace:
Jan 26 08:16:13 shaolin kernel:  [<c01ab838>] search_for_position_by_key+0x3f0/0x499
Jan 26 08:16:13 shaolin kernel:  [<c0105a98>] do_IRQ+0x155/0x1a8
Jan 26 08:16:13 shaolin kernel:  [<c018f2d0>] make_cpu_key+0x59/0x65
Jan 26 08:16:13 shaolin kernel:  [<c018f834>] _get_block_create_0+0x486/0x73f
Jan 26 08:16:13 shaolin kernel:  [<c019130e>] reiserfs_get_block+0x152e/0x159f
Jan 26 08:16:13 shaolin kernel:  [<c0263908>] ide_dma_intr+0x0/0xaf
Jan 26 08:16:13 shaolin kernel:  [<c0263dff>] dma_timer_expiry+0x0/0x81
Jan 26 08:16:13 shaolin kernel:  [<c0260ee9>] do_rw_taskfile+0x1b0/0x25f
Jan 26 08:16:13 shaolin kernel:  [<c012f8ea>] mempool_alloc+0x75/0x166
Jan 26 08:16:13 shaolin kernel:  [<c0111dcc>] autoremove_wake_function+0x0/0x57
Jan 26 08:16:13 shaolin kernel:  [<c0242f39>] as_update_arq+0x2e/0x78
Jan 26 08:16:13 shaolin kernel:  [<c0243c10>] as_add_request+0x1a8/0x20e
Jan 26 08:16:13 shaolin kernel:  [<c023badd>] __elv_add_request+0x45/0x9e
Jan 26 08:16:13 shaolin kernel:  [<c023ea3f>] __make_request+0x2d4/0x541
Jan 26 08:16:13 shaolin kernel:  [<c014b8cb>] __find_get_block+0x72/0x103
Jan 26 08:16:13 shaolin kernel:  [<c0149f7c>] wake_up_buffer+0x13/0x39
Jan 26 08:16:13 shaolin kernel:  [<c01a8e6b>] is_tree_node+0x6f/0x71
Jan 26 08:16:13 shaolin kernel:  [<c01aa2d2>] search_by_key+0x13c2/0x2538
Jan 26 08:16:13 shaolin kernel:  [<c0111dcc>] autoremove_wake_function+0x0/0x57
Jan 26 08:16:13 shaolin kernel:  [<c0111dfb>] autoremove_wake_function+0x2f/0x57
Jan 26 08:16:13 shaolin kernel:  [<c0169bca>] do_mpage_readpage+0x147/0x484
Jan 26 08:16:13 shaolin kernel:  [<c02639f4>] ide_build_sglist+0x3d/0x9f
Jan 26 08:16:13 shaolin kernel:  [<c01feb57>] radix_tree_node_alloc+0x1f/0x5a
Jan 26 08:16:13 shaolin kernel:  [<c01fede5>] radix_tree_insert+0xe5/0x105
Jan 26 08:16:13 shaolin kernel:  [<c012c69e>] add_to_page_cache+0x69/0xaf
Jan 26 08:16:13 shaolin kernel:  [<c016a046>] mpage_readpages+0x13f/0x16c
Jan 26 08:16:13 shaolin kernel:  [<c018fde0>] reiserfs_get_block+0x0/0x159f
Jan 26 08:16:13 shaolin kernel:  [<c0133604>] read_pages+0x136/0x13f
Jan 26 08:16:13 shaolin kernel:  [<c018fde0>] reiserfs_get_block+0x0/0x159f
Jan 26 08:16:13 shaolin kernel:  [<c0130ce0>] __alloc_pages+0x2f7/0x36e
Jan 26 08:16:13 shaolin kernel:  [<c0133902>] do_page_cache_readahead+0x10a/0x197
Jan 26 08:16:13 shaolin kernel:  [<c0133a94>] page_cache_readahead+0x105/0x1eb
Jan 26 08:16:13 shaolin kernel:  [<c012cf33>] do_generic_mapping_read+0xf9/0x4b4
Jan 26 08:16:13 shaolin kernel:  [<c012d5d3>] __generic_file_aio_read+0x1f3/0x225
Jan 26 08:16:13 shaolin kernel:  [<c012d2ee>] file_read_actor+0x0/0xf2
Jan 26 08:16:13 shaolin kernel:  [<c01bbcc1>] reiserfs_permission+0x27/0x2b
Jan 26 08:16:13 shaolin kernel:  [<c012d6fd>] generic_file_read+0x84/0x9c
Jan 26 08:16:13 shaolin kernel:  [<c0148149>] filp_open+0x62/0x64
Jan 26 08:16:13 shaolin kernel:  [<c0148d16>] vfs_read+0xb0/0x119
Jan 26 08:16:13 shaolin kernel:  [<c0148f96>] sys_read+0x51/0x80
Jan 26 08:16:13 shaolin kernel:  [<c0103eab>] syscall_call+0x7/0xb
Jan 26 08:16:13 shaolin kernel: Code: 0f 0b 6a 01 ea 21 31 c0 85 f6 c7 44 24 08 80 c8 40 c0 c7 04
I have no idea what it is =/

Im running Slackware 10 with kernel version 2.6.8.1.
ReiserFs on both my harddrives..

If anyone could help me I would be most gratefull.
 
Old 01-26-2005, 01:58 PM   #2
BajaNick
Senior Member
 
Registered: Jul 2003
Location: So. Cal.
Distribution: Slack 11
Posts: 1,737

Rep: Reputation: 46
Assuming your main drive is /dev/hda1, You might want to try this:

hdparm -d /dev/hda1

Does it show dma on ?

Last edited by BajaNick; 01-26-2005 at 02:00 PM.
 
Old 01-26-2005, 02:25 PM   #3
Matir
LQ Guru
 
Registered: Nov 2004
Location: San Jose, CA
Distribution: Ubuntu
Posts: 8,507

Rep: Reputation: 124Reputation: 124
I saw errors like that on my ext3fs SATA hard drive last week. The next day, the drive wouldn't do anything at all. I've seen those errors on 3 other hard drives, and all had hardware failures within a reasonably short period of time: anywhere from a day to a month.
 
Old 01-31-2005, 02:08 PM   #4
Shalle
LQ Newbie
 
Registered: Jan 2005
Posts: 2

Original Poster
Rep: Reputation: 0
Quote:
Originally posted by BajaNick
Assuming your main drive is /dev/hda1, You might want to try this:

hdparm -d /dev/hda1

Does it show dma on ?

Yes it does..


# hdparm -d /dev/hdd1

/dev/hdd1:
using_dma = 1 (on)
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
reiserfs kernel panic ncf Slackware 31 06-22-2005 02:29 PM
2.6.0 kernel not liking ReiserFS very much... froguy Linux - Software 3 01-11-2004 12:18 PM
Kernel 2.6, RAID-1 & reiserfs kernel panic Raptor Ramjet Slackware 2 01-04-2004 08:25 AM
Virtual Machine kernel stack fault in kernel mode virtical Linux - Software 0 07-14-2003 09:30 PM
Kernel 2.4.2 doesn't support Reiserfs? Citizen Bleys Linux - General 0 03-27-2001 07:10 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 02:56 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration