From: Ed Tomlinson <tomlins@cam.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [BUG] linux 2.4.1 to 2.4.1-ac3 hangs
Date: Wed, 7 Feb 2001 07:30:46 -0500 [thread overview]
Message-ID: <01020707304600.29374@oscar> (raw)
In-Reply-To: <01020617572800.00870@oscar>
In-Reply-To: <01020617572800.00870@oscar>
Hi,
In retrospect it looks like there are three problems shown here.
1. The are the packet error messages which have just started appearing in
ac3, but do not seem to hurt anything... I am forced to use pppoe and do have
the mtu(s) set correctly (1500 on eth1, 1492 on ppp0 (which runs on eth1), all
internal PC should have 1454 (one was incorrect and is now fixed)). I am
using the ipchains module and have not tried the iptables filter to clamp
mtus.
2. There is a PCI routing error reported during boot. The kernel does seem
to resolve this ok - is this message anything to worry about?
3. System hangs. This box has been quite stable. The hangs started
appearing around 2.4.1 or so. I very much doubt they are heat releated. I
have had heat problems in the past an have moved the kit into a much better
case. The old symptoms (ide tape problems) have gone and not returned even
on the hotest summer day... Next time this happens I will try to telnet or
ssh into box to see if anything is active, I will also setup a UPS on the box
and see it that can shut it down. Its interesting that the software watchdog
does not get triggered.
TIA,
Ed Tomlinson <tomlins@cam.org>
-
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/
prev parent reply other threads:[~2001-02-07 12:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-06 22:57 [BUG] linux 2.4.1 to 2.4.1-ac3 hangs Ed Tomlinson
2001-02-07 12:30 ` Ed Tomlinson [this message]
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=01020707304600.29374@oscar \
--to=tomlins@cam.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox