LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   "unable to handle kernel paging request" doing rsync (https://www.linuxquestions.org/questions/slackware-14/unable-to-handle-kernel-paging-request-doing-rsync-4175463297/)

Barx 05-24-2013 06:10 AM

"unable to handle kernel paging request" doing rsync
 
Hi

I've a fresh install of slackware 14.0 32 bit with all patches
Hardware tested OK (memtest and prime95)

The system seems to run good (now I've configured only samba and few more)

Now I'm trying to run a script to rsync slackware patches on the system itself ( :-) )

Every time I run rsync I got the following error (copied from the syslog)

Code:

May 24 11:06:06 server2 kernel: [ 1842.278600] BUG: unable to handle kernel paging request at f5dfdc00
May 24 11:06:06 server2 kernel: [ 1842.279005] IP: [<c110f1f7>] fget_light+0x27/0xc0
May 24 11:06:06 server2 kernel: [ 1842.279005] *pdpt = 0000000001e50001 *pde = 8000000035c001e3
May 24 11:06:06 server2 kernel: [ 1842.279005] Oops: 0009 [#1] SMP
May 24 11:06:06 server2 kernel: [ 1842.279005] Modules linked in: snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss ipv6 lp ppdev parport_pc parport snd_hda_codec_realtek nouveau mxm_wmi wmi video ttm drm_kms_helper drm agpgart snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer snd soundcore i2c_algo_bit k8temp psmouse serio_raw processor fan thermal thermal_sys evdev hwmon forcedeth i2c_nforce2 i2c_core firewire_ohci button firewire_core loop
May 24 11:06:06 server2 kernel: [ 1842.279005]
May 24 11:06:06 server2 kernel: [ 1842.279005] Pid: 2308, comm: rsync Not tainted 3.2.45-smp #2 HP-Pavilion GT667AA-ABZ a6200.it/Nettle2
May 24 11:06:06 server2 kernel: [ 1842.279005] EIP: 0060:[<c110f1f7>] EFLAGS: 00010282 CPU: 1
May 24 11:06:06 server2 kernel: [ 1842.279005] EIP is at fget_light+0x27/0xc0

Message from syslogd@server2 at Fri May 24 11:06:06 2013 ...
server2 kernel: [ 1842.279005] Oops: 0009 [#1] SMP
May 24 11:06:06 server2 kernel: [ 1842.279005] EAX: 00000004 EBX: 00000004 ECX: f5dfdc00 EDX: f3f29f98
May 24 11:06:06 server2 kernel: [ 1842.279005] ESI: 00004c20 EDI: 00000000 EBP: f3f29f8c ESP: f3f29f80
May 24 11:06:06 server2 kernel: [ 1842.279005]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068

Message from syslogd@server2 at Fri May 24 11:06:06 2013 ...
server2 kernel: [ 1842.279005] Process rsync (pid: 2308, ti=f3f28000 task=f303f3c0 task.ti=f3f28000)

Message from syslogd@server2 at Fri May 24 11:06:06 2013 ...
server2 kernel: [ 1842.279005] Stack:
May 24 11:06:06 server2 kernel: [ 1842.279005] Process rsync (pid: 2308, ti=f3f28000 task=f303f3c0 task.ti=f3f28000)
May 24 11:06:06 server2 kernel: [ 1842.279005] Stack:
May 24 11:06:06 server2 kernel: [ 1842.279005]  00000004 00004c20 00000000 f3f29fac c110dee8 f3f29f9c 00000000 00ac0000
May 24 11:06:06 server2 kernel: [ 1842.279005]  00000000 00000004 00004c20 f3f28000 c1a6ac04 00000004 0881d2c8 00004c20
May 24 11:06:06 server2 kernel: [ 1842.279005]  00004c20 00000000 08741a38 00000003 0000007b 0000007b 00000000 00000033
May 24 11:06:06 server2 kernel: [ 1842.279005] Call Trace:
May 24 11:06:06 server2 kernel: [ 1842.279005]  [<c110dee8>] sys_read+0x18/0x70
May 24 11:06:06 server2 kernel: [ 1842.279005]  [<c1a6ac04>] syscall_call+0x7/0xb
May 24 11:06:06 server2 kernel: [ 1842.279005] Code: f3 ff eb e0 55 89 e5 83 ec 0c 89 5d f4 89 75 f8 89 7d fc 3e 8d 74 26 00 64 8b 0d 4c 15 e4 c1 8b 89 b4 02 00 00 c7 02 00 00 00 00 <8b> 19 83 fb 01 74 2a 8b 49 04 3b 01 73 12 8b 49 04 8d 04 81 8b
May 24 11:06:06 server2 kernel: [ 1842.279005] EIP: [<c110f1f7>] fget_light+0x27/0xc0 SS:ESP 0068:f3f29f80
May 24 11:06:06 server2 kernel: [ 1842.279005] CR2: 00000000f5dfdc00
May 24 11:06:06 server2 kernel: [ 1842.279005] ---[ end trace 96f6eb1ee14ca442 ]---

Message from syslogd@server2 at Fri May 24 11:06:06 2013 ...
server2 kernel: [ 1842.279005] EIP: [<c110f1f7>] fget_light+0x27/0xc0 SS:ESP 0068:f3f29f80

Message from syslogd@server2 at Fri May 24 11:06:06 2013 ...
server2 kernel: [ 1842.279005] CR2: 00000000f5dfdc00

Message from syslogd@server2 at Fri May 24 11:06:06 2013 ...
server2 kernel: [ 1842.279005] Code: f3 ff eb e0 55 89 e5 83 ec 0c 89 5d f4 89 75 f8 89 7d fc 3e 8d 74 26 00 64 8b 0d 4c 15 e4 c1 8b 89 b4 02 00 00 c7 02 00 00 00 00 <8b> 19 83 fb 01 74 2a 8b 49 04 3b 01 73 12 8b 49 04 8d 04 81 8b

Message from syslogd@server2 at Fri May 24 11:06:06 2013 ...
server2 kernel: [ 1842.279005] Call Trace:

Any hint?

Thank you

ljb643 05-25-2013 07:31 PM

Quote:

3.2.45-smp #2
Is this a kernel you built yourself? If so, have you tried / are you able to instead use the Slackware-released kernel-generic-smp-3.2.45_smp-i686-2?
(I know that patch is -2, but I have it and it shows "3.2.45-smp #1", which makes me think you might be running a custom-built kernel.)

Barx 05-27-2013 01:56 AM

no, it's the one released in /patches/ , I haven's recompiled it

In any case, I was getting the same problem with slackware 14.0 stock kernel (3.2.29)

Celyr 05-27-2013 03:38 AM

I trink it's a faulty memory chip, wich tests have you done with memtest86?

Barx 05-27-2013 04:50 AM

2 loops of memtest86+ 4.2.0 with default settings, no errors detected

niknah 06-06-2013 08:01 AM

I had the "unable to handle kernel paging request" error a few times too, I think it was all the moisture in the air.
I opened up the case for a few hours and it stopped happening.


All times are GMT -5. The time now is 11:08 PM.