From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: apw@shadowen.org, jens.axboe@oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.23-git18 Kernel oops in sg helpers
Date: Wed, 24 Oct 2007 21:38:30 +0530 [thread overview]
Message-ID: <471F6DFE.3040304@linux.vnet.ibm.com> (raw)
In-Reply-To: <20071024214014C.fujita.tomonori@lab.ntt.co.jp>
FUJITA Tomonori wrote:
> On Wed, 24 Oct 2007 12:54:36 +0100
> Andy Whitcroft <apw@shadowen.org> wrote:
>
>> On Tue, Oct 23, 2007 at 08:44:20PM +0200, Jens Axboe wrote:
>>> On Tue, Oct 23 2007, Kamalesh Babulal wrote:
>>>> Hi,
>>>>
>>>> Kernel oops is triggered while running fsx-linux test, followed by cpu softlock
>>>> over the AMD box
>>>>
>>>> Unable to handle kernel NULL pointer dereference at 0000000000000018 RIP:
>>>> [<ffffffff8021f2f6>] gart_map_sg+0x26c/0x406
>>>> PGD 10185b067 PUD 10075b067 PMD 0
>>>> Oops: 0002 [1] SMP
>>>> CPU 3
>>>> Modules linked in:
>>>> Pid: 18676, comm: fsx-linux Not tainted 2.6.23-git18-autokern1 #1
>>>> RIP: 0010:[<ffffffff8021f2f6>] [<ffffffff8021f2f6>] gart_map_sg+0x26c/0x406
>>>> RSP: 0000:ffff810181edf948 EFLAGS: 00010002
>>> Can you check where gart_map_sg+0x26c is at? Make sure you have
>>> CONFIG_DEBUG_INFO defined, then do:
>>>
>>> $ gdb vmlinux
>>> $ l *gart_map_sg+0x26c
>> Ok, this problem still seems to be about in 2.6.24-rc1. Here is the gdb
>> output from that version, the panic (also below) seems the same:
>>
>> (gdb) l *gart_map_sg+0x26c
>> 0xffffffff8022011e is in gart_map_sg (arch/x86/kernel/pci-gart_64.c:433).
>> 428 goto error;
>> 429 out++;
>> 430 flush_gart();
>> 431 if (out < nents) {
>> 432 sgmap = sg_next(sgmap);
>> 433 sgmap->dma_length = 0;
>> 434 }
>> 435 return out;
>> 436
>> 437 error:
>>
>> So it seems sg_next has returned 0.
>
> Have you tried this?
>
> http://marc.info/?l=linux-kernel&m=119317981406073&w=2
> -
Hi,
Thanks, this patch solves the kernel oops.
--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
next prev parent reply other threads:[~2007-10-24 16:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 15:19 [BUG] 2.6.23-git18 Kernel oops in sg helpers Kamalesh Babulal
2007-10-23 18:44 ` Jens Axboe
2007-10-24 11:54 ` Andy Whitcroft
2007-10-24 12:25 ` Jens Axboe
2007-10-24 12:40 ` FUJITA Tomonori
2007-10-24 16:08 ` Kamalesh Babulal [this message]
2007-10-24 18:06 ` Jens Axboe
2007-10-24 22:09 ` FUJITA Tomonori
2007-10-25 5:34 ` Jens Axboe
2007-10-23 22:42 ` FUJITA Tomonori
2007-10-24 8:32 ` Jens Axboe
2007-10-24 8:50 ` Benny Halevy
2007-10-25 8:53 ` Benny Halevy
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=471F6DFE.3040304@linux.vnet.ibm.com \
--to=kamalesh@linux.vnet.ibm.com \
--cc=apw@shadowen.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox