From: Michael Frank <mflt1@micrologica.com.hk>
To: matthew@greycloaklabs.ca
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: PROBLEM: kswapd and toshiba libretto 50ct
Date: Sat, 2 Aug 2003 17:13:41 +0800 [thread overview]
Message-ID: <200308021713.41569.mflt1@micrologica.com.hk> (raw)
I used 2.4 on a 100MHz L60 until it passed away recently...
Stop overclocking!
If problem persists, config you kernel for serial console and
grab the oops.
Regards
Michael
--
Powered by linux-2.6-test2-mm2. Compiled with gcc-2.95-3 - mature and rock solid
2.4/2.6 kernel testing: ACPI PCI interrupt routing, keyboard failure with
ACPI, PCI IRQ sharing and swsusp
2.6 kernel testing: PCMCIA yenta_socket, Suspend to RAM with ACPI S1-S3.
More info on swsusp: http://sourceforge.net/projects/swsusp/
next reply other threads:[~2003-08-02 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-02 9:13 Michael Frank [this message]
2003-08-12 13:24 ` PROBLEM: kswapd and toshiba libretto 50ct Matthew Peters
2003-08-12 13:50 ` Michael Frank
-- strict thread matches above, loose matches on Subject: below --
2003-08-02 0:50 Matthew Peters
2003-08-02 6:37 ` Willy Tarreau
2003-08-02 8:53 ` Matthew Peters
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=200308021713.41569.mflt1@micrologica.com.hk \
--to=mflt1@micrologica.com.hk \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@greycloaklabs.ca \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).