public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sakellarios Gerakios <s.gerakios@digi-net.gr>
To: linux-kernel@vger.kernel.org
Subject: Oops: 0000
Date: Thu, 03 Feb 2005 11:50:57 +0200	[thread overview]
Message-ID: <4201F401.7080401@digi-net.gr> (raw)

Hello,

I am not sure if sending you this Oops message form my Kernel is 
politically correct but here you go....

If you can help, I would greatly appreciate it.

Thank you in advance,


Larry


Feb  2 14:37:45 geezer kernel: Unable to handle kernel NULL pointer 
dereference at virtual address 00000074
Feb  2 14:37:45 geezer kernel:  printing eip:
Feb  2 14:37:45 geezer kernel: c0143c53
Feb  2 14:37:45 geezer kernel: *pde = 00000000
Feb  2 14:37:45 geezer kernel: Oops: 0000
Feb  2 14:37:45 geezer kernel: parport_pc lp parport autofs e100 
iptable_nat ip_conntrack iptable_mangle ipt_REJECT iptable_filter i
p_tables keybdev mousedev hid input usb-uhci usbcore ext3
Feb  2 14:37:45 geezer kernel: CPU:    0
Feb  2 14:37:45 geezer kernel: EIP:    0060:[<c0143c53>]    Not tainted
Feb  2 14:37:45 geezer kernel: EFLAGS: 00010216
Feb  2 14:37:45 geezer kernel:
Feb  2 14:37:45 geezer kernel: EIP is at page_referenced [kernel] 0xe3 
(2.4.20-8)
Feb  2 14:37:45 geezer kernel: eax: c1057788   ebx: 00000818   ecx: 
00000000   edx: 0000aeeb
Feb  2 14:37:45 geezer kernel: esi: c030d24c   edi: c1125c24   ebp: 
00000003   esp: c1afff84
Feb  2 14:37:45 geezer kernel: ds: 0068   es: 0068   ss: 0068
Feb  2 14:37:45 geezer kernel: Process kscand/Normal (pid: 7, 
stackpage=c1aff000)
Feb  2 14:37:45 geezer kernel: Stack: c1afffa0 00000000 00000001 
c1afffb4 c11467f0 c11467f0 c030d24c c1125c24
Feb  2 14:37:45 geezer kernel:        00000003 c013c68e c1afe000 
c0125ba0 00000001 00000003 c1afe000 c030d100
Feb  2 14:37:45 geezer kernel:        c1afe000 c013d564 c030d100 
00000003 00000001 c025ef1b 000009c4 c013d4b0
Feb  2 14:37:45 geezer kernel: Call Trace:   [<c013c68e>] 
scan_active_list [kernel] 0x3e (0xc1afffa8))
Feb  2 14:37:45 geezer kernel: [<c0125ba0>] process_timeout [kernel] 0x0 
(0xc1afffb0))
Feb  2 14:37:45 geezer kernel: [<c013d564>] kscand [kernel] 0xb4 
(0xc1afffc8))
Feb  2 14:37:45 geezer kernel: [<c013d4b0>] kscand [kernel] 0x0 
(0xc1afffe0))
Feb  2 14:37:45 geezer kernel: [<c010742d>] kernel_thread_helper 
[kernel] 0x5 (0xc1affff0))
Feb  2 14:37:45 geezer kernel:
Feb  2 14:37:45 geezer kernel:
Feb  2 14:37:46 geezer kernel: Code: 8b 41 74 39 41 60 b8 01 00 00 00 0f 
43 44 24 04 89 44 24 04

             reply	other threads:[~2005-02-03  9:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-03  9:50 Sakellarios Gerakios [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-16 14:46 Oops 0000 Stephan Henningsen

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=4201F401.7080401@digi-net.gr \
    --to=s.gerakios@digi-net.gr \
    --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