From: malahal@us.ibm.com
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Mike Anderson <andmike@linux.vnet.ibm.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Alexander Beregalov <a.beregalov@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
linux-scsi@vger.kernel.org, David Miller <davem@davemloft.net>,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: next-20081119: general protection fault: get_next_timer_interrupt()
Date: Mon, 24 Nov 2008 16:09:02 -0800 [thread overview]
Message-ID: <20081125000902.GA24251@us.ibm.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0811242327130.3235@localhost.localdomain>
Thomas Gleixner [tglx@linutronix.de] wrote:
> On Mon, 24 Nov 2008, Mike Anderson wrote:
> > Thomas Gleixner <tglx@linutronix.de> wrote:
> > > Yeah, block could it be as well. Jens, Mike ?
> >
> > I added a comment to bug 12020 on Thursday about a few other systems that
> > where seeing the signature shown in bug 12020. It appeared from debug that
> > there where a few paths that where adding timers for requests that where
> > not expected.
> >
> > http://bugzilla.kernel.org/show_bug.cgi?id=12020
> >
> > It would be good to know if the debug patch below effects your problem as while.
> >
> > If it does we need to investigated a solution to resolve not adding a
> > timer for these requests.
The block timer code calls del_timer(), should it call del_timer_sync()?
It is possible although unlikely that you are hitting del_timer_sync vs
del_timer problem in the block timeout code. Can only be seen on SMP
systems though!
--Malahal.
next prev parent reply other threads:[~2008-11-25 0:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 15:14 next-20081119: general protection fault: get_next_timer_interrupt() Alexander Beregalov
2008-11-19 21:14 ` Thomas Gleixner
2008-11-21 10:50 ` Alexander Beregalov
2008-11-24 17:43 ` Thomas Gleixner
2008-11-24 19:15 ` James Bottomley
2008-11-24 19:31 ` Thomas Gleixner
2008-11-24 21:35 ` Mike Anderson
2008-11-24 22:33 ` Thomas Gleixner
2008-11-24 23:42 ` malahal
2008-11-25 0:09 ` malahal [this message]
2008-11-25 0:57 ` Stephen Rothwell
2008-11-25 2:08 ` malahal
2008-11-25 8:51 ` Jens Axboe
2008-11-25 16:59 ` malahal
2008-11-25 17:14 ` Alexander Beregalov
2008-11-25 17:43 ` Jens Axboe
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=20081125000902.GA24251@us.ibm.com \
--to=malahal@us.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=a.beregalov@gmail.com \
--cc=andmike@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).