From: Michael Breuer <mbreuer@majjas.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Regressionhung task during raid rebuild 2.6.33 rc5 was: Re: 2.6.33RC3 hung task - jbd2/dm-1-8 (during raid rebuild)
Date: Sat, 30 Jan 2010 15:00:24 -0500 [thread overview]
Message-ID: <4B648FD8.6060904@majjas.com> (raw)
In-Reply-To: <201001302057.59529.rjw@sisk.pl>
On 1/30/2010 2:57 PM, Rafael J. Wysocki wrote:
> On Saturday 30 January 2010, Michael Breuer wrote:
>
>> On 1/10/2010 4:47 PM, Michael Breuer wrote:
>>
>>> System crashed (watchdog reset).
>>>
>>> Was doing a raid rebuild at the time (raid6).
>>>
>>> I typed, 'yumdownloader --source virtlib' ... system froze, then
>>> rebooted on the watchdog reset.
>>>
>>> I've attached the log extract from the event as well as dmesg.
>>>
>>>
>>>
>> Hit this again - system doesn't crash now - just get the hung task
>> warning (log extract attached). System seems to keep running (albeit the
>> rebuild is incredibly slow on 2.6.33 rc5 - approx 6500K/sec vs. about
>> 80,000K/sec on 2.6.32.4.
>>
>> Looks like it may be triggered by disk io during the rebuild. This time
>> I had typed, "sync." "sync" hung for a long while but did eventually
>> complete.
>>
> Is this the bug tracked as http://bugzilla.kernel.org/show_bug.cgi?id=15125 ?
>
> Rafael
>
Yes - although the behavior is different on rc5 vs. rc3. I think it's
the same.
prev parent reply other threads:[~2010-01-30 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-10 21:47 2.6.33RC3 hung task - jbd2/dm-1-8 (during raid rebuild) Michael Breuer
2010-01-30 19:21 ` Regressionhung task during raid rebuild 2.6.33 rc5 was: " Michael Breuer
2010-01-30 19:26 ` Regression: hung " Michael Breuer
2010-01-30 19:57 ` Regressionhung " Rafael J. Wysocki
2010-01-30 20:00 ` Michael Breuer [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=4B648FD8.6060904@majjas.com \
--to=mbreuer@majjas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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