Oops with 2.4.23
Quoted 3 lines · Arnaud Fontaine
Sorry, i forgot to tell if i had error. So after 11 pass, i have had no error. I have also test with cpuburn which printed nothing after 30 minutes.
disable the SWAP, and run three burnMMX for 30 minutes:
# swapoff -a $ ./burnMMX P || echo $? &
Quoted 7 lines · Xose Vazquez Perez
Quoted 3 lines · Arnaud Fontaine
Sorry, i forgot to tell if i had error. So after 11 pass, i have had no error. I have also test with cpuburn which printed nothing after 30 minutes.
disable the SWAP, and run three burnMMX for 30 minutes:
How does disabling swap help?
Quoted 1 line · Mike Fedyk
How does disabling swap help?
It helps to not test the SWAP memory :-). Really the important thing is 'P' flag in burnMMX. Otherwise it will test _only_ the cache memory of the processor.
Quoted 8 lines · Xose Vazquez Perez
Quoted 3 lines
Sorry, i forgot to tell if i had error. So after 11 pass, i have had no error. I have also test with cpuburn which printed nothing after 30 minutes.
disable the SWAP, and run three burnMMX for 30 minutes:
# swapoff -a $ ./burnMMX P || echo $? &
Hello,
Do i ran burnMMX during more than 30 minutes and nothing reported. Do you have an other idea ?
Thanks for your help.
Arnaud
Signature · 7 lines
Arnaud Fontaine <[email protected]> - http://www.andesi.org/ GnuPG Public Key available on pgp.mit.edu Fingerprint: D792 B8A5 A567 B001 C342 2613 BDF2 A220 5E36 19D3 -- Make sure input cannot violate the limits of the program. - The Elements of Programming Style (Kernighan & Plaugher)
Quoted 2 lines · Arnaud Fontaine
Do i ran burnMMX during more than 30 minutes and nothing reported. Do you have an other idea ?
next steps :
- run burnP5 for 30 min.
- try 2.4.24-pre2
Quoted 4 lines · Xose Vazquez Perez
next steps :
- run burnP5 for 30 min.
- try 2.4.24-pre2
Hello,
So, i have compiled 2.4.24-pre2 as you say. In addition, i had this Oops after every reboot on 2.4.23 (nothing with 2.4.18 which works fine).
Then, I reboot again on 2.4.24-pre2 and ran burnP5 during 40 minutes to be sure. I had nothing and no oops at the moment. If i see this Oops with 2.4.24 (nothing now ;)), i'll run burnP5 on this and i'll say you what i have.
Thanks for your help...
++ Arnaud
Signature · 7 lines
Arnaud Fontaine <[email protected]> - http://www.andesi.org/ GnuPG Public Key available on pgp.mit.edu Fingerprint: D792 B8A5 A567 B001 C342 2613 BDF2 A220 5E36 19D3 -- Be free and open and breezy! Enjoy! Things won't get any better so get used to it.
Quoted 8 lines · Arnaud Fontaine
Quoted 4 lines · Xose Vazquez Perez
next steps :
- run burnP5 for 30 min.
- try 2.4.24-pre2Hello,
Quoted 7 lines
So, i have compiled 2.4.24-pre2 as you say. In addition, i had this Oops after every reboot on 2.4.23 (nothing with 2.4.18 which works fine).
Then, I reboot again on 2.4.24-pre2 and ran
burnP5during 40 minutes to be sure. I had nothing and no oops at the moment. If i see this Oops with 2.4.24 (nothing now ;)), i'll run burnP5 on this and i'll say you what i have.
Could you please try 2.4.23 with the patch at
http://www.hardrock.org/kernel/current-updates/linux-2.4.23-updates.patch
I would like to know if that helps or not.
Thanks and regards
James
Quoted 5 lines
Thanks for your help...
++ Arnaud
Signature · 5 lines
James Bourne | Email: [email protected] Unix Systems Administrator | WWW: http://www.hardrock.org Custom Unix Programming | Linux: The choice of a GNU generation ---------------------------------------------------------------------- "All you need's an occasional kick in the philosophy." Frank Herbert