Unable to handle kernel paging request at virtual address

Unable to handle kernel paging request at virtual address

[shacky]

Hi.
I installed Ubuntu 7.04 and then upgraded to the future 7.10 on my
system based on an Asus Pundit barebone with 512 mb RAM and 120 Gb IDE
hard disk.
The system works without any problem, but when I try to shutdown or
restart the system, after a while during the shutdown process, the
system hangs and I see this error:

[87.935473] BUG: unable to handle kernel paging request at virtual
address 6d207972
[...........] printing eip:
[...........] 6d207972
[...........] *pde = 00000000
[...........] Oops: 000 [#2]
[...........] SMP
[...........] Modules linked in: bluetooth capability lirc_dev
speedstep_lib cpufreq_powersave cpufreq_stats cpufreq_userspace
cpufreq_ondemand cpufreq_conservative freq_table video container sbs
button dock ac battery ipv6 sbp2 lp fuse snd_emu10k1_synth
snd_emux_synth snd_seq_virmidi snd_seq_midi_emul  [....] etc.

I'm using the kernel 2.6.22.

I'm omitting the rest of the error because it is very very long and I
have to rewrite it because I can't copy&paste it. If you need some
other information please ask. :-)

Could you help me, please? What could be the problem?

Thank you very much!
Bye.

Re: Unable to handle kernel paging request at virtual address

[Dave Jones]

On Fri, Aug 10, 2007 at 01:17:14AM +0200, shacky wrote:

 > [87.935473] BUG: unable to handle kernel paging request at virtual
 > address 6d207972
 > [...........] printing eip:
 > [...........] 6d207972
 > [...........] *pde = 00000000
 > [...........] Oops: 000 [#2]
 > [...........] SMP
 > [...........] Modules linked in: bluetooth capability lirc_dev
 > speedstep_lib cpufreq_powersave cpufreq_stats cpufreq_userspace
 > cpufreq_ondemand cpufreq_conservative freq_table video container sbs
 > button dock ac battery ipv6 sbp2 lp fuse snd_emu10k1_synth
 > snd_emux_synth snd_seq_virmidi snd_seq_midi_emul  [....] etc.
 > 
 > I'm using the kernel 2.6.22.
 > 
 > I'm omitting the rest of the error because it is very very long and I
 > have to rewrite it because I can't copy&paste it. If you need some
 > other information please ask. :-)

You snipped the most important part.  Even a digital photo of the
crash would be more useful than what we have above.
So far, there's not really much to go on.

	Dave

-- 
http://www.codemonkey.org.uk

Re: Unable to handle kernel paging request at virtual address

[shacky]

> You snipped the most important part.  Even a digital photo of the
> crash would be more useful than what we have above.
> So far, there's not really much to go on.

Could you tell me what is the most important part, so I try to rewrite
it by hand?
I don't think a digital photo will be much useful because the whole
error is writed on a simple black screen with white caracters.

Re: Unable to handle kernel paging request at virtual address

[Dave Jones]

On Fri, Aug 10, 2007 at 01:44:24AM +0200, shacky wrote:
 > > You snipped the most important part.  Even a digital photo of the
 > > crash would be more useful than what we have above.
 > > So far, there's not really much to go on.
 > 
 > Could you tell me what is the most important part, so I try to rewrite
 > it by hand?

It's hard to blindly guess because there's so little to go on.
At the least, a complete list of the modules loaded, the EIP/RIP
and the call trace. (This makes up 90% of the output, hence the
suggestion to take a photograph).

 > I don't think a digital photo will be much useful because the whole
 > error is writed on a simple black screen with white caracters.

That's expected. We usually cope with that quite well.

	Dave

-- 
http://www.codemonkey.org.uk

Re: Unable to handle kernel paging request at virtual address

[shacky]

> It's hard to blindly guess because there's so little to go on.
> At the least, a complete list of the modules loaded, the EIP/RIP
> and the call trace. (This makes up 90% of the output, hence the
> suggestion to take a photograph).

Ok, I wrote down all the error:

===========================================================
[9271.829711] BUG: unable to handle kernel paging request at virtual
address 6d207972
[9271.829805] printing eip:
[9271.829845] 6d207972
[9271.829883] *pde = 00000000
[9271.829926] Oops: 000 [#2]
[9271.829965] SMP
[9271.830067] Modules linked in: bluetooth capability lirc_dev ppdev
speedstep_lib cpufreq_powersave cpufreq_stats cpufreq_userspace
cpufreq_ondemand cpufreq_conservative freq_table video container sbs
button dock ac battery ipv6 sbp2 lp fuse snd_emu10k1_synth
snd_emux_synth snd_seq_virmidi snd_seq_midi_emul snd_emu10k1
snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm
snd_page_alloc and_util_mem snd_hwdep snd_seq_dummy snd_seq_oss
snd_seq_midi snd_rawmidi snd_seq_midi_event pcmcia snd_seq snd_timer
snd_seq_device parport_pc snd parport serio_raw psmouse pcspkr
emu10k1_gp soundcore yenta_socket rsrc_nonstatic pcmcia_core gameport
i2c_sis96x shpchp i2c_core pci_hotplug sis_agp agpgart af_packet evdev
reiserfs sg sr_mod cdrom sd_mod b44 mii ehci_hcd ohci_hcd usbcore
pata_sis ata_generic libata scsi_mod ohci1394 ieee1394 thermal
processor fan apparmor commoncap aamatch_pcre
[9271.833075] CPU:    0
[9271.833076] EIP:    0060:[<6d207972>]    Not tainted VLI
[9271.833078] EFLAGS: 00010206   (2.6.22-9-generic #1)
[9271.833212] EIP is at 0x6d207972
[9271.833255] eax: d55f5c08   ebx: d26f0a00   ecx: 00000000   edx: 6d207972
[9271.833305] esi: 01234567   edi: b7f8fff4   ebp: d3218000   esp: d3219e8c
[9271.833371] ds: 007b   es: 007b   fs: 00d8  gs: 0033  ss: 0068
[9271.833435] Process reboot (pid: 9650, ti=d3218000 task=d8b2af60
task.ti=d3218000)
[9271.833501] Stack: c026326c 00000000 c013585b c02f2c7e 28121969
28121969 c0135a4a 000000c3
[9271.833868]        c158fcd4 c158fcd4 c015e660 00000148 c13b5b00
c0161001 c0284a32 00000000
[9271.834236]        d3219f50 ddf6d420 dc2ada80 dc2adac8 c158fc30
00000000 00000000 c043ac20
[9271.843603] Call trace:
[9271.834704]  [<c026326c>] device_shutdown+0x3c/0x90
[9271.834818]  [<c013585b>] kernel_restart+0xb/0x50
[9271.834915]  [<c02f2c7e>] lock_kernel+0x1e/0x40
[9271.835028]  [<c0135a4a>] sys_reboot+0x19a/0x1e0
[9271.835140]  [<c015e660>] find_get_page+0x20/0x60
[9271.835249]  [<c0161001>] filemap_nopage+0x181/0x340
[9271.835344]  [<c0284a32>] netdev_run_todo+0x142/0x250
[9271.835512]  [<c02f2a58>] _spin_lock_bh+0x8/0x20
[9271.835624]  [<c01a32fe>] invalidate_inode_buffers+0xe/0xc0
[9271.835719]  [<c02f2a58>] _spin_lock_bh+0x8/0x20
[9271.835878]  [<c0193d9e>] destroy_inode+0x2e/0x50
[9271.835993]  [<c0191758>] d_kill+0x38/0x50
[9271.836098]  [<c0192457>] dput+0x87/0x100
[9271.836197]  [<c01814eb>] __fput+0x12b/0x1a0
[9271.836318]  [<c0196884>] mntput_no_expire+0x24/0xa0
[9271.836430]  [<c017e8f7>] filp_close+0x47/0x80
[9271.836548]  [<c017fc6b>] sys_close+0x6b/0xd0
[9271.836658]  [<c01041d2>] sysenter_pat_esp+0x6b/0xa9
[9271.836848]  =======================
[9271.836905] Code:  Bad EIP value.
[9271.837024] EIP: [<6d207972>] 0x6d207972 SS:ESP 0068:d3219e8c
===========================================================

Thank you very much!
Bye.

Re: Unable to handle kernel paging request at virtual address

[shacky]

I think this problem is caused by the lirc_serial module, because if I
try to modprobe the lirc_serial module I get this error:

kobject_add failed for lirc_serial.0 with -EEXIST, don't try to
register things whith the same name in the same directory.
kobject_shadow_add
kobject_set_name
device_add
platform_device_add
init_module
sys_init_module
prio_tree_insert
sysenter_past_esp

But I don't understand why it happens...

Have you any idea?
Thank you very much! :-)

Unable to handle kernel paging request at virtual address

[pavankvk]

Reference to my previous mail..the actual error message on console is given below..
Unable to handle kernel paging request at virtual address c2acc6d8
current->tss.cr3 = 0116e000, ^Pr3 = 0116e000
*pde = 0009e067
*pte = 00000000
Oops: 0000
CPU:    0
EIP:    0010:[dev_close+52/184]
EFLAGS: 00010206
eax: 00000000   ebx: 02acc6d8   ecx: 00000002   edx: 73cb2605
esi: 00000000   edi: 0001fdfc   ebp: 00001143   esp: 00b38ef8
ds: 0018   es: 0018   fs: 002b   gs: 002b   ss: 0018
Process ifconfig (pid: 4602, process nr: 98, stackpage=00b38000)
Stack: 02acc6d8 00000002 0001fdfc 0001fdfc bffff9b8 00b38f60 001397e8 0001fdfc
       bffff998 00008914 0804c983 00b47810 00000000 0098a1d4 40075000 010c0c98
       0006d000 ffffffed 31687465 0804e000 0804c921 08048bc8 08041142 0804cdef
Call Trace: [<02acc6d8>] [dev_ifsioc+708/1628] [dev_ioctl+439/508] [inet_ioctl+871/960] [sock_ioctl+33/40] [sys_ioctl+255/272] [system_call+85/124] 

Code: 8b 03 ff d0 83 c4 0c 66 85 c0 7c 07 8b 5b 04 85 db 75 e9 57





Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com

 Buy Music, Video, CD-ROM, Audio-Books and Music Accessories from http://www.planetm.co.in

Unable to handle kernel paging request at virtual address....

[Femitha Majeed]

Hi,

I am trying to write a kernel module which reads the files in the /proc 
directory.

When I do an insmod filename.o, I get the following error:
Unable to handle kernel paging request at virtual address....

In the module, I use kmalloc to allocate memory. Is that the reason I am 
getting this error?

I am very new to writing kernel modules, I would really appreciate a reply.

Thanks,
Femitha Majeed

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

Re: Unable to handle kernel paging request at virtual address....

[Erik Mouw]

On Sat, Nov 10, 2001 at 04:23:03AM +0000, Femitha Majeed wrote:
> I am trying to write a kernel module which reads the files in the /proc 
> directory.

The idea behind /proc is that it allows userland to read or write
certain kernel variables. You shouldn't read a /proc file from within
the kernel.

> When I do an insmod filename.o, I get the following error:
> Unable to handle kernel paging request at virtual address....
> 
> In the module, I use kmalloc to allocate memory. Is that the reason I am 
> getting this error?

Without having your source it's impossible to tell. Please read the
procfs guide in your kernel tree or at
http://www.kernelnewbies.org/documents/ .

> I am very new to writing kernel modules, I would really appreciate a reply.

Go to the www.kernelnewbies.org website and subscribe to the
kernelnewbies mailing list. The #kernelnewbies IRC channel is also
quite helpful.


Erik

-- 
J.A.K. (Erik) Mouw, Information and Communication Theory Group, Faculty
of Information Technology and Systems, Delft University of Technology,
PO BOX 5031, 2600 GA Delft, The Netherlands  Phone: +31-15-2783635
Fax: +31-15-2781843  Email: J.A.K.Mouw@its.tudelft.nl
WWW: http://www-ict.its.tudelft.nl/~erik/

Unable to handle kernel paging request at virtual address

[Dominik Sacher]

hi !
i not a kernel hacker, so i don't know, whom to write to.
maybe you can help !
i get several application-crashs on my redhat7.1 (updated to kernel 2.4.3-12) 
and every crash produces some kind of this:

----------------------------------------------------------------------------
Jul 16 20:04:35 jukebox kernel:  <1>Unable to handle kernel paging request at 
virtual address 41648370
Jul 16 20:04:35 jukebox kernel:  printing eip:
Jul 16 20:04:35 jukebox kernel: c013f6bc
Jul 16 20:04:35 jukebox kernel: pgd entry c8dd6414: 0000000000000000
Jul 16 20:04:35 jukebox kernel: pmd entry c8dd6414: 0000000000000000
Jul 16 20:04:35 jukebox kernel: ... pmd not present!
Jul 16 20:04:35 jukebox kernel: Oops: 0000
Jul 16 20:04:35 jukebox kernel: CPU:    0
Jul 16 20:04:35 jukebox kernel: EIP:    0010:[d_lookup+96/260]
Jul 16 20:04:35 jukebox kernel: EIP:    0010:[<c013f6bc>]
Jul 16 20:04:35 jukebox kernel: EFLAGS: 00010a87
Jul 16 20:04:35 jukebox kernel: eax: c1640000   ebx: 41648328   ecx: 0000000f 
  edx: 134b8ec9
Jul 16 20:04:35 jukebox kernel: esi: 134b8ec9   edi: c6c99f84   ebp: 41648340 
  esp: c6c99eb4
Jul 16 20:04:35 jukebox kernel: ds: 0018   es: 0018   ss: 0018
Jul 16 20:04:35 jukebox kernel: Process gkrellm (pid: 6233, 
stackpage=c6c99000)
Jul 16 20:04:35 jukebox kernel: Stack: c1648340 c43e000a 134b8ec9 00000005 
c6c99f18 134b8ec9 c6c99f84 c43e000f 
Jul 16 20:04:35 jukebox kernel:        c01377f6 ca020f60 c6c99f18 c6c99f18 
c0137eb7 ca020f60 c6c99f18 00000000 
Jul 16 20:04:35 jukebox kernel:        c6c99f04 c6c99f04 00000001 00000000 
00000000 c33df7e0 000009f7 000001f4 
Jul 16 20:04:35 jukebox kernel: Call Trace: [cached_lookup+14/72] 
[path_walk+1275/1880] [open_namei+145/1456] [filp_open+50/80] [getname+92/
152] 
Jul 16 20:04:35 jukebox kernel: Call Trace: [<c01377f6>] [<c0137eb7>] 
[<c01385c1>] [<c012dd72>] [<c0137608>] 
Jul 16 20:04:35 jukebox kernel:    [sys_open+49/148] [system_call+51/56] 
Jul 16 20:04:35 jukebox kernel:    [<c012e029>] [<c0106c1f>] 
Jul 16 20:04:35 jukebox kernel: 
Jul 16 20:04:35 jukebox kernel: Code: 39 53 48 8b 6d 00 0f 85 80 00 00 00 8b 
44 24 24 39 43 0c 75 
----------------------------------------------------------------------------

i even can compile me a new kernel (2.4.6 / 2.2.19), because everytime i try, 
i get this bug and the "make" process dies.
maybe someone can give a hint.

thanks a lot !
d.sacher

Re: Unable to handle kernel paging request at virtual address

[Jesse Wyant]

> hi !
> i not a kernel hacker, so i don't know, whom to write to.
> maybe you can help !
> i get several application-crashs on my redhat7.1 (updated to kernel 2.4.3-12) 
> and every crash produces some kind of this:

I've seen similar `Oopses' when I've compiled my ALSA sound drivers (for
my i815e motherboard's AC'97 audio) for the wrong kernel, or didn't do a 
`make clean' before recompiling ALSA.  But, to determine the problem, you
need to run your Oops output through 'ksymoops', do a 'man ksymoops' for
usage instructions.  This will attach library calls to all those pointers
in the Oops outputs.  That is where I would see that my Oopses were due
to ALSA, you should be able to better root-cause the problem this way.

-jesse

Jesse Wyant
------------------------------------------------------------
An Englishman never enjoys himself, except for a noble purpose.
		-- A.P. Herbert