From: Jorge Carminati <jcarminati@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel freezing....
Date: Fri, 7 Dec 2001 05:30:20 -0800 (PST) [thread overview]
Message-ID: <20011207133020.41163.qmail@web13905.mail.yahoo.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 2566 bytes --]
Hi!
Well, I have some news regarding my case.
Brief for the impatient: IMHO it's a kernel bug.
7pm: I arrived home from work; as suggested by Alan I ran memtest86
(v.2.8). I let it make two passes as to have a first impression. NO
memory error was found. It took ~24 minutes for each pass (240 Mb total
(256Mb - 16Mb used for video card)). Meanwhile I was compiling in my
Mandrake workstation a kernel optimized for i386 as suggested by
François Cami.
7.50pm: I spent a couple of minutes repairing with fsck my ext3
partition; had a lot of freezes the previous day.
8pm: I ftped the kernel to the notebook (first attempt failed; kernel
froze again (Red Hat's default kernel) second attempt was ok). Rebooted
and logged in in init 1. I typed some commands, and later started X
Window, no freeze. Next I launched lot of applications, just to try a
very basic memory stress. I started to enjoy Linux in my notebook.
After an uptime of 1:40 hour I decided to switch to the next kernel
optimized version: i486.
9.40pm: Booted i486 kernel. Made some basic tests, played with XFree86,
while at the same time for first time I was compiling a newer kernel
using this notebook (using Red Hat's 7.2 default gcc, etc). This newer
kernel was optimized for 586/K5. Rebooted after an uptime of 30 min
without a freeze.
10:15pm: Played a lot with this new kernel for almost 1:30 hour, no
freeze suffered.
Last thing I did was to compile again a newer kernel for the next cpu
type (I think it´s named "Pentium Standard" or something similar). I´ll
test probably on saturday this kernel as I went to sleep.
In all the cases the compiled kernel had set exactly the same options,
**just changed the cpu optimization type**. Kernel version 2.4.16.
I was thinking, as suggested by Alan, to ran memtest86 all night long,
but as didn't suffered in 4 hours a freeze, I discarded this idea.
Conclusion: IMHO it´s a kernel bug. The same .config optimized for AMD
freezes, and Red Hat's default kernel does the same. Luckily for my
investment it´s not a memory bug.
I'll investigate when this bug is introduced playing with the cpu
optimization setting. I'll post my results probably next monday.
If anyone has any kind of suggestion or want me to test something in
particular please let me know.
* PLEASE cc to jcarminati@yahoo.com for any answer. I'm not subscribed.
*
Kind regards and thanks again.
Jorge Carminati.
jcarminati@yahoo.com
__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com
next reply other threads:[~2001-12-07 13:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 13:30 Jorge Carminati [this message]
2001-12-07 13:51 ` Kernel freezing Alan Cox
2001-12-07 15:03 ` Jorge Carminati
[not found] <3C11096E.9040102@wanadoo.fr>
2001-12-07 19:23 ` Jorge Carminati
-- strict thread matches above, loose matches on Subject: below --
2001-12-06 14:16 Jorge Carminati
2001-12-06 14:35 ` Alan Cox
2001-12-06 14:45 ` Jorge Carminati
2001-12-06 14:04 Jorge Carminati
[not found] <E16Buao-00010V-00@the-village.bc.nu>
2001-12-06 13:17 ` Jorge Carminati
[not found] <3C0EDAEE.6080608@wanadoo.fr>
2001-12-06 13:11 ` Jorge Carminati
2001-12-06 2:20 Jorge Carminati
2001-12-06 6:49 ` Jaswinder Singh
2001-12-06 13:13 ` Jorge Carminati
2001-12-06 8:12 ` jcassidy
2001-12-06 12:57 ` Jorge Carminati
2001-12-07 17:34 ` Pavel Machek
2001-12-08 21:12 ` Mike Castle
2001-12-08 23:21 ` jcassidy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20011207133020.41163.qmail@web13905.mail.yahoo.com \
--to=jcarminati@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.