From: Lee Revell <rlrevell@joe-job.com>
To: Ed Sweetman <safemode@comcast.net>
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: 2.6.16-rc6-ide1 irq trap, io hang problem solved?
Date: Tue, 21 Mar 2006 19:06:35 -0500 [thread overview]
Message-ID: <1142985995.4532.195.camel@mindpipe> (raw)
In-Reply-To: <442089CB.1000008@comcast.net>
On Tue, 2006-03-21 at 18:18 -0500, Ed Sweetman wrote:
> I've seen some traffic here to suggest that the problem was tracked
> down, but I saw nothing about it being solved completely. Currently my
> system hangs whenever an irq trap message appears, usually after some
> sort of disk io on SATA drives. Is it fixed in the GIT patchset recently
> posted or is this still open?
Are you referring to the "Losing ticks" bug? What is the exact error
message that you get? Does the system hang momentarily or have to be
rebooted?
Lee
next prev parent reply other threads:[~2006-03-22 0:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 23:18 2.6.16-rc6-ide1 irq trap, io hang problem solved? Ed Sweetman
2006-03-22 0:06 ` Lee Revell [this message]
2006-03-22 0:25 ` Ed Sweetman
2006-03-22 3:26 ` Ed Sweetman
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=1142985995.4532.195.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=safemode@comcast.net \
/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