All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: Tejun Heo <tj@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>, linux-kernel@vger.kernel.org
Subject: Re: WARNING: at block/genhd.c:1556 disk_clear_events+0xdc/0xf0()
Date: Sat, 9 Apr 2011 10:34:49 +0100	[thread overview]
Message-ID: <20110409093449.GA10016@sucs.org> (raw)
In-Reply-To: <20110406213718.GA14139@mtj.dyndns.org>

On Wed, Apr 06, 2011 at 02:37:18PM -0700, Tejun Heo wrote:
> 
> The problem would be quite timing dependent.  It would be great if you
> can prepare a setup where you can reproduce the problem on some
> regular basis and make sure that the problem goes away with the patch
> applied.

Try as I might I cannot even reproduce the problem with the original
problem kernels. I've tried all sorts (such as plugging in multiple USB
disks and killing/restarting services such as udisks) but the problem
has refused to show itself again. Originally I saw the message three
times over a two days period and two of those were within 10 seconds of
boot. I've booted the same kernel a dozen times but the error never
comes back...

-- 
Sitsofe | http://sucs.org/~sits/

  reply	other threads:[~2011-04-09  9:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04 21:16 WARNING: at block/genhd.c:1556 disk_clear_events+0xdc/0xf0() Sitsofe Wheeler
2011-04-05  1:51 ` Jens Axboe
2011-04-06 13:04 ` Tejun Heo
2011-04-06 21:26   ` Sitsofe Wheeler
2011-04-06 21:37     ` Tejun Heo
2011-04-09  9:34       ` Sitsofe Wheeler [this message]
2011-04-10 14:59         ` Sitsofe Wheeler
2011-04-13 20:00           ` Tejun Heo
2011-04-15  9:01             ` Tejun Heo
2011-04-15 18:20               ` Tejun Heo
2011-04-15 21:41                 ` Sitsofe Wheeler
2011-04-21 17:38                   ` Tejun Heo
2011-04-21 18:43                     ` Tejun Heo
2011-05-10 16:48                       ` Tejun Heo

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=20110409093449.GA10016@sucs.org \
    --to=sitsofe@yahoo.com \
    --cc=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@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.