From: Chuck Ebbert <76306.1226@compuserve.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: "s.a." <sancelot@free.fr>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: kernel module debugging question
Date: Fri, 30 Jun 2006 14:48:59 -0400 [thread overview]
Message-ID: <200606301451_MC3-1-C3E0-AB89@compuserve.com> (raw)
In-Reply-To: <1151661642.11434.23.camel@laptopd505.fenrus.org>
On Fri, 30 Jun 2006 12:00:42 +0200, Arjan van de Ven wrote:
> On Fri, 2006-06-30 at 12:28 +0000, s.a. wrote:
> > Hi,
> > I have got the following fault , can you provide me with more details
> > about the problem ?
> > Best Regards
>
> you disabled CONFIG_KALLSYMS in your kernel configuration, which means
> the backtrace isn't really useful for anyone to look at
The only thing on the stack is the regs, thus no backtrace.
Someone modified entry.S and added code just before the sysexit. There is
no 'sysenter_exit' in stock 2.6.16 for one, and there's new code before
the sysexit:
3: e8 81 ca 03 00 call 3ca89 <_EIP+0x3ca89> <== new
8: fb sti <== new
9: 8b 4d 08 mov 0x8(%ebp),%ecx
c: 66 f7 c1 ff fe test $0xfeff,%cx
11: 0f 85 4e 01 00 00 jne 165 <_EIP+0x165>
17: e8 ed ea 00 00 call eb09 <_EIP+0xeb09> <== new
1c: 8b 44 24 18 mov 0x18(%esp),%eax <== new
20: 8b 54 24 28 mov 0x28(%esp),%edx
24: 8b 4c 24 34 mov 0x34(%esp),%ecx
28: 31 ed xor %ebp,%ebp
2a: fb sti
0: 0f 35 sysexit <===== oops
But that doesn't explain the oops. Maybe the SYSENTER MSR got screwed up?
--
Chuck
"You can't read a newspaper if you can't read." --George W. Bush
next reply other threads:[~2006-06-30 18:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 18:48 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-30 12:28 kernel module debugging question s.a.
2006-06-30 10:00 ` Arjan van de Ven
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=200606301451_MC3-1-C3E0-AB89@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sancelot@free.fr \
/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.