From: Jens Axboe <jaxboe@fusionio.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>, Michal Hocko <mhocko@suse.cz>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.39-rc4 BUG: unable to handle kernel NULL pointer dereference at 0000000c IP: cfq_insert_request+0x1d/0x3f5
Date: Thu, 21 Apr 2011 17:30:23 +0200 [thread overview]
Message-ID: <4DB04D8F.2000708@fusionio.com> (raw)
In-Reply-To: <x49r58vprw2.fsf@segfault.boston.devel.redhat.com>
On 2011-04-21 17:04, Jeff Moyer wrote:
> Jens Axboe <axboe@kernel.dk> writes:
>
>> On 21/04/2011, at 09.16, Michal Hocko <mhocko@suse.cz> wrote:
>>
>>> On Wed 20-04-11 19:33:19, Jens Axboe wrote:
>>>> On 2011-04-20 15:29, Michal Hocko wrote:
>>>>> On Wed 20-04-11 15:13:15, Jens Axboe wrote:
>>>>>> On 2011-04-20 14:58, Michal Hocko wrote:
>>> [...]
>>>>>>> [ 31.207888] Oops: 0000 [#1] PREEMPT [ 31.208186] last sysfs file: /sys/devices/pci0000:00/0000:00:1f.2/host0/target0:0:0/0:0:0:0/block/sda/queue/scheduler
>>>>>>
>>>>>> Ahh hang on, this may be a good clue. Does your boot scripts change the
>>>>>> IO scheduler?
>>>>>
>>>>> Good one...
>>>>> Yes, I have:
>>>>> echo deadline > /sys/block/sda/queue/scheduler
>>>>> in /etc/rc.local
>>>>>
>>>>> I am able to boot after I remove it. This is the first time I have seen
>>>>> "last sysfs file" being useful.
>>>>> Still want me to test the patch from the other email?
>>>>
>>>> Is this a new addition to your system? IOW, how certain are you that
>>>> this is a regression that occured between rc3 and rc4?
>>>
>>> No, I am setting the scheduler this way for quite some time. If I use it
>>> rc4 explodes while rc3 boots just fine. I am wondering, can this be a
>>> timing issue? I am able to set the scheduler after system settles down
>>> after boot and kde starts.
>>>
>>> I am going to bisect, let's see if I can find anything.
>>
>> Thanks, that would be great!
>
> OK, this is a long shot, but in a derivative kernel, I saw what may be
> the same issue. Is this kernel built with CONFIG_BLK_CGROUP=n by
> chance? The exact problem I saw was a panic on boot in
> cfq_insert_request+0x77, which mapped to this:
>
> /usr/src/debug/kernel-2.6.32-135.el6/linux-2.6.32-135.el6.x86_64/block/cfq-iosched.c:1997
> ffffffff8125c390: 49 8b 84 24 a8 00 00 mov 0xa8(%r12),%rax
> ffffffff8125c397: 00 <---------------------
> ffffffff8125c398: 83 80 ec 02 00 00 01 addl $0x1,0x2ec(%rax)
>
> cfq-iosched.c:1997 looks like this:
>
> (RQ_CFQG(rq))->dispatched++;
>
> Enabling CONFIG_BLK_CGROUP made the problem go away. Again, not sure
> it's the same thing, but I figured I'd speak up in case it helps.
I think this is just the canary in this particular case, I bet it does
not work reliably in general after the addition of the SORT_MERGE
insert.
--
Jens Axboe
prev parent reply other threads:[~2011-04-21 15:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 12:58 2.6.39-rc4 BUG: unable to handle kernel NULL pointer dereference at 0000000c IP: cfq_insert_request+0x1d/0x3f5 Michal Hocko
2011-04-20 13:03 ` Jens Axboe
2011-04-20 13:13 ` Jens Axboe
2011-04-20 13:29 ` Michal Hocko
2011-04-20 13:31 ` Jens Axboe
2011-04-20 17:33 ` Jens Axboe
2011-04-21 7:16 ` Michal Hocko
2011-04-21 7:25 ` Jens Axboe
2011-04-21 14:38 ` Linus Torvalds
2011-04-21 15:29 ` Jens Axboe
2011-04-21 18:52 ` Michal Hocko
2011-04-21 18:51 ` Michal Hocko
2011-04-21 19:00 ` Jens Axboe
2011-04-22 7:00 ` Michal Hocko
2011-04-22 11:35 ` Jens Axboe
2011-04-22 20:30 ` Hugh Dickins
2011-04-21 15:04 ` Jeff Moyer
2011-04-21 15:27 ` Vivek Goyal
2011-04-21 15:51 ` Jeff Moyer
2011-04-21 15:30 ` 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=4DB04D8F.2000708@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=axboe@kernel.dk \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=torvalds@linux-foundation.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.