LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 12-18-2003, 09:51 AM   #1
kadaver
Member
 
Registered: Nov 2003
Location: Beautiful Northern-sweden (Luleň)
Posts: 90

Rep: Reputation: 15
Unable to handle kernel NULL pointer dereference....


This is one of those threads pertaining to errors-that-doesn't-affect-the-system-at-all.
Browsing through my syslog a couple of minutes ago I found this error: (I stripped the date and hostname entries)

*****
Unable to handle kernel NULL pointer dereference at virtual address 00000008
printing eip:
c01858fb
*pde = 00000000
Oops: 0000 [#1]
CPU: 0
EIP: 0060:[<c01858fb>] Not tainted
EFLAGS: 00010296
EIP is at create_dir+0x1b/0xc0
eax: df819f48 ebx: e197a150 ecx: 00000000 edx: e197a154
esi: e197a150 edi: 00000000 ebp: df819f48 esp: df819f18
ds: 007b es: 007b ss: 0068
Process modprobe (pid: 92, threadinfo=df818000 task=df83ecc0)
Stack: e197a0b4 e197a0b4 00000246 e197a150 e197a150 e197a150 e197a0b4 c0185a10
e197a150 00000000 e197a154 df819f48 00000000 00000000 c01fa9ff e197a150
e197a0a0 e197a0a4 c01fae98 e197a150 c01fb2b6 e197a150 e197a0a0 e197a0a4
Call Trace:
[<c0185a10>] sysfs_create_dir+0x40/0x80
[<c01fa9ff>] create_dir+0x1f/0x50
[<c01fae98>] kobject_add+0x48/0x120
[<c01fb2b6>] kset_init+0x16/0x30
[<c024893c>] bus_register+0x5c/0xa0
[<e197c032>] usb_init+0x32/0x80 [usbcore]
[<c0131fc7>] sys_init_module+0x157/0x240
[<c01093e7>] syscall_call+0x7/0xb
Code: 8b 77 08 c7 04 24 a2 7d 32 c0 c7 44 24 04 77 00 00 00 e8 8e
*****
And then this: (Again stripped from date and hostname)
*****
kobject_register failed for ohci_hcd (-17)
Call Trace:
[<c01fafc2>] kobject_register+0x52/0x60
[<c02486da>] bus_add_driver+0x4a/0xc0
[<c0248bdf>] driver_register+0x2f/0x40
[<c020294c>] pci_register_driver+0x5c/0x90
[<e1aca063>] ohci_hcd_pci_init+0x63/0x89 [ohci_hcd]
[<c0131fc7>] sys_init_module+0x157/0x240
[<c01093e7>] syscall_call+0x7/0xb

Debug: sleeping function called from invalid context at mm/slab.c:1856
in_atomic():1, irqs_disabled():0
Call Trace:
[<c0118f4b>] __might_sleep+0xab/0xd0
[<c013bfdc>] kmem_cache_alloc+0x6c/0x70
[<c014ae24>] __get_vm_area+0x24/0x100
[<c014af32>] get_vm_area+0x32/0x40
[<c0116280>] __ioremap+0xc0/0x120
[<c011630b>] ioremap_nocache+0x2b/0xc0
[<e1dcea77>] os_map_kernel_space+0x47/0x80 [nvidia]
[<e1ca3377>] __nvsym00568+0x1f/0x2c [nvidia]
[<e1ca5496>] __nvsym00775+0x6e/0xe0 [nvidia]
[<e1ca5526>] __nvsym00781+0x1e/0x190 [nvidia]
[<e1ca6fac>] rm_init_adapter+0xc/0x10 [nvidia]
[<e1dcb414>] nv_kern_open+0x124/0x240 [nvidia]
[<c0159fa0>] exact_match+0x0/0x10
[<e1dcb2f0>] nv_kern_open+0x0/0x240 [nvidia]
[<c0159dbe>] chrdev_open+0xbe/0x1d0
[<c0159d00>] chrdev_open+0x0/0x1d0
[<c014fbb4>] dentry_open+0x114/0x180
[<c014fa98>] filp_open+0x68/0x70
[<c014fe9b>] sys_open+0x5b/0x90
[<c01093e7>] syscall_call+0x7/0xb

Debug: sleeping function called from invalid context at mm/slab.c:1856
in_atomic():1, irqs_disabled():0
Call Trace:
[<c0118f4b>] __might_sleep+0xab/0xd0
[<c013bfdc>] kmem_cache_alloc+0x6c/0x70
[<c014ae24>] __get_vm_area+0x24/0x100
[<c014af32>] get_vm_area+0x32/0x40
[<c0116280>] __ioremap+0xc0/0x120
[<c011630b>] ioremap_nocache+0x2b/0xc0
[<e1dcea77>] os_map_kernel_space+0x47/0x80 [nvidia]
[<e1ca3377>] __nvsym00568+0x1f/0x2c [nvidia]
[<e1ca5496>] __nvsym00775+0x6e/0xe0 [nvidia]
[<e1ca5526>] __nvsym00781+0x1e/0x190 [nvidia]
[<e1ca6fac>] rm_init_adapter+0xc/0x10 [nvidia]
[<e1dcb414>] nv_kern_open+0x124/0x240 [nvidia]
[<e1dcb2f0>] nv_kern_open+0x0/0x240 [nvidia]
[<c0159dbe>] chrdev_open+0xbe/0x1d0
[<c0159d00>] chrdev_open+0x0/0x1d0
[<c014fbb4>] dentry_open+0x114/0x180
[<c014fa98>] filp_open+0x68/0x70
[<c014fe9b>] sys_open+0x5b/0x90
[<c01093e7>] syscall_call+0x7/0xb
*****
This doesn't seem to affect my system at all.
Since I have no idea of what this means I was hoping that someone could explain it to me and maybe point me in the right direction to solve it.
I'm running Linux 2.6.0-test11 on Slack 9.1.
 
Old 12-18-2003, 07:14 PM   #2
jharris
Senior Member
 
Registered: May 2001
Location: Bristol, UK
Distribution: Slackware, Fedora, RHES
Posts: 2,243

Rep: Reputation: 46
I've got no suggestion for what the cause of the problem is but now that 2.6.0 proper is out give the a go and see if it still happens.

cheers

Jamie...
 
Old 12-19-2003, 08:46 AM   #3
kadaver
Member
 
Registered: Nov 2003
Location: Beautiful Northern-sweden (Luleň)
Posts: 90

Original Poster
Rep: Reputation: 15
I upgraded to stable and I still get the same message...
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Oops: Unable to handle kernel NULL pointer dereference at virtual address with mysqld GoranTornqvist Fedora 2 12-09-2004 12:30 PM
Oops: Unable to handle kernel NULL pointer dereference at virtual address GoranTornqvist Linux - General 1 12-09-2004 11:58 AM
NIC, unable to handle kernel NULL pointer dereference blo1005 Linux - Networking 1 06-30-2004 04:23 AM
Unable to handle kernel NULL pointer dereference at virtual ...? severedhead Linux - Software 0 07-12-2002 05:46 PM
Kernel Message:unable to handle kernel NULL pointer dereference at virtual address... dave_d Linux - General 0 02-14-2001 06:01 PM


All times are GMT -5. The time now is 03:55 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration