From: Keith Owens <kaos@ocs.com.au>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Andrew Morton <akpm@osdl.org>, "Rafael J. Wysocki" <rjw@sisk.pl>,
Stephen Hemminger <shemminger@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-netdev <netdev@vger.kernel.org>
Subject: Re: 2.6.18-rc3-mm2 (+ hotfixes): GPF related to skge on suspend
Date: Mon, 14 Aug 2006 10:21:55 +1000 [thread overview]
Message-ID: <17002.1155514915@ocs10w.ocs.com.au> (raw)
In-Reply-To: Your message of "Sun, 13 Aug 2006 04:53:09 -0400." <200608130456_MC3-1-C7EE-44C8@compuserve.com>
Chuck Ebbert (on Sun, 13 Aug 2006 04:53:09 -0400) wrote:
>In-Reply-To: <20060812052853.f9e5d648.akpm@osdl.org>
>
>On Sat, 12 Aug 2006 05:28:53 -0700, Andrew Morton wrote:
>
>> > Code: 44 8b 28 c7 45 d0 00 00 00 00 45 85 ed 0f 89 29 fb ff ff e9
>>
>> ksymoops says:
>>
>> Code; ffffffff88107287 <_end+7ac9287/7efc2000>
>> 00000000 <_EIP>:
>> Code; ffffffff88107287 <_end+7ac9287/7efc2000> <=====
>> 0: 44 inc %esp <=====
>> Code; ffffffff88107288 <_end+7ac9288/7efc2000>
>> 1: 8b 28 mov (%eax),%ebp
>
>0x44 is a REX prefix in 64-bit mode, so somehow ksymoops got it
>wrong and gave you an i386-mode decode instead of 64-bit mode.
>Did you run it on a i386 machine and it assumed i386? Maybe you
>need to use "-a x86-64"? (I can't make it work on my setup.)
>
>So it's really "mov (%r8),%ebp" if I am reading the manual right.
ksymoops -VKLMO -t elf64-x86-64 -a i386:x86-64
ksymoops 2.4.11 on i686 2.6.16.21-0.13-smp. Options used
-V (specified)
-K (specified)
-L (specified)
-O (specified)
-M (specified)
-t elf64-x86-64 -a i386:x86-64
Warning (merge_maps): no symbols in merged map
Code: 44 8b 28 c7 45 d0 00 00 00 00 45 85 ed 0f 89 29 fb ff ff e9
Code; 0000000000000000 No symbols available
0000000000000000 <_RIP>:
Code; 0000000000000000 No symbols available
0: 44 8b 28 mov (%rax),%r13d
Code; 0000000000000003 No symbols available
3: c7 45 d0 00 00 00 00 movl $0x0,0xffffffffffffffd0(%rbp)
Code; 000000000000000a No symbols available
a: 45 85 ed test %r13d,%r13d
Code; 000000000000000d No symbols available
d: 0f 89 29 fb ff ff jns fffffffffffffb3c <_RIP+0xfffffffffffffb3c>
Code; 0000000000000013 No symbols available
13: e9 00 00 00 00 jmpq 18 <_RIP+0x18>
next prev parent reply other threads:[~2006-08-14 0:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-13 8:53 Chuck Ebbert
2006-08-13 17:38 ` Andrew Morton
2006-08-14 0:21 ` Keith Owens [this message]
2006-08-14 0:35 ` Andrew Morton
2006-08-14 0:54 ` Keith Owens
2006-08-14 1:06 ` Andrew Morton
2006-08-14 1:10 ` Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2006-08-12 10:07 Rafael J. Wysocki
2006-08-12 12:28 ` Andrew Morton
2006-08-12 13:39 ` Jeff Garzik
2006-08-12 14:32 ` Rafael J. Wysocki
2006-08-12 19:34 ` Rafael J. Wysocki
2006-08-12 14:31 ` Rafael J. Wysocki
2006-08-12 16:12 ` Edgar E. Iglesias
2006-08-12 17:13 ` Rafael J. Wysocki
2006-08-12 18:16 ` Edgar E. Iglesias
2006-08-12 19:32 ` Rafael J. Wysocki
2006-08-13 5:56 ` Stephen Hemminger
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=17002.1155514915@ocs10w.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=shemminger@osdl.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
all inboxes | Powered by JetHome®