From: "Lina Lu" <lulina_nuaa@foxmail.com>
To: "Vivek Goyal" <vgoyal@redhat.com>
Cc: "linux kernel mailing list" <linux-kernel@vger.kernel.org>
Subject: Re: Re: Re: cfq-iosched.c: panic in cfq_dispatch_requests
Date: Tue, 22 Mar 2011 23:48:16 +0800 [thread overview]
Message-ID: <201103222348152343383@foxmail.com> (raw)
In-Reply-To: <201103222332465003523@foxmail.com>
On 2011-03-22 23:39:48, Vivek Goyal wrote:
>On Tue, Mar 22, 2011 at 11:32:47PM +0800, Lina Lu wrote:
>> On 2011-03-21 22:08:19, Vivek Goyal wrote:
>> >On Sun, Mar 20, 2011 at 03:23:23PM +0800, Lina Lu wrote:
>> >> Hi Vivek,
>> >>
>> >> I did some test with blkio weight policy these days. The kernel panic
>> >> once in a while.
>> >>
>> >> From the calltrace, It 's in func cfq_dispatch_requests(+0x058D).
>> >> And I caught a divide by zero error with system monitor tools.
>> >
>> >Hi Lina,
>> >
>> >Can you please paste the full backtrace here.
>> >
>> >>
>> >> The panic happens when I first set 100 weight to two IO pids, then
>> >> change the weight to 200, and begin to perform IO. The kernel panic
>> >> accurately when the IO begin.
>> >
>> >So you notice this only if weights are changed otherwise not?
>>
>> Hi Vivek
>>
>> Thanks for this patch! I did objdump and find place that divide by zero.
>> It's in cfq_group_slice function, the st->total_weight is zero in my issue.
>> As described in the patch, this is because I change the weight when the
>> group on service tree.
>
>Ok, so this patch did solve the issue you are facing?
>
Yes, this patch did solve the issue.
And I will do more test these days, if there is any other problem, I will keep
you know.
Thanks
Lina
prev parent reply other threads:[~2011-03-22 15:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 7:23 Lina Lu
2011-03-21 14:07 ` Vivek Goyal
2011-03-22 15:32 ` Lina Lu
2011-03-22 15:39 ` Vivek Goyal
2011-03-22 15:48 ` Lina Lu [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=201103222348152343383@foxmail.com \
--to=lulina_nuaa@foxmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome