mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "WebLab Help" <help@wecltd.eu>
To: linux-kernel@vger.kernel.org
Cc: help@wecltd.eu
Subject: Oops in kernel 2.6.22 rc3
Date: Sun,  8 Jul 2007 12:43:41 +0200	[thread overview]
Message-ID: <aohr4divd.15j5uve@arsen.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 715 bytes --]

Hello,

I hope you can help me with the following problem.
One of my systems got some bigger problems, it stops and/or reboots every few days.
Today I was able to make a screenshot of the kernel oops, it's attached to this email. Because I made it via a digital photography and typing it in again it's possible that there are typos in it but I hope everything is fine.
Remarks: It's a new system - I'm unsure if possibly unreliable hardware also can cause Oopses or if Ooopses everytime are caused by errors in the kernel itself. If it's caused by the hardware - is there a chance to get a hint by the oops pointing to the components causing the errors?

Thank you very much in advance!

Best regards
Stefan Helbing

[-- Attachment #2: kernel-oops.txt --]
[-- Type: text/plain, Size: 1515 bytes --]

BUG: unable to handle kernel NULL pointer dereference at virtual address 00000000
 printing eip:
00000000
*pdpt = 000000001966d001
*pde = 0000000000000000
Oops: 0010 [#1]
SMP
Modules linked in: nfsd exportfs softdog ipt_REJECT ipt_LOG xt_state xt_limit xt_tpcudp iptable_filter nf_conntrack_ftp nf_conntrack_ipv4 nf_conntrack ip_tables x_tables core_temp it87 hwmon_vid hwmon i2c_isa nfs lockd sunrpc 3c59x i2c_i801 unix
CPU:    0
EIP:    0060:[<00000000>]    Not tainted VLI
EFLAGS: 00010206   (2.6.22-rc3-i386 #1)
EIP is at run_init_process+0x3fefff50/0x20
eax: f3601344   ebx: 00000000   ecx: c13207c0   edx: f3601344
esi: c3616720   edi: 00000009   ebp: c042c710   esp: d907df60
ds: 007b   es: 007b   fs: 00d8  gs: 0000  ss: 0068
Process mv (pid: 28651, ti=d907c000 task=d9981030 task.ti=d907c000)
Stack: c01288dc c361679c 00000000 c0429040 c0128ae7 c011dee8 00000001 c03ecce8
       c042c760 c0429040 c011dc64 00000000 00000007 00000046 00000812 00000003
       00012000 c011dc68 00000000 c010c0da b7faa000 c01039c8 b7faa000 00002000
Call Trace:
 [<c01288dc>] rcu_do_batch+0x1c/0x90
 [<c0128ea7>] rcu_process_callbacks+0x17/0x30
 [<c011dee8>] tasklet_action+0x58/0xa0
 [<c011dc64>] __do_softirq+0xc4/0xe0
 [<c011dcb8>] do_softirq+0x38/0x40
 [<c010c0da>] smp_apic_timer_interrupt+0x2a/0x40
 [<c01039c8>] apic_timer_interrupt+0x28/0x30
 =======================
Code:  Bad EIP value.
EIP: [<00000000>] run_init_process+0x3fefff50/0x20 SS:ESP 0068:d907df60
Kernel panic - not syncing: Fatal exception in interrupt

             reply	other threads:[~2007-07-08 11:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-08 10:43 WebLab Help [this message]
2007-07-08 11:26 ` Michal Piotrowski

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=aohr4divd.15j5uve@arsen.de \
    --to=help@wecltd.eu \
    --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

all inboxes | Powered by JetHome®