From: Mike Frisch <mfrisch@saturn.tlug.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Athlon/MSI mobo combo broken?
Date: Wed, 8 Aug 2001 18:14:06 -0400 [thread overview]
Message-ID: <20010808181406.A9258@saturn.tlug.org> (raw)
In-Reply-To: <419E5D46960FD211A2D5006008CAC79902E5C425@pcmailsrv1.sac.unify.com>
In-Reply-To: <419E5D46960FD211A2D5006008CAC79902E5C425@pcmailsrv1.sac.unify.com>; from mmt@unify.com on Wed, Aug 08, 2001 at 02:35:07PM -0700
On Wed, Aug 08, 2001 at 02:35:07PM -0700, Manuel A. McLure wrote:
> Let me add my voice to the crowd. I have the same MSI K7T Turbo with an
> Athlon TBird 900MHz and 256M of PC133 SDRAM, and kernel 2.4.6 runs
> rock-stable on it. However, 2.4.7 hangs hard after a day or so of uptime -
> no response to pings, can't switch from X to a virtual console, etc. Sysrq-B
> will reboot, but other Sysrq-keys (like Sysrq-S or Sysrq-U) don't seem to
> work. Unfortunately I am invariably in X when this happens so I don't get to
> see ant OOPS text, and there is no OOPS information in the system log after
> the reboot.
I do not know if this is related since it seems to be VIA-based boards
being mentioned here, but I am also experiencing hard lockups on
Athlon-optimized 2.4.7 (and 2.4.7-ac?). My board is an ASUS A7A266 (ALi
MaGik chipset), Micro PC2100 DDR RAM, and an Athlon T-Bird 1.2GHz.
next prev parent reply other threads:[~2001-08-08 22:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-08 21:35 Manuel A. McLure
2001-08-08 22:14 ` Mike Frisch [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-23 16:02 Felix von Leitner
2001-07-23 17:32 ` Alan Cox
2001-07-23 22:05 ` Dan Hollis
2001-07-25 14:25 ` Miloslaw Smyk
2001-07-26 19:39 ` Gerbrand van der Zouw
2001-08-08 17:08 ` jury gerold
2001-08-08 21:08 ` Mark Hahn
2001-08-09 8:59 ` gjury
2001-08-09 14:55 ` Mike Frisch
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=20010808181406.A9258@saturn.tlug.org \
--to=mfrisch@saturn.tlug.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
all inboxes | Powered by JetHome®