From: Kevin Brosius <cobra@compuserve.com>
To: kernel <linux-kernel@vger.kernel.org>
Subject: Re: machine hangs in 2.6 bk latest
Date: Thu, 16 Oct 2003 21:17:06 -0400 [thread overview]
Message-ID: <3F8F4312.FDCECC3B@compuserve.com> (raw)
In-Reply-To: 3F8B4EC4.2584A2E9@compuserve.com
Kevin Brosius wrote:
>
> Kevin Brosius wrote:
> >
> > I've noticed a pair of machine hangs today with latest 2.6.0 bk tree.
> > So far, I've been unable to retrieve information from the test machine,
> > as the network is down, console is unresponsive and in power save at the
> > time of the hang. (I've haven't tried Magic-Sysrq yet.)
> >
> > After reboot, logs are truncated, so no useful information there either.
> >
> > System is base SuSE 8.2, running 2.6.0 bk, pulled today (Sun 16:00 EST
> > or earlier).
> >
> > Dual AMD MP CPUs, with reiserfs main fs on Mylex RAID disks. 2.6 bk
> > kernel from about a week ago was stable on this machine. I'll try and
> > capture more info. Any thoughts, please copy my email.
>
> bk pulls from today behave the same. The lockup seems to occur while
> using an ssh forwarded X connection and moving a large mozilla window on
> a remote machine.
>
> The server machine is hard locked. Alt-Sysrq does not respond at all.
It looks like
ChangeSet 1.1237.1.117 2003/10/13 16:30:26 torvalds@home.osdl.org
Revert recent SMP timer changes - they cause deadlocks
resolved this problem. Thanks Linus! :)
--
Kevin
prev parent reply other threads:[~2003-10-17 1:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-12 21:00 machine hangs in 2.6 bk latest Kevin Brosius
2003-10-14 1:17 ` Kevin Brosius
2003-10-17 1:17 ` Kevin Brosius [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=3F8F4312.FDCECC3B@compuserve.com \
--to=cobra@compuserve.com \
--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;
as well as URLs for NNTP newsgroup(s).