From: Jochen Hein <jochen@jochen.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [2.6.0] Thinkpad 390E hangs after some time
Date: Fri, 09 Jan 2004 16:52:53 +0100 [thread overview]
Message-ID: <87isjlw23u.fsf@echidna.jochen.org> (raw)
In-Reply-To: Pine.LNX.4.44.0401071146140.2266-100000@bigblue.dev.mdolabs.com
Davide Libenzi <davidel@xmailserver.org> writes:
> On Wed, 7 Jan 2004, Jochen Hein wrote:
>
>>
>> I'm running 2.6.0 (and .1-rc1) on an IBM Thinkpad 390E with 196MB RAM.
>> After some time - sometimes an hour or more, sometimes after a few
>> minutes, performance suffers, the machine feels sluggish. After some
>> more minutes, the machine hangs. No NMI-oopser, no ping, no panic
>> LEDs blinking.
>
> I had a very similar problem on two of my machines (CPQ laptop and IBM
> NetVista). [...], but building
> with 2.95.3 made my machines stable.
Not here. compiled with both:
root@hermes:/usr/src# gcc -v
Reading specs from /usr/lib/gcc-lib/i486-linux/3.3.2/specs
Konfiguriert mit: ../src/configure -v
--enable-languages=c,c++,java,f77,pascal,objc,ada,treelang
--prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info
--with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared
--with-system-zlib --enable-nls --without-included-gettext
--enable-__cxa_atexit --enable-clocale=gnu --enable-debug
--enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc
i486-linux
Thread model: posix
gcc-Version 3.3.2 (Debian)
root@hermes:/usr/src# gcc-2.95 -v
Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs
gcc version 2.95.4 20011002 (Debian prerelease)
Anyway, got a new (faster) laptop and will move my 2.6 tests there.
Jochen
--
#include <~/.signature>: permission denied
next prev parent reply other threads:[~2004-01-09 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 19:02 [2.6.0] Thinkpad 390E hangs after some time Jochen Hein
2004-01-07 19:56 ` Davide Libenzi
2004-01-09 15:52 ` Jochen Hein [this message]
2004-01-09 16:26 ` Davide Libenzi
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=87isjlw23u.fsf@echidna.jochen.org \
--to=jochen@jochen.org \
--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.