From: Randy Dunlap <randy.dunlap@oracle.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>, Andi Kleen <ak@suse.de>
Subject: Re: crashme fault
Date: Sat, 15 Sep 2007 11:40:02 -0700 [thread overview]
Message-ID: <46EC2702.3090000@oracle.com> (raw)
In-Reply-To: <20070915183412.GA14501@one.firstfloor.org>
Andi Kleen wrote:
>> Andi, anything comes to mind?
>
> No, unfortunately not. There weren't any changes to entry.S recently
> that could corrupt the error code as far as I remember. Also cannot think of
> something else.
>
> A version where it started happening would be useful.
I'll begin testing older kernels then.
Had another on recent last night (probably not helpful):
[58169.607164] Unable to handle kernel paging request at 00000000ff018915 RIP:
[58169.611784] [<0000000000506986>]
[58169.617570] PGD d4380067 PUD 0
[58169.620757] Oops: 0000 [1] SMP
[58169.623943] CPU 2
[58169.625970] Modules linked in: loop
[58169.629496] Pid: 26735, comm: crashme Not tainted 2.6.23-rc6-git4 #1
[58169.635842] RIP: 0033:[<0000000000506986>] [<0000000000506986>]
[58169.641861] RSP: 002b:00007fff14d3f9a0 EFLAGS: 00010247
[58169.647171] RAX: 0000000000506909 RBX: 00002b8695e82c00 RCX: 00002b8695f15b37
[58169.654298] RDX: 0000000000000000 RSI: 0000000000401476 RDI: 000000000000000a
[58169.661426] RBP: 00007fff14d3f9a0 R08: 00007fff14d3f8f0 R09: 0000000000000000
[58169.668553] R10: 0000000000000008 R11: 0000000000000212 R12: 0000000000000000
[58169.675680] R13: 00007fff14d3fb90 R14: 0000000000000000 R15: 0000000000000000
[58169.682808] FS: 00002b86960b46d0(0000) GS:ffff81011fc75840(0000) knlGS:0000000000000000
[58169.690889] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[58169.696630] CR2: 00000000ff018915 CR3: 00000000d8820000 CR4: 00000000000006e0
[58169.703757] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[58169.710885] DR3: 0000000000000000 DR6: 00000000ffff4ff0 DR7: 0000000000000400
[58169.718014] Process crashme (pid: 26735, threadinfo ffff8100cd176000, task ffff81011fffe040)
[58169.726439]
[58169.727937] RIP [<0000000000506986>]
[58169.731609] RSP <00007fff14d3f9a0>
[58169.735100] CR2: 00000000ff018915
[58169.738710] Kernel panic - not syncing: Fatal exception
[58169.743953] Rebooting in 30 seconds..
next prev parent reply other threads:[~2007-09-15 18:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 5:21 crashme fault Randy Dunlap
2007-09-15 4:28 ` Linus Torvalds
2007-09-15 5:05 ` Randy Dunlap
2007-09-15 5:21 ` Randy Dunlap
2007-09-15 18:34 ` Andi Kleen
2007-09-15 18:40 ` Randy Dunlap [this message]
2007-09-15 19:44 ` Linus Torvalds
2007-09-15 19:53 ` Randy Dunlap
2007-09-15 22:15 ` Linus Torvalds
2007-09-15 22:47 ` Linus Torvalds
2007-09-15 23:47 ` Randy Dunlap
2007-09-16 0:34 ` Linus Torvalds
2007-09-16 16:40 ` Randy Dunlap
2007-09-16 17:14 ` Linus Torvalds
2007-09-16 18:12 ` Linus Torvalds
2007-09-17 5:06 ` Randy Dunlap
2007-09-17 5:28 ` Linus Torvalds
2007-09-17 14:29 ` Randy Dunlap
2007-09-17 14:53 ` Linus Torvalds
2007-09-17 20:05 ` Randy Dunlap
2007-09-16 18:28 ` Andi Kleen
2007-09-16 3:10 ` Andi Kleen
2007-09-16 15:53 ` Andrea Arcangeli
2007-09-16 16:17 ` Randy Dunlap
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=46EC2702.3090000@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=ak@suse.de \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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