public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Sullivan <tsulliva@iex.net>
To: Brian Gerst <bgerst@didntduck.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: test12-pre3: paging problem
Date: Wed, 29 Nov 2000 09:37:22 -0700	[thread overview]
Message-ID: <3A2530C2.456BF661@iex.net> (raw)
In-Reply-To: <3A250F85.EF1FD067@iex.net> <3A252464.2AB55600@didntduck.org>

Brian Gerst wrote:
> 
> Tim Sullivan wrote:
> >
> > Hello,
> >
> > The following occurred during startup using test12-pre3. test12-pre2
> > does not exhibit the problem.
> >
> > regards,
> >
> > -tim
> >
> > kernel: Unable to handle kernel paging request at virtual address
> > fffffffc
> > kernel:  printing eip:
> > kernel: c011a41f
> > kernel: *pde = 00001063
> > kernel: *pte = 00000000
> > kernel: Oops: 0000
> > kernel: CPU:    0
> > kernel: EIP:    0010:[sys_setitimer+191/208]
> > kernel: EFLAGS: 00010246
> > kernel: eax: 00000000   ebx: cf4e1fb0   ecx: 00000000   edx: c027169d
> > kernel: esi: bffffc68   edi: cf4e1fc0   ebp: 00000000   esp: cf4e1f88
> > kernel: ds: 0018   es: 0018   ss: 0018
> > kernel: Process ntpdate (pid: 451, stackpage=cf4e1000)
> > kernel: Stack: cf4e0000 bffffd1c 00000009 bffffc70 00000000 cf4e0000
> > 400538e8 00000000
> > kernel:        00000000 40166214 00000000 00030d40 00000000 000186a0
> > c010a847 00000000
> > kernel:        bffffc58 00000000 bffffd1c 00000009 bffffc70 00000068
> > 0000002b 0000002b
> > kernel: Call Trace: [system_call+51/56]
> > kernel: Code: c8 5d 83 c4 28 c3 90 90 90 90 90 90 90 90 90 90 90 83 ec
> > 44
> 
> Disassemblind the code bytes, it shows up as:
>    0:   c8 5d 83 c4             enter  $0x835d,$0xc4
>    4:   28 c3                   subb   %al,%bl
>    6:   90                      nop
> which is definately wrong.  Moving one byte forward it becomes:
>    0:   5d                      popl   %ebp
>    1:   83 c4 28                addl   $0x28,%esp
>    4:   c3                      ret
>    5:   90                      nop
> which a normal sequence of instructions for the end of a function.  It
> looks like a branch may have been miscompiled off by one.  What
> compiler/binutils are you using?
> 
> --
> 
>                                 Brian Gerst


compiler = kgcc (RedHat 7)
	gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
binutils = 2.10.0.18

-tim
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2000-11-29 17:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-29 14:15 test12-pre3: paging problem Tim Sullivan
     [not found] ` <3A251361.CC904AC0@didntduck.org>
2000-11-29 15:26   ` Tim Sullivan
2000-11-29 15:44 ` Brian Gerst
2000-11-29 16:37   ` Tim Sullivan [this message]

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=3A2530C2.456BF661@iex.net \
    --to=tsulliva@iex.net \
    --cc=bgerst@didntduck.org \
    --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