2007-08-09 23:17:36

by shacky

[permalink] [raw]
Subject: Unable to handle kernel paging request at virtual address

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.


2007-08-09 23:40:31

by Dave Jones

[permalink] [raw]
Subject: Re: Unable to handle kernel paging request at virtual address

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

2007-08-09 23:44:38

by shacky

[permalink] [raw]
Subject: Re: Unable to handle kernel paging request at virtual address

> 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.

2007-08-10 00:09:20

by Dave Jones

[permalink] [raw]
Subject: Re: Unable to handle kernel paging request at virtual address

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

2007-08-10 11:03:34

by shacky

[permalink] [raw]
Subject: Re: Unable to handle kernel paging request at virtual address

> 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.

2007-08-10 11:20:31

by shacky

[permalink] [raw]
Subject: Re: Unable to handle kernel paging request at virtual address

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! :-)