Visit Jeremy's Blog.
Go Back > Forums > Linux Forums > Linux - General
User Name
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.


  Search this Thread
Old 08-05-2005, 02:35 PM   #1
LQ Newbie
Registered: Jan 2005
Posts: 4

Rep: Reputation: 0
Kernel Oops 2.6.11 --What does it mean???

What does this mean?

The machine went ok for another 2 days after this, but finally the program (intelisec_server) stopped responding. Otherwise seemed OK.

Any hint would help.


Aug 3 15:06:53 kernel: Unable to handle kernel paging request at virtual address 80808084
Aug 3 15:06:53 kernel: printing eip:
Aug 3 15:06:53 kernel: c012df43
Aug 3 15:06:53 kernel: *pde = 00000000
Aug 3 15:06:53 kernel: Oops: 0002 [#1]
Aug 3 15:06:53 kernel: PREEMPT
Aug 3 15:06:53 kernel: Modules linked in: bttv video_buf firmware_class v4l2_common btcx_risc tveeprom videodev
Aug 3 15:06:53 kernel: CPU: 0
Aug 3 15:06:53 kernel: EIP: 0060:[find_lock_page+37/234] Not tainted VLI
Aug 3 15:06:53 kernel: EFLAGS: 00010082 (
Aug 3 15:06:53 kernel: EIP is at find_lock_page+0x25/0xea
Aug 3 15:06:53 kernel: eax: 80808080 ebx: 80808080 ecx: 00000000 edx: c49bb8d4
Aug 3 15:06:53 kernel: esi: 00004600 edi: cda04180 ebp: cda0417c esp: c0771d4c
Aug 3 15:06:53 kernel: ds: 007b es: 007b ss: 0068
Aug 3 15:06:53 kernel: Process intelisec_serve (pid: 21914, threadinfo=c0770000 task=c6f54020)
Aug 3 15:06:53 kernel: Stack: b5d5a000 00004600 cda0417c 00000805 c012ff79 00001000 c031e614 00000018
Aug 3 15:06:53 kernel: c0771d8c c0771d94 cfd8f680 c0771d8c 00000000 b5d597fb 00000805 000007fb
Aug 3 15:06:53 kernel: cda040dc c0381b20 cc892980 00000001 c0771efc 00000000 00000000 c0771ebc
Aug 3 15:06:53 kernel: Call Trace:
Aug 3 15:06:53 kernel: [generic_file_buffered_write+229/1607] generic_file_buffered_write+0xe5/0x647
Aug 3 15:06:53 kernel: [fn_hash_lookup+134/208] fn_hash_lookup+0x86/0xd0
Aug 3 15:06:53 kernel: [current_fs_time+68/78] current_fs_time+0x44/0x4e
Aug 3 15:06:53 kernel: [inode_update_time+75/167] inode_update_time+0x4b/0xa7
Aug 3 15:06:53 kernel: [__generic_file_aio_write_nolock+714/1331] __generic_file_aio_write_nolock+0x2ca/0x533
Aug 3 15:06:53 kernel: [timer_interrupt+130/267] timer_interrupt+0x82/0x10b
Aug 3 15:06:53 kernel: [__do_softirq+58/129] __do_softirq+0x3a/0x81
Aug 3 15:06:53 kernel: [generic_file_aio_write+107/237] generic_file_aio_write+0x6b/0xed
Aug 3 15:06:53 kernel: [ext3_file_write+48/178] ext3_file_write+0x30/0xb2
Aug 3 15:06:53 kernel: [do_sync_write+185/262] do_sync_write+0xb9/0x106
Aug 3 15:06:53 kernel: [autoremove_wake_function+0/67] autoremove_wake_function+0x0/0x43
Aug 3 15:06:53 kernel: [sys_fstat64+35/40] sys_fstat64+0x23/0x28
Aug 3 15:06:53 kernel: [vfs_write+294/299] vfs_write+0x126/0x12b
Aug 3 15:06:53 kernel: [sys_write+65/106] sys_write+0x41/0x6a
Aug 3 15:06:53 kernel: [sysenter_past_esp+82/117] sysenter_past_esp+0x52/0x75
Aug 3 15:06:53 kernel: Code: 00 89 d8 5b 5e c3 55 89 c5 57 56 89 d6 53 fa b8 01 00 00 00 e8 62 05 fe ff 8d 7d 04 89 f2 89 f8 e8 d3 bb 09 00 85 c0 89 c3 74 7c <ff> 40 04 0f ba 28 00 19 c0 85 c0 74 6f fb b8 01 00 00 00 e8 6a
Aug 3 15:06:53 kernel: <6>note: intelisec_serve[21914] exited with preempt_count 1
Old 08-05-2005, 02:45 PM   #2
LQ Guru
Registered: Feb 2004
Location: SE Tennessee, USA
Distribution: Gentoo, LFS
Posts: 6,107

Rep: Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520Reputation: 1520
A "kernel oops" is a non-fatal error within the kernel. (A "kernel panic" is, of course, fatal.) The problem occurred in kernel-space, not user-space, so it strongly implies that there is a problem in some kernel module. Some kind of physical I/O error condition, in this case, also cannot be excluded.

A study of the kernel map for the address c012df43 should point out the offending module. We know from the dump that the intelisec_serve process was running, and that it was doing a file-write. The traceback, read from the bottom up, shows the list of active calls at the time the failure occurred.

Since it is very unlikely that you are the first intelisec user to have encountered this problem, a search of Google and of the vendor's site would be a good first step.

The relevant source-code seems to be in arch/i386/fault.c where we are told that "the kernel tried to access some bad page. We'll have to terminate things with extreme prejudice." A few steps backward in the traceback should help to see why.

Last edited by sundialsvcs; 08-05-2005 at 02:51 PM.
Old 08-05-2005, 08:22 PM   #3
LQ Newbie
Registered: Jan 2005
Posts: 4

Original Poster
Rep: Reputation: 0
Thanks for the quick reply.

Kernel map shows that address c012df43 is in function find_lock_page.

The application running is my own program. It uses threads to write into files. One file one thread. It also uses the v4l2 driver to grab images. Never have a problem with it before I started using a P4 CPU on an Intel motherboard. I have two identical machines, both are troubled.

This is the first time it had this problem, usually the program crashes or stops responding, but only on this full Intel platform.

Could it be a sign of system bus overload, irq or dma problems?

Old 08-05-2005, 10:06 PM   #4
Senior Member
Registered: May 2004
Location: In the DC 'burbs
Distribution: Arch, Scientific Linux, Debian, Ubuntu
Posts: 4,265

Rep: Reputation: 369Reputation: 369Reputation: 369Reputation: 369
It could be a subtle driver issue that only shows up on this particular system. Can you check with the author of the driver to see if perhaps this isn't a known problem. In general, nothing from user space should be able to bother the kernel unless something in the kernel itself isn't behaing quite correctly. Is this accessing a device such as a camera connecting to a USB port via this driver? Perhaps the driver has some sort of race condition, given that you are using threads, but it's hard to say without knowing a bit more about your application.
Old 08-06-2005, 05:38 AM   #5
LQ Newbie
Registered: Jan 2005
Posts: 4

Original Poster
Rep: Reputation: 0
I use 4 PCI analog frame grabbers to grab images. There are 2 IDE drives to store the images. There are no graphics card, cd, floppy or any other device connected. I use ext3 filesystem.

The machine mainly runs ok, but time to time scrambles the filesystem, depending on load, crashes the application, or hangs the applications network connection. It happens about once a day. The operating system seems runs fine. There are no users, or other applications running, no X, hardly any process beside the main application.

Usually there is nothing in the kernel log. Ocasonally - about 2 a week - the bttv module logs some errors. I have spent a month on tracking down the source of instability. This is the first time I see the Oops inthe kernel log and wondering, that my problems are comming not from my application, but some hardware problem, however I have 2 idetical machines behaving very similarly. They are Intel 915 motherboards with P4 cpu and 256 RAM. I also tested the RAM.

I guess the kernel Oops does not bring me closer to the solution. It only tells me that there is a problem which propably not originates from my code, but could be caused by conflicts between kernel modules, or a hardware problem.


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 On
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Kernel OOPS morphs into BUG? Charred Slackware 1 08-28-2005 04:21 AM
Kernel 2.6.8-> Oops on NFS EyesOnly Linux - Software 2 08-15-2004 06:35 AM
what file are kernel oops stored in? abefroman Linux - General 0 03-22-2004 04:26 PM
Horrible Kernel Oops Thetargos Linux - General 2 08-13-2003 01:47 AM
Kernel oops on boot imbert Linux - Software 1 03-10-2003 02:16 PM

All times are GMT -5. The time now is 04:07 PM.

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