From: Andrew Benton <b3nton@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: ata2: lost interrupt with kernel 2.6.34-rc1
Date: Fri, 12 Mar 2010 00:01:41 +0000 [thread overview]
Message-ID: <4B998465.2080009@gmail.com> (raw)
In-Reply-To: <4B997FB1.3000404@garzik.org>
On 11/03/10 23:41, Jeff Garzik wrote:
> On 03/11/2010 11:57 AM, Andrew Benton wrote:
>> Hello,
>> I'm not subscribed to this list, sorry if it's the wrong place to send
>> this.
>> I've been having problems with 2.6.34-rc1, when the system tries to
>> access a
>> lot of files (eg, if I recompile the kernel) it freezes for about 10
>> seconds
>> or so and then I get a message like this in the sys.log:
>
> Does 2.6.33 also have this behavior?
>
No, 2.6.33 works fine. This freezing, waiting for the disk to be reset is
new behavior in 2.6.34-rc1
Andy
prev parent reply other threads:[~2010-03-12 0:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 16:57 ata2: lost interrupt with kernel 2.6.34-rc1 Andrew Benton
2010-03-11 23:41 ` Jeff Garzik
2010-03-12 0:01 ` Andrew Benton [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=4B998465.2080009@gmail.com \
--to=b3nton@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).