public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: linux-kernel@vger.kernel.org
Subject: Re: unable to handle kernel paging request when inserting FAT32 formatted flash media
Date: Tue, 03 May 2011 09:41:11 +0900	[thread overview]
Message-ID: <8762psfwew.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <87bozkg3ng.fsf@devron.myhome.or.jp> (OGAWA Hirofumi's message of "Tue, 03 May 2011 07:04:51 +0900")

OGAWA Hirofumi <hirofumi@mail.parknet.co.jp> writes:

> Tino Keitel <tino.keitel@tikei.de> writes:
>
>>> > Yes, it is reproducible. It happens with a CF card from a Canon DSLR as
>>> > well as with a SD card from a little Fuji cam. Configs are attached.
>>> 
>>> .config didn't have interest part for now. Could you send another oops,
>>> and vfat.ko, fat.ko? I'd like to see more detail by assembler, current
>>> oops is unclear...
>>
>> Another Oops, this time with the SD card, and the modules are attached.
>>
>>> And if possible, git bisect is appreciate.
>>
>> Lack of spare time currently, sorry.
>
> OK. Thanks for your help.

It seems to be interesting exception.

before relocation (from fat.ko)
    8656:	74 51                	je     86a9 <fat_build_inode+0x2e9>
    8658:	49 c7 c6 00 00 00 00 	mov    $0x0,%r14
    865f:	b2 b6                	mov    $0xb6,%dl
    8661:	80 3d 00 00 00 00 00 	cmpb   $0x0,0x0(%rip) <-- exception
    8668:	74 3f                	je     86a9 <fat_build_inode+0x2e9>
    866a:	49 8d 44 24 08       	lea    0x8(%r12),%rax

after relocation (from oops)

  20:	74 51                	je     73 <a+0x73>
  22:	49 c7 c6 d8 91 13 a0 	mov    $0xffffffffa01391d8,%r14
  29:	b2 b6                	mov    $0xb6,%dl
  2b:	3d fc 9b 00 00       	cmp    $0x9bfc,%eax
  30:	00 74 3f 49          	add    %dh,0x49(%rdi,%rdi,1)
  34:	8d 44 24 08          	lea    0x8(%rsp),%eax

relocation info would be this
  0x0000000000006883  X86_64_32S      000000000000000000    +253 .rodata.str1.1

Although I'm not sure at all for now, I'm guessing something wrong
happened around relocation.

Thanks.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

  reply	other threads:[~2011-05-03  0:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-02  6:49 unable to handle kernel paging request when inserting FAT32 formatted flash media Tino Keitel
2011-05-02  6:55 ` Tino Keitel
2011-05-02 14:34   ` OGAWA Hirofumi
2011-05-02 15:12     ` OGAWA Hirofumi
2011-05-02 17:01       ` Tino Keitel
2011-05-02 18:46         ` OGAWA Hirofumi
2011-05-02 20:33           ` Tino Keitel
2011-05-02 20:34             ` Tino Keitel
2011-05-02 22:04             ` OGAWA Hirofumi
2011-05-03  0:41               ` OGAWA Hirofumi [this message]
2011-05-03  0:44                 ` OGAWA Hirofumi
2011-05-03 20:22                   ` Tino Keitel
2011-05-03 21:09                     ` OGAWA Hirofumi
2011-05-03  1:14                 ` OGAWA Hirofumi
2011-05-03  1:52                   ` OGAWA Hirofumi
2011-05-03  2:34                     ` OGAWA Hirofumi
2011-05-09  2:26                       ` Rusty Russell
2011-05-09  3:13                         ` OGAWA Hirofumi

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=8762psfwew.fsf@devron.myhome.or.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --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