From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
Bob Copeland <me@bobcopeland.com>
Subject: Re: git pull on linux-next makes my system crawl to its knees and beg for mercy
Date: Fri, 18 Dec 2009 18:38:20 +0100 [thread overview]
Message-ID: <200912181838.20204.bzolnier@gmail.com> (raw)
In-Reply-To: <43e72e890912180926oad3b09fl6b7951864a836700@mail.gmail.com>
On Friday 18 December 2009 06:26:29 pm Luis R. Rodriguez wrote:
> on my kernel logs. Bewildered with this issue I set out to prove to
> myself this issue was not a 2.6.32 issue and booted other kernels,
> including Ubuntu's distro kernel on 2.6.31 and then later my own built
> fresh 2.6.27.41 kernel. The issue was reproducible on all three
> kernels!
>
> This lead me to believe this was a system / hard drive issue and
> embraced myself for a system fix. I yet needed to prove this was
Just some hints for ruling out the system / hard drive problem.
smartctl -a /dev/sdx is your friend for checking your disk (keep an eye
on anything suspicious like re-allocated sector count going up etc.)
It could be also fs related issue that shows up only under specific
conditions (i.e. almost full partition -- some file-systems starts to
crawl when the amount of available free space gets low).
HTH
--
Bartlomiej Zolnierkiewicz
next prev parent reply other threads:[~2009-12-18 17:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 17:26 git pull on linux-next makes my system crawl to its knees and beg for mercy Luis R. Rodriguez
2009-12-18 17:38 ` Bartlomiej Zolnierkiewicz [this message]
2009-12-18 19:19 ` Luis R. Rodriguez
2009-12-18 19:55 ` Luis R. Rodriguez
2009-12-18 20:51 ` Luis R. Rodriguez
2009-12-18 21:13 ` Luis R. Rodriguez
2009-12-18 21:56 ` Stephen Rothwell
2009-12-18 22:03 ` Luis R. Rodriguez
2009-12-23 15:27 ` Denys Vlasenko
2009-12-23 16:20 ` Luis R. Rodriguez
2009-12-23 17:11 ` Denys Vlasenko
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=200912181838.20204.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=me@bobcopeland.com \
--cc=sfr@canb.auug.org.au \
/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.