From: Eckhard Jokisch <e.jokisch@u-code.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [me to]2.4.0-test12 randomly hangs up
Date: Wed, 13 Dec 2000 21:07:23 +0000 [thread overview]
Message-ID: <00121321070701.22766@eckhard> (raw)
On Mit, 13 Dez 2000, Jani Monoses wrote:
> Mine too did this 15 minutes ago.Just moving the mouse around in X and
> suddenly complete freeze.No response to ping either.Such a thing didn't
> happen for a long time to me.The only thing I've changed since test11 is
> compiling fb+fbvesa in.
I made similar experience but it also involved 2.2.18 in combination with
KDE2.0 and ALSA.
The machine "hung" but worked heavily on the HD and after about one hour it
worked abain at least on the console.
One thing I found was the current CVS from ALSA seems to have a bug.
Another thing is tha the 8139too driver prodices
Dec 13 12:34:09 eckhard kernel: eth0: Abnormal interrupt, status 00000006.
Dec 13 12:34:19 eckhard kernel: eth0: Abnormal interrupt, status 00000002.
Dec 13 12:34:44 eckhard last message repeated 7 times
Dec 13 12:35:50 eckhard last message repeated 16 times
Dec 13 12:36:23 eckhard last message repeated 4 times
Dec 13 12:37:49 eckhard last message repeated 15 times
Dec 13 12:38:21 eckhard last message repeated 7 times
Dec 13 12:38:22 eckhard kernel: eth0: Abnormal interrupt, status 00000006.
Dec 13 12:38:24 eckhard kernel: eth0: Abnormal interrupt, status 00000002.
in /var/log/messages and the machine is getting very slow then.
This is even worse when compiled as a module.
With rlt8139 driver this does not happen. The chip is 8139A.
Eckhard Jokisch
-------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2000-12-13 20:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=00121321070701.22766@eckhard \
--to=e.jokisch@u-code.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox