Skip to contentSkip to conversation

Poor performance during disk writes

DISCUSSION jlm 8 participants 12 messages Dec 18, 2001 – Dec 21, 2001

lore
Share & tools
lore

jlm

author
#0 lore raw

I have been witnessing what I believe to be poor performance from my computer ever since I have moved into the 2.4.x kernel versions. Combing through the unofficial archives of this mailing list reveals some others having similar problems, but I haven't seen any real resolution, or maybe their problems are completely different than mine.

The problem simply is that whenever the computer does a big disk write, everything else is put on hold. Maybe this isn't a problem, but just the way it was written. I have tested this on a 2.2.x kernel and it also does it, but to a much lesser extent, to the point that I noticed the performance loss in the upgrade to a 2.4.x kernel and decided to investigate further.

But also, I do not have any performance problems with disk reads. Programs can be loading up all they want and I am able to use my computer for other things during that time. It just seems to me (maybe I'm wrong) that the computer should be able to send small bits of data to the disk for writing during the off cycles and not affect the rest of the system (which is what I imagine it is doing for reads).

To test, I've got a 142Meg file. I copy it around, makeing sure to copy from one disk to another. Of course the copy goes fine, because it does a cache (as I've been reading here), but eventually it needs to write out to disk (or when I do a sync) and here is where the computer hangs for a bit. If an mp3 is playing, it halts for 5 seconds at a time, mouse movement on the screen is VERY jerky, Gkrellm will stop updating for seconds and even just in console I can't type in stuff for a bit.

I've been using hdparm to try and tweak hard disk access, but I'm not so sure this is the problem, and it's making me more confused about the entire situation. hdparm doesn't allow me to set using_dma, which it seems ought to be a necessity for getting a decent speed out of your hard drives (not that speed is the problem here), but despite that I still get a 51MB/s cache read speed in testing. Confusing, is the hard drive using (u)dma or not? Also, unmaskirq masks things a bit slower.

So, the questions: Is there a way for me to stop this, some configure option? Is it a bug/performance issue that needs to be addressed in the kernel? Should I just go back to the 2.2.x kernel series and shutup already?

I'm running 3 hard drives (30G Maxtor, 20G Seagate, and 2.1G Quantum Fireball) on an AMD k6-2 3dnow with a Gigabyte GA-5AX MOBO and the ALI Aladin V chipset.

Thanks for your time and let me know if you need any more info/ output from dmesg or something.

Signature · 3 lines
MACINTOSH = Machine Always Crashes If Not The Operating System Hangs
"Life would be so much easier if we could just look at the source code."
- Dave Olson
#1 lore raw
Quoted 6 lines

So, the questions: Is there a way for me to stop this, some configure option? Is it a bug/performance issue that needs to be addressed in the kernel? Should I just go back to the 2.2.x kernel series and shutup already?

Quoted 6 lines

I'm running 3 hard drives (30G Maxtor, 20G Seagate, and 2.1G Quantum Fireball) on an AMD k6-2 3dnow with a Gigabyte GA-5AX MOBO and the ALI Aladin V chipset.

Thanks for your time and let me know if you need any more info/ output from dmesg or something.

Specific kernel version, df, & hdparm output would all be helpful.

Quoted 1 line

- Dave Olson

Regards,
Reid

author
#2 lore raw
Quoted 1 line · Reid Hekman

Specific kernel version, df, & hdparm output would all be helpful.

/usr 24> uname -a
Linux PC2 2.4.16 #1 Sun Dec 2 15:26:09 EST 2001 i586 unknown /usr 25> df .
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hdb1 6047724 3472788 2267728 61% /usr
/usr 26> hdparm -I /dev/hdb

/dev/hdb:

non-removable ATA device, with non-removable media

        Model Number:           ST320413A                               
        Serial Number:          6ED2305M            
        Firmware Revision:      3.39    

Standards:
Supported: 1 2 3 4 5
Likely used: 5
Configuration:

        Logical         max     current
        cylinders       16383   16383
        heads           16      16
        sectors/track   63      63
        bytes/track:    0               (obsolete)
        bytes/sector:   0               (obsolete)

current sector capacity: 16514064
LBA user addressable sectors = 39102336
Capabilities:
LBA, IORDY(can be disabled)
Buffer size: 512.0kB Queue depth: 1
Standby timer values: spec'd by standard
r/w multiple sector transfer: Max = 16 Current = 16
DMA: mdma0 mdma1 *mdma2 udma0 udma1 udma2 udma3 udma4 udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=240ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* READ BUFFER cmd
* WRITE BUFFER cmd
* Host Protected Area feature set
* look-ahead
* write cache
* Power Management feature set
Security Mode feature set
SMART feature set
SET MAX security extension
* DOWNLOAD MICROCODE cmd
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
HW reset results:
CBLID- above Vih
Device num = 1
Checksum: correct

My hdb hard drive is where I found the problem originally. Also, I'm running the ext2 filesystem.

Signature · 3 lines
MACINTOSH = Machine Always Crashes If Not The Operating System Hangs
"Life would be so much easier if we could just look at the source code."
- Dave Olson
#3 lore raw
Quoted 5 lines · jlm
Quoted 1 line · Reid Hekman

Specific kernel version, df, & hdparm output would all be helpful.

/usr 24> uname -a
Linux PC2 2.4.16 #1 Sun Dec 2 15:26:09 EST 2001 i586 unknown

Is PCI IDE support for your chipset compiled in? PCI DMA by default?

Quoted 4 lines

non-removable ATA device, with non-removable media

        Model Number:           ST320413A                               
        Serial Number:          6ED2305M            
        Firmware Revision:      3.39    

[...]

Quoted 7 lines

Capabilities:
LBA, IORDY(can be disabled)
Buffer size: 512.0kB Queue depth: 1
Standby timer values: spec'd by standard
r/w multiple sector transfer: Max = 16 Current = 16
DMA: mdma0 mdma1 *mdma2 udma0 udma1 udma2 udma3 udma4 udma5
Cycle time: min=120ns recommended=120ns

Can you set udma on the drive instead?

Quoted 1 line

- Dave Olson

Regards,
Reid

#4 lore raw
In reply to jlm

File './Bonnie.2276', size: 1073741824, volumes: 1

Writing with putc()...  done:  72692 kB/s  83.7 %CPU
Rewriting...            done:  25355 kB/s  12.0 %CPU
Writing intelligently...done: 103022 kB/s  40.5 %CPU
Reading with getc()...  done:  37188 kB/s  67.5 %CPU
Reading intelligently...done:  40809 kB/s  11.4 %CPU
Seeker 2...Seeker 1...Seeker 3...start 'em...done...done...done...
              ---Sequential Output (nosync)--- ---Sequential Input-- --Rnd Seek-
              -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --04k (03)-
Machine    MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU   /sec %CPU
       1*1024 72692 83.7 103022 40.5 25355 12.0 37188 67.5 40809 11.4  382.1  2.4

Maybe this is the kind of performance you want out your ATA subsystem. Maybe if I could get a patch in to the kernels we could all have stable and fast IO.

Regards,

Andre Hedrick
CEO/President, LAD Storage Consulting Group
Linux ATA Development
Linux Disk Certification Project

Quoted 59 lines · jlm

I have been witnessing what I believe to be poor performance from my computer ever since I have moved into the 2.4.x kernel versions. Combing through the unofficial archives of this mailing list reveals some others having similar problems, but I haven't seen any real resolution, or maybe their problems are completely different than mine.

The problem simply is that whenever the computer does a big disk write, everything else is put on hold. Maybe this isn't a problem, but just the way it was written. I have tested this on a 2.2.x kernel and it also does it, but to a much lesser extent, to the point that I noticed the performance loss in the upgrade to a 2.4.x kernel and decided to investigate further.

But also, I do not have any performance problems with disk reads. Programs can be loading up all they want and I am able to use my computer for other things during that time. It just seems to me (maybe I'm wrong) that the computer should be able to send small bits of data to the disk for writing during the off cycles and not affect the rest of the system (which is what I imagine it is doing for reads).

To test, I've got a 142Meg file. I copy it around, makeing sure to copy from one disk to another. Of course the copy goes fine, because it does a cache (as I've been reading here), but eventually it needs to write out to disk (or when I do a sync) and here is where the computer hangs for a bit. If an mp3 is playing, it halts for 5 seconds at a time, mouse movement on the screen is VERY jerky, Gkrellm will stop updating for seconds and even just in console I can't type in stuff for a bit.

I've been using hdparm to try and tweak hard disk access, but I'm not so sure this is the problem, and it's making me more confused about the entire situation. hdparm doesn't allow me to set using_dma, which it seems ought to be a necessity for getting a decent speed out of your hard drives (not that speed is the problem here), but despite that I still get a 51MB/s cache read speed in testing. Confusing, is the hard drive using (u)dma or not? Also, unmaskirq masks things a bit slower.

So, the questions: Is there a way for me to stop this, some configure option? Is it a bug/performance issue that needs to be addressed in the kernel? Should I just go back to the 2.2.x kernel series and shutup already?

I'm running 3 hard drives (30G Maxtor, 20G Seagate, and 2.1G Quantum Fireball) on an AMD k6-2 3dnow with a Gigabyte GA-5AX MOBO and the ALI Aladin V chipset.

Thanks for your time and let me know if you need any more info/ output from dmesg or something.

Signature · 9 lines
MACINTOSH = Machine Always Crashes If Not The Operating System Hangs
"Life would be so much easier if we could just look at the source code."
- Dave Olson

-
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/
#5 lore raw
Quoted 12 lines · Andre Hedrick

File './Bonnie.2276', size: 1073741824, volumes: 1

Writing with putc()...  done:  72692 kB/s  83.7 %CPU
Rewriting...            done:  25355 kB/s  12.0 %CPU
Writing intelligently...done: 103022 kB/s  40.5 %CPU
Reading with getc()...  done:  37188 kB/s  67.5 %CPU
Reading intelligently...done:  40809 kB/s  11.4 %CPU
Seeker 2...Seeker 1...Seeker 3...start 'em...done...done...done...
              ---Sequential Output (nosync)--- ---Sequential Input-- --Rnd Seek-
              -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --04k (03)-
Machine    MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU   /sec %CPU
       1*1024 72692 83.7 103022 40.5 25355 12.0 37188 67.5 40809 11.4  382.1  2.4
Quoted 3 lines

Maybe this is the kind of performance you want out your ATA subsystem. Maybe if I could get a patch in to the kernels we could all have stable and fast IO.

I rather see lots of wasting rather than performance, here. Bonnie says that your subsystem can sustain 103 MB/s write but only 41 MB/s read. This looks about 60% throughput wasted for read.

Note that if you intend to use it only for write-only applications, performance are not that bad, even if just dropping the data on the floor would give you infinite throughput without any difference in functionnality. :-)

Gérard Roudier
Not CEO, not President of anything.

Quoted 7 lines

Regards,

Andre Hedrick
CEO/President, LAD Storage Consulting Group
Linux ATA Development
Linux Disk Certification Project

#6 lore raw
Quoted 20 lines · Gérard Roudier
Quoted 12 lines · Andre Hedrick

File './Bonnie.2276', size: 1073741824, volumes: 1

Writing with putc()...  done:  72692 kB/s  83.7 %CPU
Rewriting...            done:  25355 kB/s  12.0 %CPU
Writing intelligently...done: 103022 kB/s  40.5 %CPU
Reading with getc()...  done:  37188 kB/s  67.5 %CPU
Reading intelligently...done:  40809 kB/s  11.4 %CPU
Seeker 2...Seeker 1...Seeker 3...start 'em...done...done...done...
              ---Sequential Output (nosync)--- ---Sequential Input-- --Rnd Seek-
              -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --04k (03)-
Machine    MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU   /sec %CPU
       1*1024 72692 83.7 103022 40.5 25355 12.0 37188 67.5 40809 11.4  382.1  2.4
Quoted 3 lines

Maybe this is the kind of performance you want out your ATA subsystem. Maybe if I could get a patch in to the kernels we could all have stable and fast IO.

Quoted 8 lines

I rather see lots of wasting rather than performance, here. Bonnie says that your subsystem can sustain 103 MB/s write but only 41 MB/s read. This looks about 60% throughput wasted for read.

Note that if you intend to use it only for write-only applications, performance are not that bad, even if just dropping the data on the floor would give you infinite throughput without any difference in functionnality. :-)

Well sense somebody paid/paying me make write performance go through the roof -- that is what I did. Now if you look closely you could see that in writing we are doing a boat load more work than reading. If somebody want me to throttle the reads more then they know how to get it done.

Regards,

Andre Hedrick
Linux Disk Certification Project Linux ATA Development

#7 lore raw
Quoted 31 lines · Andre Hedrick
Quoted 20 lines · Gérard Roudier
Quoted 12 lines · Andre Hedrick

File './Bonnie.2276', size: 1073741824, volumes: 1

Writing with putc()...  done:  72692 kB/s  83.7 %CPU
Rewriting...            done:  25355 kB/s  12.0 %CPU
Writing intelligently...done: 103022 kB/s  40.5 %CPU
Reading with getc()...  done:  37188 kB/s  67.5 %CPU
Reading intelligently...done:  40809 kB/s  11.4 %CPU
Seeker 2...Seeker 1...Seeker 3...start 'em...done...done...done...
              ---Sequential Output (nosync)--- ---Sequential Input-- --Rnd Seek-
              -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --04k (03)-
Machine    MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU   /sec %CPU
       1*1024 72692 83.7 103022 40.5 25355 12.0 37188 67.5 40809 11.4  382.1  2.4
Quoted 3 lines

Maybe this is the kind of performance you want out your ATA subsystem. Maybe if I could get a patch in to the kernels we could all have stable and fast IO.

Quoted 8 lines

I rather see lots of wasting rather than performance, here. Bonnie says that your subsystem can sustain 103 MB/s write but only 41 MB/s read. This looks about 60% throughput wasted for read.

Note that if you intend to use it only for write-only applications, performance are not that bad, even if just dropping the data on the floor would give you infinite throughput without any difference in functionnality. :-)

Quoted 4 lines

Well sense somebody paid/paying me make write performance go through the roof -- that is what I did. Now if you look closely you could see that in writing we are doing a boat load more work than reading. If somebody want me to throttle the reads more then they know how to get it done.

I am not the one that will pay you for that, as you can guess. :-)

I just was curious about the technical reasons, if any, of so large a difference. Just, the CPU and the memory subsystem are certainly not the issue. But I donnot want to prevent you from earning from such kind of improvement. Hence, let me go back to free scsi.

Gérard.

Quoted 4 lines

Regards,

Andre Hedrick
Linux Disk Certification Project Linux ATA Development

author
#8 lore raw
Quoted 10 lines · Gérard Roudier
Quoted 6 lines · Andre Hedrick
Quoted 4 lines · Gérard Roudier

On Tue, 18 Dec 2001, Andre Hedrick wrote:

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines

File './Bonnie.2276', size: 1073741824, volumes: 1

Writing with putc()...  done:  72692 kB/s  83.7 %CPU
Rewriting...            done:  25355 kB/s  12.0 %CPU
Writing intelligently...done: 103022 kB/s  40.5 %CPU
Reading with getc()...  done:  37188 kB/s  67.5 %CPU
Reading intelligently...done:  40809 kB/s  11.4 %CPU

Seeker 2...Seeker 1...Seeker 3...start

'em...done...done...done...

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

---Sequential Output (nosync)--- ---Sequential

Input-- --Rnd Seek-

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
              -Per Char- --Block--- -Rewrite-- -Per Char-

--Block--- --04k (03)-

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec

%CPU /sec %CPU

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
       1*1024 72692 83.7 103022 40.5 25355 12.0 37188 67.5 40809

11.4 382.1 2.4

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

Maybe this is the kind of performance you want out your ATA

subsystem.

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

Maybe if I could get a patch in to the kernels we could all have

stable

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

and fast IO.

I think people might be missing the issue that I'm having, here. Let me see if I can clarify. I'm not too concerned about write speed. I don't care too much if the hard drive can only write one byte per second. The problem is that when the kernel decides to write out to the disk, it is pre-empting everything else. All output to the user in X, the sound card, and also text typing in the console is put "on the back burner" while the disk is written to.

It seems to me that smaller chunks of data can be written to the disk without disrupting my use of the computer (which is the case with untarring a small file, for instance), so if the kernel has got a lot to write to disk, just do that as a bunch of smaller writes and we should be fine.

So I guess I don't really care what mode the hard drive is operating in (udma, mdma, dma or plain ide), I just don't want to have to go get a cup of coffee while the hard drive saves some data. Is there a "don't pre-empt the rest of the system" switch for the eide drives? Is there something fundamental/unique going on here that I'm missing?

Thanks for listening.

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

I rather see lots of wasting rather than performance, here. Bonnie

says

Quoted 1 line
Quoted 1 line
Quoted 1 line

that your subsystem can sustain 103 MB/s write but only 41 MB/s

read. This

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

looks about 60% throughput wasted for read.

Note that if you intend to use it only for write-only

applications,

Quoted 1 line
Quoted 1 line
Quoted 1 line

performance are not that bad, even if just dropping the data on

the floor

Quoted 4 lines
Quoted 4 lines
Quoted 2 lines

would give you infinite throughput without any difference in functionnality. :-)

Well sense somebody paid/paying me make write performance go through

the

Quoted 1 line
Quoted 1 line

roof -- that is what I did. Now if you look closely you could see

that in

Quoted 1 line
Quoted 1 line

writing we are doing a boat load more work than reading. If

somebody want

Quoted 6 lines
Quoted 1 line

me to throttle the reads more then they know how to get it done.

I am not the one that will pay you for that, as you can guess. :-)

I just was curious about the technical reasons, if any, of so large a difference. Just, the CPU and the memory subsystem are certainly not

the

Quoted 2 lines

issue. But I donnot want to prevent you from earning from such kind of improvement. Hence, let me go back to free scsi.

Signature · 3 lines
MACINTOSH = Machine Always Crashes If Not The Operating System Hangs
"Life would be so much easier if we could just look at the source code."
- Dave Olson
#9 lore raw
In reply to Gérard Roudier
Quoted 7 lines · jlm

I think people might be missing the issue that I'm having, here. Let me see if I can clarify. I'm not too concerned about write speed. I don't care too much if the hard drive can only write one byte per second. The problem is that when the kernel decides to write out to the disk, it is pre-empting everything else. All output to the user in X, the sound card, and also text typing in the console is put "on the back burner" while the disk is written to.

There may be a problem here, and maybe not:

All of the actions above _may_ require disk access. The shell you type into could be swapped out, for example. A slow disk will be a problem in that case, swapin won't happen until the disk head seeks to the relevant position, and that may be delayed by the write. Even if the cpu is capable of doing other work while IO is going on.

Quoted 9 lines

It seems to me that smaller chunks of data can be written to the disk without disrupting my use of the computer (which is the case with untarring a small file, for instance), so if the kernel has got a lot to write to disk, just do that as a bunch of smaller writes and we should be fine.

So I guess I don't really care what mode the hard drive is operating in (udma, mdma, dma or plain ide), I just don't want to have to go get a cup of coffee while the hard drive saves some data. Is there a "don't

Devices generally get the cpu before anything else. A good disk system don't need much cpu. Running IDE in PIO mode require a lot
of cpu though. Using any of the DMA modes avoids that.

Quoted 2 lines

pre-empt the rest of the system" switch for the eide drives? Is there something fundamental/unique going on here that I'm missing?

dma, udma, etc. is that switch. It lets the cpu do other work (such as redrawing X) while the disk is busy. Plain ide is what you don't want.

The problem of waiting for other files or swapping while a really big write
is going on is different. Get more drives, so the big writes go to one drive while you get stuff swapped in (or other file access) on other drive(s). The kernel is capable of getting fast response from one drive while another is completely bogged down with enormous writes.

Helge Hafting

#10 lore raw

Oops in 2.4.14-pre6 and 2.4.14-pre9aa1

In reply to Gérard Roudier

I'm running a Application server in a DELL POWEREDGE 8450 with 4xP-III 700 Mhz, 4GB Memory. After 40 days running kernel 2.4.14-pre6 my system reports the following error in /var/adm/messages:

Dec 13 13:52:42 front01 kernel: invalid operand: 0000
Dec 13 13:52:42 front01 kernel: CPU:    3
Dec 13 13:52:42 front01 kernel: EIP:    0010:[<c012e764>]    Not tainted
Dec 13 13:52:42 front01 kernel: EFLAGS: 00010282
Dec 13 13:52:42 front01 kernel: eax: 00000880   ebx: c855e280   ecx: c855e280 
  edx: 00000000
Dec 13 13:52:42 front01 kernel: esi: fe000ff4   edi: 00000000   ebp: 00000ff1 
  esp: ce439eb0
Dec 13 13:52:42 front01 kernel: ds: 0018   es: 0018   ss: 0018
Dec 13 13:52:42 front01 kernel: Process ps.bin (pid: 29154, 
stackpage=ce439000)
Dec 13 13:52:42 front01 kernel: Stack: c855e280 fe000ff4 e58f3003 00000ff1 
f40252a3 c01f4bd8 c021bb70 c01504aa
Dec 13 13:52:42 front01 kernel:        c855e280 c012eebc c011daf8 00000003 
00000003 bffffff1 eef09920 c011dbb6
Dec 13 13:52:42 front01 kernel:        ca07b400 eef09920 bffffff1 e58f3000 
00000003 00000000 ca07b400 ca07b41c
Dec 13 13:52:42 front01 kernel: Call Trace: [<c01504aa>] [<c012eebc>] 
[<c011daf8>] [<c011dbb6>] [<c011dc3a>]
Dec 13 13:52:42 front01 kernel:    [<c014f66a>] [<c014f8db>] [<c01343d7>] 
[<c0106f73>]
Dec 13 13:52:42 front01 kernel:
Dec 13 13:52:42 front01 kernel: Code: 0f 0b ba 00 e0 ff ff 80 63 18 eb 21 e2 

f6 42 05 20 0f 85 55

I change ther kernel to 2.4.15-pre9aa1 and today the same error occurs, one week later, with this message:

Dec 20 01:21:58 front01 kernel: invalid operand: 0000
Dec 20 01:21:58 front01 kernel: CPU:    3
Dec 20 01:21:58 front01 kernel: EIP:    0010:[<c013153b>]    Not tainted
Dec 20 01:21:58 front01 kernel: EFLAGS: 00010202
Dec 20 01:21:58 front01 kernel: eax: 00000840   ebx: c5ba3ec0   ecx: c5ba3ec0 
  edx: 00000000
Dec 20 01:21:58 front01 kernel: esi: fe000f81   edi: 00000000   ebp: 00000f7b 
  esp: c2cebeb0
Dec 20 01:21:58 front01 kernel: ds: 0018   es: 0018   ss: 0018
Dec 20 01:21:58 front01 kernel: Process ps.bin (pid: 19556, 
stackpage=c2ceb000)
Dec 20 01:21:58 front01 kernel: Stack: c5ba3ec0 fe000f81 cd7b1006 00000f7b 
c0238fb0 c0154d8a d51db340 d51db340
Dec 20 01:21:58 front01 kernel:        c5ba3ec0 c0131d98 c011ffb8 00000006 
00000006 bfffff7b c8b8e740 c0120076
Dec 20 01:21:58 front01 kernel:        c294b820 c8b8e740 bfffff7b cd7b1000 
00000006 00000000 c294b83c c294b820
Dec 20 01:21:58 front01 kernel: Call Trace: [<c0154d8a>] [<c0131d98>] 
[<c011ffb8>] [<c0120076>] [<c0120119>]
Dec 20 01:21:58 front01 kernel:    [<c0153f3a>] [<c01541ab>] [<c0138117>] 
[<c0106f73>]
Dec 20 01:21:58 front01 kernel:
Dec 20 01:21:58 front01 kernel: Code: 0f 0b 8b 43 18 a8 80 74 02 0f 0b b9 00 

e0 ff ff 80 63 18 eb

ksymoops:

ksymoops 2.4.1 on i686 2.4.15-pre9. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.15-pre9/ (default)
-m /usr/src/linux/System.map (default)

Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options.

Error (expand_objects): cannot stat(/lib/reiserfs.o) for reiserfs Error (expand_objects): cannot stat(/lib/sym53c8xx.o) for sym53c8xx Error (expand_objects): cannot stat(/lib/qla2x00.o) for qla2x00 Error (expand_objects): cannot stat(/lib/megaraid.o) for megaraid Error (expand_objects): cannot stat(/lib/sd_mod.o) for sd_mod Error (expand_objects): cannot stat(/lib/scsi_mod.o) for scsi_mod Warning (read_object): no symbols in /lib/modules/2.4.15-pre9/build/net/ipv4/netfilter/netfilter.o Warning (read_object): no symbols in /lib/modules/2.4.15-pre9/build/net/ipv6/netfilter/netfilter.o Warning (read_object): no symbols in /lib/modules/2.4.15-pre9/build/drivers/net/fc/fc.o
Warning (read_object): no symbols in /lib/modules/2.4.15-pre9/build/drivers/net/wan/wan.o
Warning (read_object): no symbols in /lib/modules/2.4.15-pre9/build/drivers/net/appletalk/appletalk.o Warning (read_object): no symbols in /lib/modules/2.4.15-pre9/build/drivers/net/tokenring/tr.o
Warning (read_object): no symbols in /lib/modules/2.4.15-pre9/build/drivers/net/pcmcia/pcmcia_net.o Warning (read_object): no symbols in /lib/modules/2.4.15-pre9/build/drivers/net/wireless/wireless_net.o Warning (read_object): no symbols in /lib/modules/2.4.15-pre9/build/drivers/misc/misc.o
Warning (read_object): no symbols in /lib/modules/2.4.15-pre9/build/drivers/cdrom/driver.o
Warning (read_object): no symbols in /lib/modules/2.4.15-pre9/build/drivers/media/radio/radio.o Warning (read_object): no symbols in /lib/modules/2.4.15-pre9/build/drivers/media/video/video.o Warning (read_object): no symbols in /lib/modules/2.4.15-pre9/build/drivers/media/media.o
Warning (read_object): no symbols in /lib/modules/2.4.15-pre9/build/drivers/sound/sounddrivers.o Warning (read_object): no symbols in /lib/modules/2.4.15-pre9/build/drivers/parport/driver.o
Warning (read_object): no symbols in /lib/modules/2.4.15-pre9/build/drivers/hotplug/vmlinux-obj.o Warning (compare_maps): mismatch on symbol partition_name , ksyms_base says c01a3160, System.map says c0158b20. Ignoring ksyms_base entry Warning (compare_maps): mismatch on symbol vg , lvm-mod says c89d8b20, /lib/modules/2.4.15-pre9/kernel/drivers/md/lvm-mod.o says c89d8780. Ignoring /lib/modules/2.4.15-pre9/kernel/drivers/md/lvm-mod.o entry Warning (map_ksym_to_module): cannot match loaded module reiserfs to a unique module object. Trace may not be reliable.
Warning (map_ksym_to_module): cannot match loaded module sym53c8xx to a unique module object. Trace may not be reliable.
Warning (map_ksym_to_module): cannot match loaded module qla2x00 to a unique module object. Trace may not be reliable.
Warning (map_ksym_to_module): cannot match loaded module megaraid to a unique mole object. Trace may not be reliable.
Warning (map_ksym_to_module): cannot match loaded module scsi_mod to a unique module object. Trace may not be reliable.

Dec 20 01:21:58 front01 kernel: invalid operand: 0000
Dec 20 01:21:58 front01 kernel: CPU:    3
Dec 20 01:21:58 front01 kernel: EIP:    0010:[<c013153b>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
Dec 20 01:21:58 front01 kernel: EFLAGS: 00010202
Dec 20 01:21:58 front01 kernel: eax: 00000840   ebx: c5ba3ec0   ecx: c5ba3ec0 
edx: 00000000
Dec 20 01:21:58 front01 kernel: esi: fe000f81   edi: 00000000   ebp: 00000f7b 
esp: c2cebeb0
Dec 20 01:21:58 front01 kernel: ds: 0018   es: 0018   ss: 0018
Dec 20 01:21:58 front01 kernel: Process ps.bin (pid: 19556, 
stackpage=c2ceb000)
Dec 20 01:21:58 front01 kernel: Stack: c5ba3ec0 fe000f81 cd7b1006 00000f7b 
c0238fb0 c0154d8a d51db340 d51db340 
Dec 20 01:21:58 front01 kernel:        c5ba3ec0 c0131d98 c011ffb8 00000006 
00000006 bfffff7b c8b8e740 c0120076 
Dec 20 01:21:58 front01 kernel:        c294b820 c8b8e740 bfffff7b cd7b1000 
00000006 00000000 c294b83c c294b820 
Dec 20 01:21:58 front01 kernel: Call Trace: [<c0154d8a>] [<c0131d98>] 

[<c011ffb8>] [<c0120076>] [<c0120119>]

Warning (Oops_read): Code line not seen, dumping what data is available

Quoted 1 line
Quoted 1 line

EIP; c013153b <__free_pages_ok+4b/238> <=====

Trace; c0154d8a <proc_base_lookup+22a/23c>
Trace; c0131d98 <__free_pages+1c/20>
Trace; c011ffb8 <access_one_page+244/2a0>
Trace; c0120076 <access_mm+62/7c>
Trace; c0120119 <access_process_vm+89/c4>
Trace; c0153f3a <proc_pid_cmdline+62/e8>
Trace; c01541ab <proc_info_read+53/110>
Trace; c0138117 <sys_read+8f/c4>
Trace; c0106f73 <system_call+33/38>

26 warnings and 6 errors issued. Results may not be reliable.

In all oops the system stay up, but if you run a ps command this process freeze.

It's possible to reboot the machine using reboot -f

Any help?

Thank's in advance

Andre Margis

#11 lore raw
In reply to Andre Hedrick
Quoted 16 lines · Gérard Roudier
Quoted 12 lines · Andre Hedrick

File './Bonnie.2276', size: 1073741824, volumes: 1

Writing with putc()...  done:  72692 kB/s  83.7 %CPU
Rewriting...            done:  25355 kB/s  12.0 %CPU
Writing intelligently...done: 103022 kB/s  40.5 %CPU
Reading with getc()...  done:  37188 kB/s  67.5 %CPU
Reading intelligently...done:  40809 kB/s  11.4 %CPU
Seeker 2...Seeker 1...Seeker 3...start 'em...done...done...done...
              ---Sequential Output (nosync)--- ---Sequential Input-- --Rnd Seek-
              -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --04k (03)-
Machine    MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU   /sec %CPU
       1*1024 72692 83.7 103022 40.5 25355 12.0 37188 67.5 40809 11.4  382.1  2.4
Quoted 7 lines
Quoted 3 lines

Maybe this is the kind of performance you want out your ATA subsystem. Maybe if I could get a patch in to the kernels we could all have stable and fast IO.

I rather see lots of wasting rather than performance, here. Bonnie says that your subsystem can sustain 103 MB/s write but only 41 MB/s read. This looks about 60% throughput wasted for read.

Uh, well, um, what drive is he writing too?? He could very well have 2 gig of memory in this box and half the writes were cached. 41MB/s seems reasonable for most common IDE disks. Of course I know Andre has some rather 'uncommon' IDE drives :P

Does bonnie actually do any sort of 'sync' operation to ensure data writen is on the disk? Is that 100mb/sec write real, or just because of block layer caching?

Quoted 24 lines

Note that if you intend to use it only for write-only applications, performance are not that bad, even if just dropping the data on the floor would give you infinite throughput without any difference in functionnality. :-)

Gérard Roudier
Not CEO, not President of anything.

Quoted 7 lines

Regards,

Andre Hedrick
CEO/President, LAD Storage Consulting Group
Linux ATA Development
Linux Disk Certification Project

-
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/

Signature · 5 lines
Troy Benjegerdes | master of mispeeling | 'da hozer' |  [email protected]
-----"If this message isn't misspelled, I didn't write it" -- Me -----
"Why do musicians compose symphonies and poets write poems? They do it
because life wouldn't have any meaning for them if they didn't. That's 
why I draw cartoons. It's my life." -- Charles Schulz