public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.co.uk>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Alistair John Strachan <s0348365@sms.ed.ac.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: Oops in 2.6.19.1
Date: Sat, 30 Dec 2006 18:06:29 +0000	[thread overview]
Message-ID: <4596AAA5.9020506@superbug.co.uk> (raw)
In-Reply-To: <200612201550_MC3-1-D5C7-74C6@compuserve.com>

Chuck Ebbert wrote:
> In-Reply-To: <200612201421.03514.s0348365@sms.ed.ac.uk>
> 
> On Wed, 20 Dec 2006 14:21:03 +0000, Alistair John Strachan wrote:
> 
>> Any ideas?
>>
>> BUG: unable to handle kernel NULL pointer dereference at virtual address 
>> 00000009
> 
>     83 ca 10                  or     $0x10,%edx
>     3b                        .byte 0x3b
>     87 68 01                  xchg   %ebp,0x1(%eax)   <=====
>     00 00                     add    %al,(%eax)
> 
> Somehow it is trying to execute code in the middle of an instruction.
> That almost never works, even when the resulting fragment is a legal
> opcode. :)
> 
> The real instruction is:
> 
>     3b 87 68 01 00 00 00        cmp    0x168(%edi),%eax
> 
> I'd guess you have some kind of hardware problem.  It could also be
> a kernel problem where the saved address was corrupted during an
> interrupt, but that's not likely.

This looks rather strange.
The times I have seen this sort of problem is:
1) when one bit of the kernel is corrupting another part of it.
2) Kernel modules compiled with different gcc than rest of kernel.
3) kernel headers do not match the kernel being used.

One way to start tracking this down would be to run it with the fewest 
amount of kernel modules loaded as one can, but still reproduce the problem.

James

  parent reply	other threads:[~2006-12-30 18:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20 20:48 Oops in 2.6.19.1 Chuck Ebbert
2006-12-20 22:15 ` Alistair John Strachan
2006-12-21 15:31   ` Valdis.Kletnieks
2006-12-30 18:06 ` James Courtier-Dutton [this message]
2006-12-30 18:32   ` Alistair John Strachan
  -- strict thread matches above, loose matches on Subject: below --
2006-12-31 21:43 Chuck Ebbert
2006-12-31 22:16 ` Alistair John Strachan
2006-12-30 17:21 Chuck Ebbert
2006-12-30 18:29 ` Alistair John Strachan
2006-12-31 16:28   ` Adrian Bunk
2006-12-31 16:48     ` Alistair John Strachan
2007-01-02 21:12       ` Adrian Bunk
     [not found] <200612232325_MC3-1-D634-10E4@compuserve.com>
2006-12-24 14:40 ` Alistair John Strachan
2006-12-24 14:51 ` Alistair John Strachan
2006-12-21  8:05 Chuck Ebbert
2006-12-21 14:22 ` Alistair John Strachan
2006-12-20 14:21 Alistair John Strachan
2006-12-20 16:30 ` Greg KH
2006-12-20 16:44   ` Alistair John Strachan
2006-12-23 15:40 ` Alistair John Strachan
2006-12-27  2:07   ` Zhang, Yanmin
2006-12-27 12:35     ` Alistair John Strachan
2006-12-28  2:41       ` Zhang, Yanmin
2006-12-28  4:02         ` Alistair John Strachan
2006-12-28  4:14           ` Alistair John Strachan
2006-12-30 16:59             ` Alistair John Strachan
2006-12-31 13:47               ` Alistair John Strachan
2006-12-31 16:27               ` Adrian Bunk
2006-12-31 16:55                 ` Alistair John Strachan

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=4596AAA5.9020506@superbug.co.uk \
    --to=james@superbug.co.uk \
    --cc=76306.1226@compuserve.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s0348365@sms.ed.ac.uk \
    /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