mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: LKML <linux-kernel@vger.kernel.org>, Greg KH <greg@kroah.com>,
	Chuck Ebbert <76306.1226@compuserve.com>
Subject: Re: Oops in 2.6.19.1
Date: Wed, 27 Dec 2006 10:07:12 +0800	[thread overview]
Message-ID: <1167185232.15989.129.camel@ymzhang> (raw)
In-Reply-To: <200612231540.47176.s0348365@sms.ed.ac.uk>

On Sat, 2006-12-23 at 15:40 +0000, Alistair John Strachan wrote:
> On Wednesday 20 December 2006 14:21, Alistair John Strachan wrote:
> > Hi,
> >
> > Any ideas?
> 
> Pretty much like clockwork, it happened again. I think it's time to take this 
> seriously as a software bug, and not some hardware problem. I've ran kernels 
> since 2.6.0 on this machine without such crashes, and now two of the same in 
> 2.6.19.1? Pretty unlikely!
> 
> BUG: unable to handle kernel NULL pointer dereference at virtual address 
> 00000009
>  printing eip:
> c0156f60
> *pde = 00000000
> Oops: 0002 [#1]
> Modules linked in: ipt_recent ipt_REJECT xt_tcpudp ipt_MASQUERADE iptable_nat 
> xt_sta
> te iptable_filter ip_tables x_tables prism54 yenta_socket rsrc_nonstatic 
> pcmcia_core snd_via82xx snd_ac97_codec snd_ac97_bus
> snd_pcm snd_timer snd_page_alloc snd_mpu401_uart snd_rawmidi snd soundcore 
> usblp ehci_hcd eth1394 uhci_hcd usbcore ohci1394 i
> eee1394 via_agp agpgart vt1211 hwmon_vid hwmon ip_nat_ftp ip_nat 
> ip_conntrack_ftp ip_conntrack
> CPU:    0
> EIP:    0060:[<c0156f60>]    Not tainted VLI
> EFLAGS: 00010246   (2.6.19.1 #1)
> EIP is at pipe_poll+0xa0/0xb0
> eax: 00000008   ebx: 00000000   ecx: 00000008   edx: 00000000
> esi: ee1b9e9c   edi: f4d80a00   ebp: ee1b9c1c   esp: ee1b9c0c
> ds: 007b   es: 007b   ss: 0068
> Process java (pid: 5374, ti=ee1b8000 task=f7117560 task.ti=ee1b8000)
> Stack: 00000000 00000000 ee1b9e9c f6c17160 ee1b9fa4 c015d7f3 ee1b9c54 ee1b9fac
>        082dff90 00000010 082dffa0 00000000 ee1b9e94 ee1b9e94 00000002 ee1b9eac
>        00000000 ee1b9e94 c015e580 00000000 00000000 00000002 f6c17160 00000000
> Call Trace:
>  [<c015d7f3>] do_sys_poll+0x253/0x480
>  [<c015da53>] sys_poll+0x33/0x50
>  [<c0102c97>] syscall_call+0x7/0xb
>  [<b7f26402>] 0xb7f26402
>  =======================
> Code: 58 01 00 00 0f 4f c2 09 c1 89 c8 83 c8 08 85 db 0f 44 c8 8b 5d f4 89 c8 
> 8b 75
> f8 8b 7d fc 89 ec 5d c3 89 ca 8b 46 6c 83 ca 10 3b <87> 68 01 00 00 0f 45 ca 
> eb b6 8d b6 00 00 00 00 55 b8 01 00 00
Above codes look weird. Could you disassemble kernel image and post
the part around address 0xc0156f60?

"87 68 01 00 00" is instruction xchg, but if I disassemble from the begining,
I couldn't see instruct xchg.


> EIP: [<c0156f60>] pipe_poll+0xa0/0xb0 SS:ESP 0068:ee1b9c0c
> 

  reply	other threads:[~2006-12-27  2:07 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
2007-01-02 21:10                   ` kernel + gcc 4.1 = several problems Adrian Bunk
2007-01-02 21:56                     ` Alistair John Strachan
2007-01-02 22:06                       ` D. Hazelton
2007-01-02 23:24                         ` Adrian Bunk
2007-01-02 23:41                           ` D. Hazelton
2007-01-03  2:05                             ` Horst H. von Brand
2007-01-02 22:13                       ` Linus Torvalds
2007-01-02 23:18                         ` Alistair John Strachan
2007-01-03  1:43                           ` Linus Torvalds
2007-01-02 22:01                     ` Linus Torvalds
2007-01-02 23:09                       ` David Rientjes
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
2006-12-30 18:32   ` Alistair John Strachan
2006-12-21  8:05 Chuck Ebbert
2006-12-21 14:22 ` Alistair John Strachan
     [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-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
2006-12-31 21:43 Chuck Ebbert
2006-12-31 22:16 ` 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=1167185232.15989.129.camel@ymzhang \
    --to=yanmin_zhang@linux.intel.com \
    --cc=76306.1226@compuserve.com \
    --cc=greg@kroah.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

Powered by JetHome