Skip to contentSkip to conversation

Kernel OOPS

DISCUSSION tmp 2 participants 3 messages May 16, 2004 – May 17, 2004

lore
Share & tools
lore

tmp

author
#0 lore raw

I get the attached oops message in syslog on my 2.6.6 kernel. I have also attached the ksymoops output.

When the oops has occured, I cannot open any shell (including a login shell).

May 16 13:29:34 debian kernel: Unable to handle kernel paging request at virtual address 1841b518
May 16 13:29:34 debian kernel:  printing eip:
May 16 13:29:34 debian kernel: c016c02e
May 16 13:29:34 debian kernel: *pde = 00000000
May 16 13:29:34 debian kernel: Oops: 0000 [#1]
May 16 13:29:34 debian kernel: CPU:    0
May 16 13:29:34 debian kernel: EIP:    0060:[proc_get_inode+110/272]    Not tainted
May 16 13:29:34 debian kernel: EFLAGS: 00010202   (2.6.6) 
May 16 13:29:34 debian kernel: EIP is at proc_get_inode+0x6e/0x110
May 16 13:29:34 debian kernel: eax: 00000000   ebx: df107850   ecx: 0114df68   edx: 36013bf9
May 16 13:29:34 debian kernel: esi: dffec810   edi: dffdee00   ebp: 00000007   esp: d5037e30
May 16 13:29:34 debian kernel: ds: 007b   es: 007b   ss: 0068
May 16 13:29:35 debian kernel: Process emacs (pid: 743, threadinfo=d5036000 task=d3ec8030)
May 16 13:29:35 debian kernel: Stack: df107850 f0000000 df7f19c0 e0820ead dffec810 c5bef353 dffec863 c016e8e3 
May 16 13:29:35 debian kernel:        dffdee00 f0000000 dffec810 ffffffea 00000000 dffdddd0 d5037f70 c5bef2d0 
May 16 13:29:35 debian kernel:        c5bef2d0 c016c1d1 dffdddd0 c5bef2d0 d5037f70 fffffff4 dffdde38 dffdddd0 
May 16 13:29:35 debian kernel: Call Trace:
May 16 13:29:35 debian kernel:  [pg0+541367981/1069707264] unix_stream_sendmsg+0x24d/0x3a0 [unix]
May 16 13:29:35 debian kernel:  [proc_lookup+179/192] proc_lookup+0xb3/0xc0
May 16 13:29:35 debian kernel:  [proc_root_lookup+49/128] proc_root_lookup+0x31/0x80
May 16 13:29:35 debian kernel:  [real_lookup+203/240] real_lookup+0xcb/0xf0
May 16 13:29:35 debian kernel:  [do_lookup+150/176] do_lookup+0x96/0xb0
May 16 13:29:35 debian kernel:  [link_path_walk+1052/2048] link_path_walk+0x41c/0x800
May 16 13:29:35 debian kernel:  [path_lookup+105/272] path_lookup+0x69/0x110
May 16 13:29:35 debian kernel:  [open_namei+131/1024] open_namei+0x83/0x400
May 16 13:29:35 debian kernel:  [__pollwait+0/208] __pollwait+0x0/0xd0
May 16 13:29:35 debian kernel:  [filp_open+62/112] filp_open+0x3e/0x70
May 16 13:29:35 debian kernel:  [sys_open+91/144] sys_open+0x5b/0x90
May 16 13:29:35 debian kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
May 16 13:29:35 debian kernel: 
May 16 13:29:35 debian kernel: Code: 8b 46 18 c7 43 38 00 00 00 00 89 43 34 0f b7 46 0e 66 85 c0 

ksymoops 2.4.9 on i686 2.6.6. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.6.6/ (default)
-m /boot/System.map-2.6.6 (specified)

Error (regular_file): read_ksyms stat /proc/ksyms failed No modules in ksyms, skipping objects
No ksyms, skipping lsmod

May 16 13:29:34 debian kernel: Unable to handle kernel paging request at virtual address 1841b518
May 16 13:29:34 debian kernel: c016c02e
May 16 13:29:34 debian kernel: *pde = 00000000
May 16 13:29:34 debian kernel: Oops: 0000 [#1]
May 16 13:29:34 debian kernel: CPU:    0
May 16 13:29:34 debian kernel: EIP:    0060:[proc_get_inode+110/272]    Not tainted
May 16 13:29:34 debian kernel: EFLAGS: 00010202   (2.6.6) 
May 16 13:29:34 debian kernel: eax: 00000000   ebx: df107850   ecx: 0114df68   edx: 36013bf9
May 16 13:29:34 debian kernel: esi: dffec810   edi: dffdee00   ebp: 00000007   esp: d5037e30
May 16 13:29:34 debian kernel: ds: 007b   es: 007b   ss: 0068
May 16 13:29:35 debian kernel: Stack: df107850 f0000000 df7f19c0 e0820ead dffec810 c5bef353 dffec863 c016e8e3 
May 16 13:29:35 debian kernel:        dffdee00 f0000000 dffec810 ffffffea 00000000 dffdddd0 d5037f70 c5bef2d0 
May 16 13:29:35 debian kernel:        c5bef2d0 c016c1d1 dffdddd0 c5bef2d0 d5037f70 fffffff4 dffdde38 dffdddd0 
May 16 13:29:35 debian kernel: Call Trace:

Warning (Oops_read): Code line not seen, dumping what data is available

Quoted 4 lines
Quoted 4 lines

ebx; df107850 <pg0+1ed30850/3fc27000>
esi; dffec810 <pg0+1fc15810/3fc27000>
edi; dffdee00 <pg0+1fc07e00/3fc27000>
esp; d5037e30 <pg0+14c60e30/3fc27000>

May 16 13:29:35 debian kernel: Code: 8b 46 18 c7 43 38 00 00 00 00 89 43 34 0f b7 46 0e 66 85 c0 

Using defaults from ksymoops -t elf32-i386 -a i386

Code; 00000000 Before first symbol
00000000 <_EIP>:
Code; 00000000 Before first symbol
0: 8b 46 18 mov 0x18(%esi),%eax
Code; 00000003 Before first symbol
3: c7 43 38 00 00 00 00 movl $0x0,0x38(%ebx)
Code; 0000000a Before first symbol
a: 89 43 34 mov %eax,0x34(%ebx)
Code; 0000000d Before first symbol
d: 0f b7 46 0e movzwl 0xe(%esi),%eax
Code; 00000011 Before first symbol
11: 66 85 c0 test %ax,%ax

1 warning and 1 error issued. Results may not be reliable.

#1 lore raw
Quoted 29 lines · tmp

I get the attached oops message in syslog on my 2.6.6 kernel. I have
also attached the ksymoops output.

When the oops has occured, I cannot open any shell (including a login shell).

[oops1.txt text/plain (2452 bytes)]

 May 16 13:29:34 debian kernel: Unable to handle kernel paging request at virtual address 1841b518
 May 16 13:29:34 debian kernel:  printing eip:
 May 16 13:29:34 debian kernel: c016c02e
 May 16 13:29:34 debian kernel: *pde = 00000000
 May 16 13:29:34 debian kernel: Oops: 0000 [#1]
 May 16 13:29:34 debian kernel: CPU:    0
 May 16 13:29:34 debian kernel: EIP:    0060:[proc_get_inode+110/272]    Not tainted
 May 16 13:29:34 debian kernel: EFLAGS: 00010202   (2.6.6) 
 May 16 13:29:34 debian kernel: EIP is at proc_get_inode+0x6e/0x110
 May 16 13:29:34 debian kernel: eax: 00000000   ebx: df107850   ecx: 0114df68   edx: 36013bf9
 May 16 13:29:34 debian kernel: esi: dffec810   edi: dffdee00   ebp: 00000007   esp: d5037e30
 May 16 13:29:34 debian kernel: ds: 007b   es: 007b   ss: 0068
 May 16 13:29:35 debian kernel: Process emacs (pid: 743, threadinfo=d5036000 task=d3ec8030)
 May 16 13:29:35 debian kernel: Stack: df107850 f0000000 df7f19c0 e0820ead dffec810 c5bef353 dffec863 c016e8e3 
 May 16 13:29:35 debian kernel:        dffdee00 f0000000 dffec810 ffffffea 00000000 dffdddd0 d5037f70 c5bef2d0 
 May 16 13:29:35 debian kernel:        c5bef2d0 c016c1d1 dffdddd0 c5bef2d0 d5037f70 fffffff4 dffdde38 dffdddd0 
 May 16 13:29:35 debian kernel: Call Trace:
 May 16 13:29:35 debian kernel:  [pg0+541367981/1069707264] unix_stream_sendmsg+0x24d/0x3a0 [unix]
 May 16 13:29:35 debian kernel:  [proc_lookup+179/192] proc_lookup+0xb3/0xc0
Quoted 8 lines
 May 16 13:29:35 debian kernel:  [proc_root_lookup+49/128] proc_root_lookup+0x31/0x80
 May 16 13:29:35 debian kernel:  [real_lookup+203/240] real_lookup+0xcb/0xf0
 May 16 13:29:35 debian kernel:  [do_lookup+150/176] do_lookup+0x96/0xb0
 May 16 13:29:35 debian kernel:  [link_path_walk+1052/2048] link_path_walk+0x41c/0x800
 May 16 13:29:35 debian kernel:  [path_lookup+105/272] path_lookup+0x69/0x110
 May 16 13:29:35 debian kernel:  [open_namei+131/1024] open_namei+0x83/0x400
 May 16 13:29:35 debian kernel:  [__pollwait+0/208] __pollwait+0x0/0xd0
 May 16 13:29:35 debian kernel:  [filp_open+62/112] filp_open+0x3e/0x70

It's a bit strange that no registers have a value vaguely like 0x1841b518, but at a guess I'd say that you have a bad ->owner pointer in a /proc inode.

What modules are you using, and had any modules been rmmod'ed prior to the crash?

author
#2 lore raw

Thanks, for your reply!

Quoted 5 lines

It's a bit strange that no registers have a value vaguely like 0x1841b518, but at a guess I'd say that you have a bad ->owner pointer in a /proc inode.

What modules are you using

$ lsmod
Module                  Size  Used by
apm                    15536  1
md5                     3648  1
ipv6                  220064  19
snd_ice1712            41928  0
snd_ice17xx_ak4xxx      3136  1 snd_ice1712
snd_pcm_oss            48420  0
snd_mixer_oss          17216  1 snd_pcm_oss
snd_pcm                81636  2 snd_ice1712,snd_pcm_oss
snd_page_alloc          8964  1 snd_pcm
snd_timer              19844  1 snd_pcm
snd_ak4xxx_adda         5376  2 snd_ice1712,snd_ice17xx_ak4xxx
snd_cs8427              8768  1 snd_ice1712
snd_ac97_codec         60868  1 snd_ice1712
snd_i2c                 4800  2 snd_ice1712,snd_cs8427
snd_mpu401_uart         5824  1 snd_ice1712
snd_rawmidi            18976  1 snd_mpu401_uart
ide_scsi               13764  0
scsi_mod               61500  1 ide_scsi
parport_pc             18528  1
lp                      7940  0
parport                20608  2 parport_pc,lp
nls_cp437               5376  2
rtc                     9464  0
unix                   21552  612
Quoted 2 lines

, and had any modules been rmmod'ed prior
to the crash?

No.

By the way, I can tell, that I recently got the following message printed on a shell I opened, just before it crashed (handwritten from screen (keyboard was locked)):

Assertion failure in __journal_file_buffer() at fs/jbd/transaction.c:1934: "jh->b_transaction == transaction || jh->b_transaction == 0"