From: Donald Parsons <dparsons@brightdsl.net>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Kernel <linux-kernel@vger.kernel.org>,
Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: 2.6.17-...: looong writeouts
Date: Sat, 24 Jun 2006 22:33:04 -0400 [thread overview]
Message-ID: <1151202784.4469.8.camel@danny.parsons.org> (raw)
In-Reply-To: <1151194288.4469.4.camel@danny.parsons.org>
On Sat, 2006-06-24 at 20:11 -0400, Donald Parsons wrote:
> On Sat, 2006-06-24 at 21:36 +0400, Alexey Dobriyan wrote:
> > On Sat, Jun 24, 2006 at 06:50:52PM +0200, Arjan van de Ven wrote:
> > > just a random question to rule things out: can you check if laptop mode
> > > is enabled? (see the /proc/sys/vm/laptop_mode file). Laptop mode will
> > > have the effect of grouping writes together, so if that got enabled
> > > accidentally for some reason, that could explain the behavior you are
> > > seeing. (and it would narrow down the "what broke" search problem to
> > > something that is a lot easier to work on)
> >
> > Mine is not laptop and I've never enabled it.
> >
>
> Mine is a laptop T43 running FC3 and the mode is not enabled:
>
> # cat /proc/sys/vm/laptop_mode
> 0
>
> I have rebooted to 2.6.17 and the problem is there too. It
> happened when I tried to paste the above path from the mail.
>
> Don
Another data point (now 2.6.17):
I started up Streamtuner to see if it was affected. It is not.
While I was trying to get a window to respond for many seconds
I noticed sound continued on with no interference at all.
Don
next prev parent reply other threads:[~2006-06-25 2:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-24 16:30 2.6.17-...: looong writeouts Donald Parsons
2006-06-24 16:50 ` Arjan van de Ven
2006-06-24 17:36 ` Alexey Dobriyan
2006-06-24 17:41 ` Arjan van de Ven
2006-06-25 0:11 ` Donald Parsons
2006-06-25 2:33 ` Donald Parsons [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-24 15:15 Alexey Dobriyan
2006-06-29 3:55 ` Andrew Morton
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=1151202784.4469.8.camel@danny.parsons.org \
--to=dparsons@brightdsl.net \
--cc=adobriyan@gmail.com \
--cc=arjan@infradead.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).