unable to handle kernel paging request

It is very difficult to debug a Kernel Crash.

You can find more info about the problem either in dmesg or /var/log/kern.log

Also the /var/log/boot.log might contains useful info about the crash.

Regards
 NikTh

Thanks!

In kern.log I found this:

May 8 19:22:53 LP002 kernel: [ 6410.743266] CIFS VFS: ignoring corrupt resume name
May 8 19:22:53 LP002 kernel: [ 6411.345181] CIFS VFS: ignoring corrupt resume name
May 8 19:26:27 LP002 kernel: [ 6624.814687] CIFS VFS: ignoring corrupt resume name
May 8 19:28:13 LP002 kernel: [ 6730.978718] CIFS VFS: ignoring corrupt resume name
May 8 19:28:26 LP002 kernel: [ 6743.869566] CIFS VFS: ignoring corrupt resume name
May 8 19:28:27 LP002 kernel: [ 6744.591515] CIFS VFS: ignoring corrupt resume name
May 8 19:31:58 LP002 kernel: [ 6955.575846] CIFS VFS: ignoring corrupt resume name
May 8 19:32:19 LP002 kernel: [ 6975.809695] CIFS VFS: Send error in read = -11
May 8 19:34:02 LP002 kernel: [ 7078.769904] BUG: unable to handle kernel paging request at f7c0364f
May 8 19:34:02 LP002 kernel: [ 7078.769938] IP: [<f95129b3>] CIFSSMBQAllEAs+0x2b3/0x450 [cifs]
May 8 19:34:02 LP002 kernel: [ 7078.769970] *pdpt = 00000000019cd001 *pde = 0000000000000000
May 8 19:34:02 LP002 kernel: [ 7078.769995] Oops: 0000 [#1] SMP
May 8 19:34:02 LP002 kernel: [ 7078.770011] Modules linked in: des_generic(F) md4(F) parport_pc(F) ppdev(F) rfcomm bnep nls_utf8 cifs(F) fscache(F) snd_hda_codec_hdmi snd_hda_codec_realtek joydev(F) snd_usb_audio snd_usbmidi_lib uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev arc4(F) iwldvm mac80211 coretemp kvm_intel kvm snd_hda_intel snd_hda_codec aesni_intel(F) aes_i586(F) xts(F) lrw(F) gf128mul(F) ablk_helper(F) cryptd(F) snd_hwdep(F) snd_pcm(F) snd_page_alloc(F) snd_seq_midi(F) snd_seq_midi_event(F) snd_rawmidi(F) snd_seq(F) i915 snd_seq_device(F) samsung_laptop mei snd_timer(F) iwlwifi drm_kms_helper btusb cfg80211 mac_hid bluetooth drm video(F) snd(F) i2c_algo_bit lpc_ich psmouse(F) lp(F) parport(F) serio_raw(F) microcode(F) soundcore(F) hid_generic usbhid hid r8169 ahci(F) libahci(F)
May 8 19:34:02 LP002 kernel: [ 7078.770359] Pid: 6389, comm: pool Tainted: GF 3.8.0-19-generic #30-Ubuntu SAMSUNG ELECTRONICS CO., LTD. 300E4A/300E5A/300E7A/3430EA/3530EA/300E4A/300E5A/300E7A/3430EA/3530EA
May 8 19:34:02 LP002 kernel: [ 7078.770420] EIP: 0060:[<f95129b3>] EFLAGS: 00010202 CPU: 1
May 8 19:34:02 LP002 kernel: [ 7078.770444] EIP is at CIFSSMBQAllEAs+0x2b3/0x450 [cifs]
May 8 19:34:02 LP002 kernel: [ 7078.770465] EAX: f7c0364e EBX: 0000003e ECX: 00000000 EDX: 2bb1350b
May 8 19:34:02 LP002 kernel: [ 7078.770489] ESI: 0000f7fd EDI: 2bb1350f EBP: f77f9f1c ESP: f77f9ecc
May 8 19:34:02 LP002 kernel: [ 7078.770513] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
May 8 19:34:02 LP002 kernel: [ 7078.770545] CR0: 80050033 CR2: f7c0364f CR3: 2fe53000 CR4: 000407f0
May 8 19:34:02 LP002 kernel: [ 7078.770570] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
May 8 19:34:02 LP002 kernel: [ 7078.770595] DR6: ffff0ff0 DR7: 00000400
May 8 19:34:02 LP002 kernel: [ 7078.770612] Process pool (pid: 6389, ti=f77f8000 task=efeaa670 task.ti=f77f8000)
May 8 19:34:02 LP002 kernel: [ 7078.770641] Stack:
May 8 19:34:02 LP002 kernel: [ 7078.770651] efe10000 f77f9f0c 00000000 000000d0 f08dba00 00bd2cee 0000f7bf 00000000
May 8 19:34:02 LP002 kernel: [ 7078.770693] f7c03652 0001213e f77f9f04 f77f9f08 ee78d020 2bb1350f efe10000 efe10000
May 8 19:34:02 LP002 kernel: [ 7078.770735] 0000004f f24e5800 ee78d020 f26a1120 f77f9f58 f952b59a 00000000 00000000
May 8 19:34:02 LP002 kernel: [ 7078.770777] Call Trace:
May 8 19:34:02 LP002 kernel: [ 7078.770795] [<f952b59a>] cifs_listxattr+0xba/0x170 [cifs]
May 8 19:34:02 LP002 kernel: [ 7078.770822] [<f952b4e0>] ? cifs_getxattr+0x450/0x450 [cifs]
May 8 19:34:02 LP002 kernel: [ 7078.770848] [<c117e7aa>] vfs_listxattr+0x3a/0x60
May 8 19:34:02 LP002 kernel: [ 7078.770869] [<c117ea55>] listxattr+0xf5/0x100
May 8 19:34:02 LP002 kernel: [ 7078.770889] [<c116d22f>] ? user_path_at+0x1f/0x30
May 8 19:34:02 LP002 kernel: [ 7078.770910] [<c117f589>] sys_llistxattr+0x39/0x70
May 8 19:34:02 LP002 kernel: [ 7078.770933] [<c16198cd>] sysenter_do_call+0x12/0x28
May 8 19:34:02 LP002 kernel: [ 7078.770965] [<c161007b>] ? schedule_timeout+0x1bb/0x240
May 8 19:34:02 LP002 kernel: [ 7078.770994] Code: 04 89 cf 89 5d c4 eb 12 8b 55 d0 8d 44 32 01 8b 55 e4 85 d2 0f 84 0e 01 00 00 8d 50 04 89 55 d0 89 fa 83 ea 04 0f 88 cd 00 00 00 <0f> b6 58 01 0f b7 40 02 89 c6 01 de 89 45 c8 89 f0 f7 d0 01 d0
May 8 19:34:02 LP002 kernel: [ 7078.771214] EIP: [<f95129b3>] CIFSSMBQAllEAs+0x2b3/0x450 [cifs] SS:ESP 0068:f77f9ecc
May 8 19:34:02 LP002 kernel: [ 7078.771261] CR2: 00000000f7c0364f
May 8 19:34:02 LP002 kernel: [ 7078.808770] ---[ end trace 3139874054932ac4 ]---
May 8 19:36:59 LP002 kernel: imklog 5.8.11, log source = /proc/kmsg started.

Any advice on where to report this bug?

If this is a bug you should report it here in Launchpad bug tracker. Report a bug for linux

Open a terminal and apply this command

    ubuntu-bug linux

let the apport to collect all the info and then it will redirect you to the Launcphad page where you will report your bug.

Please be descriptive and cooperate with developers if they ask for something.

This is definitely a kernel panic but I cannot debug the "Call Trace".

Regards
 NikTh

Thanks.

I did as you proposed and repeorted the bug againt kernel.

Though the problem in itself hasnot been solved, I will close this question as "solved".