From: Simon Huggins <huggie@earth.li>
To: linux-kernel@vger.kernel.org
Subject: Scheduler broken? sdhci issues with scheduling
Date: Fri, 29 Feb 2008 11:52:57 +0000 [thread overview]
Message-ID: <20080229115256.GG24533@paranoidfreak.co.uk> (raw)
[ Please Cc me on replies ]
I had a bug with sdhci which Pierre Ossman looked at for me.
In the end essentially the fix was to use HZ=1000 and nothing else.
Pierre seemed to think that this was a bug in the scheduler.
I'm interested if someone who groks the scheduler could take a look at
the mmc/* code and see if it's abusing HZ or if there's anything
obviously wrong there. If it's not then perhaps there really is a bug
in the scheduler?
See
http://list.drzeus.cx/pipermail/sdhci-devel/2008-February/002164.html
http://list.drzeus.cx/pipermail/sdhci-devel/2008-January/002142.html
Here's the log that caused him to suspect the scheduler:
http://list.drzeus.cx/pipermail/sdhci-devel/2007-December/002086.html
and his post saying so:
http://list.drzeus.cx/pipermail/sdhci-devel/2007-December/002087.html
Originally I tried to narrow it down:
http://list.drzeus.cx/pipermail/sdhci-devel/2007-November/002072.html
and shows a commit that seemed to "fix" it for me
http://list.drzeus.cx/pipermail/sdhci-devel/2007-November/002072.html
but apparently the commit I reverted was good
http://list.drzeus.cx/pipermail/sdhci-devel/2007-November/002078.html
I'm happy to provide more information or try different kernels/config
options etc (I really should upgrade the kernel on my laptop anyway).
Thanks,
--
----------( "An excellent suggestion sir, with only two )----------
Simon ----( minor flaws...." - Kryten )---- Nomis
Htag.pl 0.0.22
next reply other threads:[~2008-02-29 12:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 11:52 Simon Huggins [this message]
2008-02-29 13:34 ` Scheduler broken? sdhci issues with scheduling Ingo Molnar
2008-02-29 13:51 ` Ingo Molnar
2008-02-29 14:00 ` Ingo Molnar
2008-02-29 19:39 ` Simon Huggins
2008-02-29 20:39 ` Ingo Molnar
2008-03-01 12:42 ` Simon Huggins
2008-03-01 14:08 ` Pierre Ossman
2008-03-02 10:40 ` Pavel Machek
2008-03-02 18:04 ` Simon Huggins
2008-03-03 19:43 ` Pierre Ossman
2008-03-03 20:38 ` Pavel Machek
2008-03-03 21:05 ` Pierre Ossman
2008-03-13 21:17 ` Simon Huggins
2008-03-15 15:04 ` Pierre Ossman
2008-04-20 21:07 ` Simon Huggins
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=20080229115256.GG24533@paranoidfreak.co.uk \
--to=huggie@earth.li \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.