All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Nathan Scott <nathans@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cfq_update_io_seektime oops
Date: Thu, 15 Jun 2006 08:50:06 +0200	[thread overview]
Message-ID: <20060615065006.GM1522@suse.de> (raw)
In-Reply-To: <20060615162107.B898607@wobbly.melbourne.sgi.com>

On Thu, Jun 15 2006, Nathan Scott wrote:
> On Thu, Jun 15, 2006 at 08:01:53AM +0200, Jens Axboe wrote:
> > The patch for this was just merged in 2.6.17-rc6-git last night, so it
> 
> Ah, great - thanks.
> 
> > should be fine now. Just curious - did you have any slab debugging
> > features enabled?
> 
> Hmm, lemme see - no, not slab for this particular build - here's
> my CONFIG_DEBUG_* list:

Ok, thanks for checking. Just wondering what the likelyhood of
->seek_samples being -36 initially, which will cause this crash. You're
now the 2nd person to have hit this bug.

-- 
Jens Axboe


      reply	other threads:[~2006-06-15  6:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-15  5:21 cfq_update_io_seektime oops Nathan Scott
2006-06-15  6:01 ` Jens Axboe
2006-06-15  6:21   ` Nathan Scott
2006-06-15  6:50     ` Jens Axboe [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=20060615065006.GM1522@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathans@sgi.com \
    /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.