REVISED: Experimentation with Athlon and fast_page_copy
Hi,
After removing my head from my a**, I revised the code that checks
the memory copy in the fast_page_copy routine. The machine then proceeded
not to stop at my panic, but I got my "normal" oopses. I then had an idea and removed all the prefetch instructions from the beginning of the routine and tried the resultin kernel. I now have no crashes. What could this mean?
Here is a nother patch just so you can keep me honest if I made another mistake:
-------------------------
diff -r ./arch/i386/lib/mmx.c ../lin2/linux/arch/i386/lib/mmx.c 149,150c149
<
< /* __asm__ __volatile__ (
---
Quoted 1 line
__asm__ __volatile__ (
158c157
< "3: movw $0x1AEB, 1b\n"
---
Quoted 1 line
"3: movw $0x1AEB, 1b\n" /* jmp on 26 bytes */
166c165
< */
---
Quoted 1 line
170c169
< "1: nop\n" /* prefetch 320(%0)\n" */
---
Quoted 1 line
"1: prefetch 320(%0)\n"
-------------------------
Please let me know if that makes sense :).
Thank you,
Seth
Quoted 10 lines · Seth Goldberg
Hi,
After removing my head from my a**, I revised the code that checks
the memory copy in thefast_page_copyroutine. The machine then proceeded
not to stop at my panic, but I got my "normal" oopses. I then had an idea and removed all the prefetch instructions from the beginning of the routine and tried the resultin kernel. I now have no crashes. What could this mean?
What are your "normal" oopses?
--
Brian Gerst
Quoted 3 lines
the memory copy in the
fast_page_copyroutine. The machine then proceeded
not to stop at my panic, but I got my "normal" oopses. I then had an
Ok
Quoted 3 lines
idea and removed all the prefetch instructions from the beginning of the routine and tried the resultin kernel. I now have no crashes. What could this mean?
I think it has to mean a hardware problem.
Quoted 2 lines
Here is a nother patch just so you can keep me honest if I made another mistake:
There is a mistake but you wont trigger it. It is no longer 26 bytes 8) That patch is only used when the prefetchw faults with an illegal instruction and is done so you can boot an athlon kernel on a lesser cpu
The prefetch instructions hint to the CPU what memory we will access very soon. The primary effect of that is that we hit full theoretical memory bandwidth when copying pages. It doesnt really change execution behaviour in any other way which then does rather point to cpu or other hardware problem. The very early athlons had prefetch bugs but we would not trigger those and no reporters have such an early CPU.
What still stands out is that exactly _zero_ people have reported the same problem with non VIA chipset Athlons.
Quoted 3 lines
What still stands out is that exactly _zero_ people have reported the same problem with non VIA chipset Athlons.
This might be grasping at straws I remember VIA problem in the "good old days" of Socket 7 with CPU/PCI Prefetches and especially Read-around-Write settings that would cause issues like we're seeing with the Athlon pre-fetches. This could be (total conjecture) related somehow to the corruption bugs they are admitting to in the 686B although they are blaming the SB Live now.
Quoted 6 lines · Aaron Tiensivu
This might be grasping at straws I remember VIA problem in the "good old days" of Socket 7 with CPU/PCI Prefetches and especially Read-around-Write settings that would cause issues like we're seeing with the Athlon pre-fetches. This could be (total conjecture) related somehow to the corruption bugs they are admitting to in the 686B although they are blaming the SB Live now.
I don't see how they figure, but in case there was any doubt I have a VIA KT133A/686B board (Abit KT7A) and don't experience anything resembling disk corruption unless the box crashes for some other reason. I do seem to be experiencing AGP problems in spades, but my disks at least are fine.
Signature · 3 lines
Joseph Carter <[email protected]> Free software developer <_Anarchy_> Argh.. who's handing out the paper bags 8)
On Fri, May 04, 2001 at 05:26:57PM -0700, Joseph Carter wrote:
I don't see how they figure, but in case there was any doubt I have a VIA KT133A/686B board (Abit KT7A) and don't experience anything resembling disk corruption unless the box crashes for some other reason. I do seem to be experiencing AGP problems in spades, but my disks at least are fine.
I too seem no disk problems whatsoever (nothing really interesting there, many people do not) but am also seeing AGP problems.
In fact, I had to disable AGP to stop X locking the box hard... yet agpgart and the video driver (NVidia[1]) both claim to support the chipset -- does anyone actually have this working?)
--cw
[1] Yeah, close source, blah blah blah. Right now it works for me, and it works _VERY_ well.
Quoted 9 lines · Chris Wedgwood
On Fri, May 04, 2001 at 05:26:57PM -0700, Joseph Carter wrote:
I don't see how they figure, but in case there was any doubt I have a VIA KT133A/686B board (Abit KT7A) and don't experience anything resembling disk corruption unless the box crashes for some other reason. I do seem to be experiencing AGP problems in spades, but my disks at least are fine.
Quoted 6 lines
I too seem no disk problems whatsoever (nothing really interesting there, many people do not) but am also seeing AGP problems.
In fact, I had to disable AGP to stop X locking the box hard... yet agpgart and the video driver (NVidia[1]) both claim to support the chipset -- does anyone actually have this working?)
My IWILL (KT133A) + GeForce 256 are working fine over AGP.
--S
Athlon and fast_page_copy: What's it worth ? :)
In reply to Alan CoxHi,
Before I go any further with this investigation, I'd like to get an
idea
of how much of a performance improvement the K7 fast_page_copy will give me.
Can someone suggest the best benchmark to test the speed of this routine?
Thanks,
Seth
Quoted 6 lines · Chris Wedgwood
I don't see how they figure, but in case there was any doubt I have a VIA KT133A/686B board (Abit KT7A) and don't experience anything resembling disk corruption unless the box crashes for some other reason. I do seem to be experiencing AGP problems in spades, but my disks at least are fine.
Quoted 6 lines
I too seem no disk problems whatsoever (nothing really interesting there, many people do not) but am also seeing AGP problems.
In fact, I had to disable AGP to stop X locking the box hard... yet agpgart and the video driver (NVidia[1]) both claim to support the chipset -- does anyone actually have this working?)
Not an option with the Radeon unfortunately. At least, not yet. Whenever I find the solution (recently a bunch of people have suggested a bunch of things to try on dri-devel - thanks guys!) I'll post to that list what fixed it since I know I am not the only person seeing this kind of problem. I think some of the guys are looking into improving the docs a bit, so maybe if I find it soon the problem and workaround will get documented. =)
Signature · 4 lines
Joseph Carter <[email protected]> Free software developer <hop> kb: I demand integrity and honesty in those who i do business with <hop> i know my demands are unreasonable, but a guy can dream, can't he?
Quoted 8 lines · Aaron Tiensivu
Quoted 2 lines
What still stands out is that exactly _zero_ people have reported the same problem with non VIA chipset Athlons.
This might be grasping at straws [...] This could be (total conjecture)
related somehow to the corruption bugs they are admitting to in
the 686B although they are blaming the SB Live now.
Just another data point (the news is in the final paragraph):
I recently built two near-twin systems using Athlon 1.2's and VIA chipsets (EPoX 8KTA3), and have *never* been able to get either to boot an Athlon-optimized kernel, having tried 2.4.0, 2.4.2, 2.4.4, and about 5 different -ac* variants of 2.4.3.
They do boot PIII kernels reliably for all those variants, though they still suffer occasional oopses, hangs, or crashes (as discussed in other threads).
However (and here's the part I haven't mentioned before), yesterday I switched one of them to a new mb with a non-VIA chipset (Asus A7A266), and it booted the first Athlon kernel I tried (2.4.4). No other changes to .config, same processor as before, same memory, same disks, same video, same case, same power cord, you name it.
Bobby Bryant
Austin, Texas
Re: Athlon and fast_page_copy: What's it worth ? :)
In reply to Seth GoldbergQuoted 8 lines · Seth Goldberg
Hi,
Before I go any further with this investigation, I'd like to get an
idea
of how much of a performance improvement the K7fast_page_copywill give me.
Can someone suggest the best benchmark to test the speed of this routine?
Arjan van de Ven did the code, and he wrote a little test harness. I've hacked it a bit (http://brain.mcmaster.ca/~hahn/athlon.c);
on my duron/600, kt133, pc133 cas2, it looks like this:
clear_page by 'normal_clear_page' took 7221 cycles (324.6 MB/s) clear_page by 'slow_zero_page' took 7232 cycles (324.1 MB/s) clear_page by 'fast_clear_page' took 6110 cycles (383.6 MB/s) clear_page by 'faster_clear_page' took 2574 cycles (910.6 MB/s)
copy_page by 'normal_copy_page' took 7224 cycles (324.4 MB/s) copy_page by 'slow_copy_page' took 7223 cycles (324.5 MB/s) copy_page by 'fast_copy_page' took 4662 cycles (502.7 MB/s) copy_page by 'faster_copy' took 2746 cycles (853.5 MB/s) copy_page by 'even_faster' took 2802 cycles (836.5 MB/s)
70% faster!
Quoted 2 lines · Bobby D. Bryant
They do boot PIII kernels reliably for all those variants, though they still suffer occasional oopses, hangs, or crashes (as discussed in other threads).
and as happens with my SMP pIII VIA-based boxed (and I've finally fixed the memory, so I no longer get the oopses, just solid hardware hangs).
Quoted 5 lines
However (and here's the part I haven't mentioned before), yesterday I switched one of them to a new mb with a non-VIA chipset (Asus A7A266), and it booted the first Athlon kernel I tried (2.4.4). No other changes to .config, same processor as before, same memory, same disks, same video, same case, same power cord, you name it.
damn. I guess the saving of 200$ on the MSI has probably been 300$ down the drain :(
Signature · 3 lines
John Lenton ([email protected]) -- Random fortune: If you treat people right they will treat you right -- 90% of the time. -- Franklin Delano Roosevelt
Re: Athlon and fast_page_copy: What's it worth ? :)
In reply to Seth GoldbergQuoted 6 lines
Before I go any further with this investigation, I'd like to get an
idea
of how much of a performance improvement the K7fast_page_copywill give me.
Can someone suggest the best benchmark to test the speed of this routine?
About 30% on page copies. Its impact in real world is very dependant on the job mix
Quoted 9 lines
Quoted 1 line
one of them to a new mb with a non-VIA chipset (Asus A7A266), and it boot=
ed the
Quoted 2 lines
first Athlon kernel I tried (2.4.4). No other changes to .config, same processor as before, same memory, same disks, same video, same case, same=
power
Quoted 1 line
cord, you name it.
damn. I guess the saving of 200$ on the MSI has probably been 300$ down the drain :(
Dont panic just yet. Manfred's observation could mean we hit chipset specific behaviour on prefetches.
Re: Athlon and fast_page_copy: What's it worth ? :)
In reply to Mark HahnQuoted 21 lines · Mark Hahn
Quoted 8 lines · Seth Goldberg
Hi,
Before I go any further with this investigation, I'd like to get an
idea
of how much of a performance improvement the K7fast_page_copywill give me.
Can someone suggest the best benchmark to test the speed of this routine?Arjan van de Ven did the code, and he wrote a little test harness. I've hacked it a bit (http://brain.mcmaster.ca/~hahn/athlon.c);
on my duron/600, kt133, pc133 cas2, it looks like this:clear_page by 'normal_clear_page' took 7221 cycles (324.6 MB/s) clear_page by 'slow_zero_page' took 7232 cycles (324.1 MB/s) clear_page by 'fast_clear_page' took 6110 cycles (383.6 MB/s) clear_page by 'faster_clear_page' took 2574 cycles (910.6 MB/s)
Quoted 8 lines
copy_page by 'normal_copy_page' took 7224 cycles (324.4 MB/s) copy_page by 'slow_copy_page' took 7223 cycles (324.5 MB/s) copy_page by 'fast_copy_page' took 4662 cycles (502.7 MB/s) copy_page by 'faster_copy' took 2746 cycles (853.5 MB/s) copy_page by 'even_faster' took 2802 cycles (836.5 MB/s)70% faster!
I've played with this some, too. I find that Arjan's tests are very delicate about the number of hw interrupts serviced. On UP I see 2-3 interrupts per page copy on average with my normal workload. On Athlon, interrupts hit 'rep mov' (looong interruptable vector path insn) much worse than they do mmx movq (direct path) instructions.
With hands off and no networking, breakeven is about the canonical 512 bytes, and page copy is about 30% better, as Alan says. With ethers up and X running mmx gets better by comparison -- 40-60% for me. I haven't seen 70% better, but I'd like to.
Cheers,
Tom
Signature · 1 line
The Daemons lurk and are dumb. -- Emerson
Re: Athlon and fast_page_copy: What's it worth ? :)
In reply to Mark HahnQuoted 20 lines · Mark Hahn
Quoted 8 lines · Seth Goldberg
Hi,
Before I go any further with this investigation, I'd like to get an
idea
of how much of a performance improvement the K7fast_page_copywill give me.
Can someone suggest the best benchmark to test the speed of this routine?Arjan van de Ven did the code, and he wrote a little test harness. I've hacked it a bit (http://brain.mcmaster.ca/~hahn/athlon.c);
on my duron/600, kt133, pc133 cas2, it looks like this:clear_page by 'normal_clear_page' took 7221 cycles (324.6 MB/s) clear_page by 'slow_zero_page' took 7232 cycles (324.1 MB/s) clear_page by 'fast_clear_page' took 6110 cycles (383.6 MB/s) clear_page by 'faster_clear_page' took 2574 cycles (910.6 MB/s)
Quoted 7 lines
copy_page by 'normal_copy_page' took 7224 cycles (324.4 MB/s) copy_page by 'slow_copy_page' took 7223 cycles (324.5 MB/s) copy_page by 'fast_copy_page' took 4662 cycles (502.7 MB/s) copy_page by 'faster_copy' took 2746 cycles (853.5 MB/s) copy_page by 'even_faster' took 2802 cycles (836.5 MB/s)70% faster!
On my Athlon 1GHz, Abit KT7, PC133 set to "Turbo" (not quite sure what the actual CAS rating is, but it works):
[chromi@beryllium compsci]$ ./athlon
1000.047 MHz
clear_page by 'normal_clear_page' took 10769 cycles (362.7 MB/s) clear_page by 'slow_zero_page' took 10349 cycles (377.5 MB/s) clear_page by 'fast_clear_page' took 10868 cycles (359.4 MB/s) clear_page by 'faster_clear_page' took 4345 cycles (899.1 MB/s)
copy_page by 'normal_copy_page' took 11242 cycles (347.5 MB/s) copy_page by 'slow_copy_page' took 11245 cycles (347.4 MB/s) copy_page by 'fast_copy_page' took 7951 cycles (491.3 MB/s) copy_page by 'faster_copy' took 4765 cycles (819.7 MB/s) copy_page by 'even_faster' took 4955 cycles (788.3 MB/s)
My wild guess is that with the "faster" code, the K7 is avoiding loading cache lines just to write them out again, and is just writing tons of data. The PPC G4 - and perhaps even the G3 - performs a similar trick automatically, without special assembly...
Perhaps the IWILL m/board doesn't like this behaviour, and somehow assumes that all written cachelines have been read beforehand. I heard of some m/boards - particularly those with more than 3 DIMM slots - using a "helper chip" to boost the signal to the last slot or two, so maybe that is a problem? How many slots does the IWILL have?
--------------------------------------------------------------
from: Jonathan "Chromatix" Morton mail: [email protected] (not for attachments) big-mail: [email protected] uni-mail: [email protected]
The key to knowledge is not to rely on people to teach you it.
Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/
-----BEGIN GEEK CODE BLOCK-----
Version 3.12
GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*) -----END GEEK CODE BLOCK-----
Re: Athlon and fast_page_copy: What's it worth ? :)
Quoted 4 lines
My wild guess is that with the "faster" code, the K7 is avoiding loading cache lines just to write them out again, and is just writing tons of data. The PPC G4 - and perhaps even the G3 - performs a similar trick automatically, without special assembly...
X86 has done that since the K5 era.
No the main thing that the mmx copier does is to read and write in 64bit wide chunks, and then more importantly to prefetch pending data. Thus instead of stalling on reads there is a continual stream of data from the sdram hitting the cpu ready for us to write it back out (and the write out is buffered too)
Alan
Re: Athlon and fast_page_copy: What's it worth ? :)
Quoted 9 lines · Alan Cox
Quoted 4 lines
My wild guess is that with the "faster" code, the K7 is avoiding loading cache lines just to write them out again, and is just writing tons of data. The PPC G4 - and perhaps even the G3 - performs a similar trick automatically, without special assembly...
X86 has done that since the K5 era.
No the main thing that the mmx copier does is to read and write in 64bit wide chunks
Just for the record, this can be done on any PPC, by using the FPU registers (which are much faster than x86 FPU). AltiVec can do 128-bit wide transfers.
Quoted 1 line
and then more importantly to prefetch pending data.
That's a tougher one. AltiVec (in the G4) can do this, but I suspect it can be emulated using the pipeline on earlier PowerPCs, by queueing up a line of FPU load instructions and then a queue of FPU saves. However, the 601 and 603 don't have a superscalar FPU, though I wonder if that would actually affect a simple load/store operation.
This is rapidly getting offtopic, though...
--------------------------------------------------------------
from: Jonathan "Chromatix" Morton mail: [email protected] (not for attachments) big-mail: [email protected] uni-mail: [email protected]
The key to knowledge is not to rely on people to teach you it.
Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/
-----BEGIN GEEK CODE BLOCK-----
Version 3.12
GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*) -----END GEEK CODE BLOCK-----
Quoted 2 lines · Alan Cox
Dont panic just yet. Manfred's observation could mean we hit chipset specific behaviour on prefetches.
OK - Please let me know when to start.
Signature · 4 lines
John Lenton ([email protected]) -- Random fortune: BOFH excuse #349: Stray Alpha Particles from memory packaging caused Hard Memory Error on Server.
Have non-production via KT133a, will test :) (tyan mobo, 1.33ghz, tulip eth, an idea drive, nothing really exciting, just a fast ath)
-j
John R Lenton enlightened recipients with the following on 06May2001:
Quoted 5 lines · Alan Cox
Quoted 2 lines
Dont panic just yet. Manfred's observation could mean we hit chipset specific behaviour on prefetches.
OK - Please let me know when to start.
Signature · 6 lines
---------------------------------------------------------------------------
heffner at darkness.net
Darkness Network Engineering
PGP public key available on request
My thoughts and opinions represent no one but myself
---------------------------------------------------------------------------Re: Athlon and fast_page_copy: What's it worth ? :)
In reply to Alan CoxQuoted 8 lines · In article <[email protected]> you wrote:
Hi,
Before I go any further with this investigation, I'd like to get an
idea
of how much of a performance improvement the K7fast_page_copywill give me.
Can someone suggest the best benchmark to test the speed of this routine?
http://www.fenrus.demon.nl/athlon.c
is a userspace benchmark of the current code vs C etc
Quoted 5 lines · Alan Cox
Quoted 4 lines
the memory copy in the
fast_page_copyroutine. The machine then proceeded
not to stop at my panic, but I got my "normal" oopses. I then had an
Quoted 7 lines
Ok
Quoted 3 lines
idea and removed all the prefetch instructions from the beginning of the routine and tried the resultin kernel. I now have no crashes. What could this mean?
I think it has to mean a hardware problem.
I don't think so, reasons below
Quoted 2 lines
What still stands out is that exactly _zero_ people have reported the same problem with non VIA chipset Athlons.
Not any more :-(
Hi Alan,
IIRC this thread is about boot going catatonic right after unloading __initmem.
I'm seeing that in 2.4.5-pre1 with Athlon stepping 2, AMD 751, MS-6195 mobo, 128M.
The machine is fine with kernels up through 2.4.4-pre3, and still works with them.
On that gear, there is no crash. The keyboard and display are alive and SysRq works.
I have copied the stack trace for pid=1 and the processor dump. I'm short of time
but I have a kind typist electrifying the trace, and I'll try to generate something
ksymoops can digest.
Here is what a quick eyeballing of System.map shows.
The code is at the end of init/main.c:init(). The processor dump shows init() halted
in default_idle() from the sequence L6 -> init -> cpu_idle.
Trace of pid 1 shows it stuck in D state. The last addresses listed are from filemap_nopage -> do_execve -> do_no_page -> handle_mm_fault -> __pmd_alloc -> rwsem_down_write_failed -> stext_lock -> system_call. That looks fishy.
Earlier, it looks like handle_mm_fault is being triggered from fast_clear_page.
I'll post the full dump soon as I have it.
Btw, above happens with both gcc-2.95.3 and gcc-3.0-[20010423] compiled kernels.
Cheers,
Tom
Signature · 1 line
The Daemons lurk and are dumb. -- Emerson
Quoted 4 lines
Quoted 2 lines
What still stands out is that exactly _zero_ people have reported the same problem with non VIA chipset Athlons.
Not any more :-(
Still the same
Quoted 2 lines
IIRC this thread is about boot going catatonic right after unloading
__initmem.
Nope. Its about memory corruptions. Your bug sounds very different
Quoted 2 lines
Earlier, it looks like
handle_mm_faultis being triggered fromfast_clear_page.
That would be messy. The other way around is sane but not that way
Quoted 11 lines · Alan Cox
Quoted 4 lines
IIRC this thread is about boot going catatonic right after unloading
__initmem.Nope. Its about memory corruptions. Your bug sounds very different
Quoted 2 lines
Earlier, it looks like
handle_mm_faultis being triggered fromfast_clear_page.That would be messy. The other way around is sane but not that way
Indeed, I was confused. Looks like ide-dma is getting goofy somehow.
Here is a decoded trace. Typos are likely. If the problem is not obvious to anyone, I'll switch around my serial console setup to get some better info.
Warning (Oops_read): Code line not seen, dumping what data is available
Trace; ffff037f <END_OF_CODE+3fcfb2ab/????>
Trace; ffff0000 <END_OF_CODE+3fcfaf2c/????>
Trace; ffff0000 <END_OF_CODE+3fcfaf2c/????>
Trace; ffff0720 <END_OF_CODE+3fcfb64c/????>
Trace; c01b956a <ide_build_dmatable+2a/120>
Trace; c01b3fb5 <ide_set_handler+55/60>
Trace; c01b9aca <ide_dmaproc+11a/210>
Trace; c01b9380 <ide_dma_intr+0/b0>
Trace; c01b9940 <dma_timer_expiry+0/70>
Trace; c01bd457 <do_rw_disk+257/300>
Trace; c01b4d2a <ide_wait_stat+7a/e0>
Trace; c01b5010 <start_request+160/210>
Trace; c01b51ff <ide_do_request+10f/340>
Trace; c01b3430 <ali_cleanup+10/70>
Trace; c0132e45 <__wait_on_buffer+75/90>
Trace; c0134026 <bread+16/70>
Trace; c018665c <__make_request+43c/6f0>
Trace; c01866ce <__make_request+4ae/6f0>
Trace; c01866e6 <__make_request+4c6/6f0>
Trace; c018665c <__make_request+43c/6f0>
Trace; c01866ce <__make_request+4ae/6f0>
Trace; c01866e6 <__make_request+4c6/6f0>
Trace; c01b956a <ide_build_dmatable+2a/120>
Trace; c01b3fb5 <ide_set_handler+55/60>
Trace; c01b9aca <ide_dmaproc+11a/210>
Trace; c01b9380 <ide_dma_intr+0/b0>
Trace; c01b9940 <dma_timer_expiry+0/70>
Trace; c01bd457 <do_rw_disk+257/300>
Trace; c01b4d2a <ide_wait_stat+7a/e0>
Trace; c01b5010 <start_request+160/210>
Trace; c01b51ff <ide_do_request+10f/340>
Trace; c01b546e <do_ide_request+e/20>
Trace; c01134d0 <schedule+200/3e0>
Trace; c012bd2c <free_shortage+1c/c0>
Trace; c012cbd7 <__alloc_pages+87/300>
Trace; c022c12f <fast_copy_page+f/90>
Trace; c0125f4d <filemap_nopage+2bd/420>
Trace; c0125f58 <filemap_nopage+2c8/420>
Trace; c022c0ca <fast_clear_page+a/60>
Trace; c0122b7d <handle_mm_fault+cd/e0>
Trace; c012bd2c <free_shortage+1c/c0>
Trace; c0122a15 <do_no_page+45/e0>
Trace; c022c0ca <fast_clear_page+a/60>
Trace; c0222b7d <packet_ioctl+17d/350>
Trace; c0225476 <do_xprt_transmit+46/3d0>
Trace; c02254c3 <do_xprt_transmit+93/3d0>
Trace; c0112ba9 <do_page_fault+2a9/450>
Trace; c01239cf <do_munmap+5f/280>
Trace; c0112900 <do_page_fault+0/450>
Trace; c0106ddc <error_code+34/3c>
Trace; c022be20 <clear_user+30/40>
Trace; c0112900 <do_page_fault+0/450>
Trace; c0134026 <bread+16/70>
Trace; c018665c <__make_request+43c/6f0>
Trace; c01866ce <__make_request+4ae/6f0>
Trace; c01866e6 <__make_request+4c6/6f0>
Trace; c01b956a <ide_build_dmatable+2a/120>
Trace; c01b3fb5 <ide_set_handler+55/60>
Trace; c01b9aca <ide_dmaproc+11a/210>
Trace; c01b9380 <ide_dma_intr+0/b0>
Trace; c01b9940 <dma_timer_expiry+0/70>
Trace; c01bd457 <do_rw_disk+257/300>
Trace; c01b4d2a <ide_wait_stat+7a/e0>
Trace; c01b5010 <start_request+160/210>
Trace; c01b51ff <ide_do_request+10f/340>
Trace; c01b546e <do_ide_request+e/20>
Trace; c01134d0 <schedule+200/3e0>
Trace; c012be03 <inactive_shortage+33/90>
Trace; c0124d05 <__find_get_page+35/80>
Trace; c013ae1b <search_binary_handler+17b/190>
Trace; c0125d44 <filemap_nopage+b4/420>
Trace; c013af79 <do_execve+149/200>
Trace; c0122a15 <do_no_page+45/e0>
Trace; c012267d <vmtruncate+12d/160>
Trace; c0112ba9 <do_page_fault+2a9/450>
Trace; c022d075 <rwsem_down_write_failed+65/140>
Trace; c022f396 <stext_lock+37a/16bc>
Trace; c0106cbf <system_call+33/38>
1 warning issued. Results may not be reliable.
Cheers,
Tom
Signature · 1 line
The Daemons lurk and are dumb. -- Emerson
Quoted 4 lines
Trace;
ffff037f<END_OF_CODE+3fcfb2ab/????>
Trace;ffff0000<END_OF_CODE+3fcfaf2c/????>
Trace;ffff0000<END_OF_CODE+3fcfaf2c/????>
Trace;ffff0720<END_OF_CODE+3fcfb64c/????>
Lets ignore the crap above..
Quoted 9 lines
Trace;
c01b956a<ide_build_dmatable+2a/120>
Trace;c01b3fb5<ide_set_handler+55/60>
Trace;c01b9aca<ide_dmaproc+11a/210>
Trace;c01b9380<ide_dma_intr+0/b0>
Trace;c01b9940<dma_timer_expiry+0/70>
Trace;c01bd457<do_rw_disk+257/300>
Trace;c01b4d2a<ide_wait_stat+7a/e0>
Trace;c01b5010<start_request+160/210>
Trace;c01b51ff<ide_do_request+10f/340>
We seem to be several layers into recursive use of the ide driver - which shouldnt happen. In fact if these are the same interface the second dmatable build would leave HWIF(drive)->sg_table wrong.
Quoted 4 lines
Trace;
c01866ce<__make_request+4ae/6f0>
Trace;c01866e6<__make_request+4c6/6f0>
Trace;c01b956a<ide_build_dmatable+2a/120>
Trace;c01b3fb5<ide_set_handler+55/60>
Quoted 11 lines · Alan Cox
Quoted 10 lines
Trace;
c01b956a<ide_build_dmatable+2a/120>
Trace;c01b3fb5<ide_set_handler+55/60>
Trace;c01b9aca<ide_dmaproc+11a/210>
Trace;c01b9380<ide_dma_intr+0/b0>
Trace;c01b9940<dma_timer_expiry+0/70>
Trace;c01bd457<do_rw_disk+257/300>
Trace;c01b4d2a<ide_wait_stat+7a/e0>
Trace;c01b5010<start_request+160/210>
Trace;c01b51ff<ide_do_request+10f/340>
Quoted 8 lines
We seem to be several layers into recursive use of the ide driver - which shouldnt happen. In fact if these are the same interface the second dmatable build would leave HWIF(drive)->sg_table wrong.
Quoted 4 lines
Trace;
c01866ce<__make_request+4ae/6f0>
Trace;c01866e6<__make_request+4c6/6f0>
Trace;c01b956a<ide_build_dmatable+2a/120>
Trace;c01b3fb5<ide_set_handler+55/60>
I think maybe it smells like a configuration problem, I have a pair of ATAPI drives on the second ide which I run with SCSI emulation. I'll see if I can get a better look, with arguments to the calls.
Thanks,
Tom
Signature · 1 line
The Daemons lurk and are dumb. -- Emerson