Skip to contentSkip to conversation

Ooops with kernel 2.4.22 and reiserfs

DISCUSSION Carlo 4 participants 9 messages Dec 22, 2003 – Dec 27, 2003

lore
Share & tools
lore

Carlo

author
#0 lore raw

Hi all,
i receive the follow message error when i delete file from a large partition (100GB) of an IDE drive (120GB) with reiserfs filesystem and kernel 2.4.22. Other partitions are EXT3.

I received this message several time in my test that erase jpeg files in nested directories.
May i increase the verbose of this error?

hda: set_drive_speed_status: status=0x58 { DriveReady SeekComplete DataRequest }
ide0: Drive 0 didn't accept speed setting. Oh, well.
hda: dma_intr: status=0x58 { DriveReady SeekComplete DataRequest }

hda: CHECK for good STATUS

Unable to handle kernel paging request at virtual address ffffffe0
 printing eip:
c0146553
*pde = 00002063
*pte = 00000000
Oops: 0000
CPU:    0
EIP:    0010:[<c0146553>]    Not tainted
EFLAGS: 00010213
eax: cded5f68   ebx: ffffffe0   ecx: cded5000   edx: 00000010
esi: 00000000   edi: cded5e40   ebp: cded5e68   esp: cb18bf24
ds: 0018   es: 0018   ss: 0018
Process rmdir (pid: 21907, stackpage=cb18b000)
Stack: 00000000 cded5e40 cded5e40 c2dfc340 cded5e40 bffffae8 c01465dd
cded5e40
       cded5e40 c013fa0f cded5e40 000001fe cb7d9040 c2dfc340 cded5e40
c018d840
       c013fb69 cded5e40 cded5d40 cb18bf9c 00000000 fffffff0 cded5e40
cded5e40
Call Trace:    [<c01465dd>] [<c013fa0f>] [<c018d840>] [<c013fb69>]

[<c013fc84>]
[<c0114d00>] [<c01088a3>]

Code: 8b 03 8b 36 85 c0 75 32 8d 4b 18 8b 51 04 8b 43 18 89 50 04

[]$ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 8
model name : AMD Athlon(tm) XP 2700+
stepping : 1
cpu MHz : 2158.060
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow
bogomips : 4299.16

#1 lore raw

Hello!

Carlo <[email protected]> wrote:
C> i receive the follow message error when i delete file from a large C> partition (100GB) of an IDE drive (120GB) with reiserfs filesystem and C> kernel 2.4.22. Other partitions are EXT3.
C> I received this message several time in my test that erase jpeg files in C> nested directories.

C> hda: set_drive_speed_status: status=0x58 { DriveReady SeekComplete C> DataRequest }
C> ide0: Drive 0 didn't accept speed setting. Oh, well.
C> hda: dma_intr: status=0x58 { DriveReady SeekComplete DataRequest } C> hda: CHECK for good STATUS

Do you always get these IDE errors prior to oops?

C> Unable to handle kernel paging request at virtual address ffffffe0 C> printing eip:
C> EIP: 0010:[<c0146553>] Not tainted
C> cded5e40
C> Call Trace: [<c01465dd>] [<c013fa0f>] [<c018d840>] [<c013fb69>]
C> [<c013fc84>]
C> [<c0114d00>] [<c01088a3>]

Also please run your oops through ksymoops.

Bye,
Oleg

author
#2 lore raw

Il lun, 2003-12-22 alle 23:05, Oleg Drokin ha scritto:

Quoted 9 lines

Hello!

C> hda: set_drive_speed_status: status=0x58 { DriveReady SeekComplete C> DataRequest }
C> ide0: Drive 0 didn't accept speed setting. Oh, well.
C> hda: dma_intr: status=0x58 { DriveReady SeekComplete DataRequest } C> hda: CHECK for good STATUS

Do you always get these IDE errors prior to oops?

No, on 6 oops only one has this error!

Quoted 1 line

C> Unable to handle kernel paging request at virtual address ffffffe0

............

Quoted 1 line

Also please run your oops through ksymoops.

ksymoops 2.4.4 on i686 2.4.22. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.22/ (default)
-m /boot/System.map-2.4.22-WE (specified)

Dec 22 19:23:57 webeye kernel: Unable to handle kernel paging request at
virtual address ffffffe0Dec 22 19:23:57 webeye kernel: c0146553
Dec 22 19:23:57 webeye kernel: *pde = 00002063
Dec 22 19:23:57 webeye kernel: Oops: 0000
Dec 22 19:23:57 webeye kernel: CPU:    0
Dec 22 19:23:57 webeye kernel: EIP:    0010:[<c0146553>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
Dec 22 19:23:57 webeye kernel: EFLAGS: 00010213
Dec 22 19:23:57 webeye kernel: eax: cbf85168   ebx: ffffffe0   ecx:
cbf85000   edx: 0000000f
Dec 22 19:23:57 webeye kernel: esi: 00000000   edi: cbf85f40   ebp:
cbf85f68   esp: c594df24
Dec 22 19:23:57 webeye kernel: ds: 0018   es: 0018   ss: 0018
Dec 22 19:23:57 webeye kernel: Process rmdir (pid: 11938,
stackpage=c594d000)
Dec 22 19:23:57 webeye kernel: Stack: 00000000 cbf85f40 cbf85f40

c6096b40 cbf85f40 bffffb18 c0146Dec 22 19:23:57 webeye kernel:
cbf85f40 c013fa0f cbf85f40 000001fe c6461540 c6096b40 cbf85Dec 22
19:23:57 webeye kernel: c013fb69 cbf85f40 cbf859c0 c594df9c
00000000 fffffff0 cbf85Dec 22 19:23:57 webeye kernel: Call Trace:
[<c01465dd>] [<c013fa0f>] [<c018d840>] [<c013fb69>]Dec 22 19:23:57
webeye kernel: [<c0114d00>] [<c01088a3>]

Dec 22 19:23:57 webeye kernel: Code: 8b 03 8b 36 85 c0 75 32 8d 4b 18 8b

51 04 8b 43 18 89 50 04

Quoted 1 line
Quoted 1 line

EIP; c0146553 <select_parent+33/a0> <=====

Trace; c01465dd <shrink_dcache_parent+1d/30>
Trace; c013fa0f <d_unhash+2f/50>
Trace; c018d840 <reiserfs_rmdir+0/270>
Trace; c013fb69 <vfs_rmdir+139/1c0>
Trace; c013fc84 <sys_rmdir+94/e0>
Trace; c0114d00 <do_page_fault+0/48c>
Trace; c01088a3 <system_call+33/38>
Code; c0146553 <select_parent+33/a0>
00000000 <_EIP>:
Code; c0146553 <select_parent+33/a0> <=====
0: 8b 03 mov (%ebx),%eax <=====
Code; c0146555 <select_parent+35/a0>
2: 8b 36 mov (%esi),%esi
Code; c0146557 <select_parent+37/a0>
4: 85 c0 test %eax,%eax
Code; c0146559 <select_parent+39/a0>
6: 75 32 jne 3a <_EIP+0x3a> c014658d
<select_parent+6d/a0>
Code; c014655b <select_parent+3b/a0>
8: 8d 4b 18 lea 0x18(%ebx),%ecx
Code; c014655e <select_parent+3e/a0>
b: 8b 51 04 mov 0x4(%ecx),%edx
Code; c0146561 <select_parent+41/a0>
e: 8b 43 18 mov 0x18(%ebx),%eax
Code; c0146564 <select_parent+44/a0>
11: 89 50 04 mov %edx,0x4(%eax)

I hope this is what you want. I had never use ksymoops before. This oops raise every time i use my program (a perl script that erase files).
If it's necessary i can send the full /var/log/messages passed through ksymoops with a lot of "Unable to handle kernel paging request at virtual address" but it's aboute 500Kb.

Thanks for your interest.

Marry Christmas :-)
Saluti Carlo!

Quoted 8 lines

Bye,
Oleg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#3 lore raw

Hello!

Quoted 7 lines · Carlo
Quoted 6 lines

C> hda: set_drive_speed_status: status=0x58 { DriveReady SeekComplete C> DataRequest }
C> ide0: Drive 0 didn't accept speed setting. Oh, well.
C> hda: dma_intr: status=0x58 { DriveReady SeekComplete DataRequest } C> hda: CHECK for good STATUS
Do you always get these IDE errors prior to oops?

No, on 6 oops only one has this error!

Ah, I see.

Quoted 11 lines
Quoted 1 line

C> Unable to handle kernel paging request at virtual address ffffffe0

............

Quoted 2 lines

Also please run your oops through ksymoops.

Quoted 1 line

EIP; c0146553 <select_parent+33/a0> <=====

Trace; c01465dd <shrink_dcache_parent+1d/30>
Trace; c013fa0f <d_unhash+2f/50>
Trace; c018d840 <reiserfs_rmdir+0/270>
Trace; c013fb69 <vfs_rmdir+139/1c0>
Trace; c013fc84 <sys_rmdir+94/e0>
Trace; c0114d00 <do_page_fault+0/48c>
Trace; c01088a3 <system_call+33/38>

Sounds like a list corruption to me.
Are you sure the memory in that box is ok?

Quoted 3 lines

If it's necessary i can send the full /var/log/messages passed through ksymoops with a lot of "Unable to handle kernel paging request at virtual address" but it's aboute 500Kb.

Run it through ksymoops and see if backtrace is different each time. Usually only first oops per boot is useful.
If backtrace is different each time, perhaps list all unique oopses?

Thank you.

Bye,
Oleg

author
#4 lore raw

Il mar, 2003-12-23 alle 16:20, Oleg Drokin ha scritto:

Quoted 3 lines

Sounds like a list corruption to me.
Are you sure the memory in that box is ok?

This PC has never gave memory problems and we use it in extensive mode.

Quoted 4 lines

Run it through ksymoops and see if backtrace is different each time. Usually only first oops per boot is useful.
If backtrace is different each time, perhaps list all unique oopses?

I run it several time with the same result.
I think thah it's a bug that is hardware dependant, because the same program on another PC with the same HW but different MainBoard run without problems

Quoted 1 line

Thank you.

Thank you too
Saluti Carlo!

Quoted 3 lines

Bye,
Oleg

#5 lore raw
In reply to Carlo
Quoted 9 lines · Carlo

Il lun, 2003-12-22 alle 23:05, Oleg Drokin ha scritto:

Quoted 8 lines

Hello!

C> hda: set_drive_speed_status: status=0x58 { DriveReady SeekComplete C> DataRequest }
C> ide0: Drive 0 didn't accept speed setting. Oh, well.
C> hda: dma_intr: status=0x58 { DriveReady SeekComplete DataRequest } C> hda: CHECK for good STATUS

I would check for SMARTerrors: smartctl -a /dev/hda Also you could try running badblocks on the drive.

regards,
dan carpenter

#6 lore raw
Quoted 9 lines
Quoted 6 lines
Quoted 6 lines

C> hda: set_drive_speed_status: status=0x58 { DriveReady SeekComplete C> DataRequest }
C> ide0: Drive 0 didn't accept speed setting. Oh, well.
C> hda: dma_intr: status=0x58 { DriveReady SeekComplete DataRequest } C> hda: CHECK for good STATUS

I would check for SMARTerrors: smartctl -a /dev/hda Also you could try running badblocks on the drive.

Run some drive self-tests:
smartctl -t long /dev/hda
and let them complete, then look again at
smartctl -a /dev/hda

Cheers,
Bruce

author
#7 lore raw

Il ven, 2003-12-26 alle 02:47, Bruce Allen ha scritto:

Quoted 7 lines
Quoted 7 lines
Quoted 6 lines
Quoted 6 lines

C> hda: set_drive_speed_status: status=0x58 { DriveReady SeekComplete C> DataRequest }
C> ide0: Drive 0 didn't accept speed setting. Oh, well.
C> hda: dma_intr: status=0x58 { DriveReady SeekComplete DataRequest } C> hda: CHECK for good STATUS

Quoted 8 lines
Quoted 2 lines

I would check for SMARTerrors: smartctl -a /dev/hda Also you could try running badblocks on the drive.

Run some drive self-tests:
smartctl -t long /dev/hda
and let them complete, then look again at
smartctl -a /dev/hda

smartctl version 5.26 Copyright (C) 2002-3 Bruce Allen Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===

Device Model:     Maxtor 6Y120L0
Serial Number:    Y3K9Q2GE
Firmware Version: YAR41BW0
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  ATA/ATAPI-7 T13 1532D revision 0
Local Time is:    Sat Dec 27 13:42:50 2003 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x80) Offline data collection activity was
never started.
Auto Offline Data Collection:
Enabled.
Self-test execution status: ( 0) The previous self-test routine
completed
without error or no self-test
has ever
been run.
Total time to complete Offline
1data collection: ( 242) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection
on/off support.
Suspend Offline collection upon
new
command.
Offline surface scan supported. Self-test supported. No Conveyance Self-test
supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode. Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
No General Purpose Logging
support.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 54) minutes.

SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
UPDATED WHEN_FAILED RAW_VALUE
3 Spin_Up_Time 0x0027 204 204 063 Pre-fail
Always - 5709
4 Start_Stop_Count 0x0032 253 253 000 Old_age
Always - 28
5 Reallocated_Sector_Ct 0x0033 253 253 063 Pre-fail
Always - 0
6 Read_Channel_Margin 0x0001 253 253 100 Pre-fail
Offline - 0
7 Seek_Error_Rate 0x000a 253 252 000 Old_age
Always - 0
8 Seek_Time_Performance 0x0027 251 245 187 Pre-fail
Always - 57965
9 Power_On_Minutes 0x0032 250 250 000 Old_age
Always - 1064h+20m
10 Spin_Retry_Count 0x002b 253 252 157 Pre-fail
Always - 0
11 Calibration_Retry_Count 0x002b 253 252 223 Pre-fail
Always - 0
12 Power_Cycle_Count 0x0032 253 253 000 Old_age
Always - 53
192 Power-Off_Retract_Count 0x0032 253 253 000 Old_age
Always - 0
193 Load_Cycle_Count 0x0032 253 253 000 Old_age
Always - 0
194 Temperature_Celsius 0x0032 253 253 000 Old_age
Always - 31
195 Hardware_ECC_Recovered 0x000a 253 252 000 Old_age
Always - 6759
196 Reallocated_Event_Count 0x0008 253 253 000 Old_age
Offline - 0
197 Current_Pending_Sector 0x0008 253 253 000 Old_age
Offline - 0
198 Offline_Uncorrectable 0x0008 253 253 000 Old_age
Offline - 0
199 UDMA_CRC_Error_Count 0x0008 199 199 000 Old_age
Offline - 0
200 Multi_Zone_Error_Rate 0x000a 253 252 000 Old_age
Always - 0
201 Soft_Read_Error_Rate 0x000a 253 248 000 Old_age
Always - 2
202 TA_Increase_Count 0x000a 253 252 000 Old_age
Always - 0
203 Run_Out_Cancel 0x000b 253 252 180 Pre-fail
Always - 0
204 Shock_Count_Write_Opern 0x000a 253 252 000 Old_age
Always - 0
205 Shock_Rate_Write_Opern 0x000a 253 252 000 Old_age
Always - 0
207 Spin_High_Current 0x002a 253 252 000 Old_age
Always - 0
208 Spin_Buzz 0x002a 253 252 000 Old_age
Always - 0
209 Offline_Seek_Performnce 0x0024 197 197 000 Old_age
Offline - 0
99 Unknown_Attribute 0x0004 253 253 000 Old_age
Offline - 0
100 Unknown_Attribute 0x0004 253 253 000 Old_age
Offline - 0
101 Unknown_Attribute 0x0004 253 253 000 Old_age
Offline - 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining
LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00%
997 -

Some ideas??

Saluti Carlo!

Quoted 4 lines

Cheers,
Bruce

#8 lore raw
Quoted 12 lines
Quoted 5 lines

Run some drive self-tests:
smartctl -t long /dev/hda
and let them complete, then look again at
smartctl -a /dev/hda

smartctl version 5.26 Copyright (C) 2002-3 Bruce Allen Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===

Device Model:     Maxtor 6Y120L0
Serial Number:    Y3K9Q2GE
Firmware Version: YAR41BW0

<snip>

Quoted 10 lines

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining
LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00%
997 -

Some ideas??

The only contribution I can make to this discussion is to suggest that 'your problem is not due to the drive': it doesn't exhibit any of the symptoms of a sick Maxtor disk.

Bruce