[1.]
i occasionaly get "unable to handle kernel paging request" kernel error.
[2.]
i occasionaly (about once in 1 or 2 months) get "unable to handle kernel
paging request at virtual address XXXXXXXX" kernel error. it is always
related to "current->tss.cr3" and i think it is present in all 2.2.X kernels
up to 2.2.10 (included) - full message (i hope it's reproduced acurately) -
message has been displayed at about 8:15pm.
after about 80 seconds another similar massege apears on console with
diferent 2nd line:
current->tss.cr3 = 0519b000, %cr3 = 0519b000
i did not catch other diferencies while about 4 minutes after second message
3rd such mesage has been displayed on console (i was taking notes on paper).
so i shutdowned machine - here are error messages while shutting down:
Unmounting NFS filesystems
umount: /mnt/net: device is busy
<...>
Unmounting filesystemsCannot MOUNTPROG RPC: RPC Port mapper failure - \
RPC: Unable to send
lockd_down: no lockd running
umount2: Device or resource busy
umount: /mnt/hda2: device is busy
here i have to note that my root filesystem is on /dev/sda2 and that
/mnt/hda2 is my second etx2fs partition.
ater booting machine up, following lines apears in dmesg (and
/var/log/messages):
EXT2-fs error (device ide0(3,2)): ext2_check_blocks_bitmap: Wrong free \
blocks count for group 3, stored = 5221, counted = 5220
EXT2-fs error (device ide0(3,2)): ext2_check_blocks_bitmap: Wrong free \
blocks count in super block, stored = 175253, counted = 175252
[3.]
kernel, paging request, nfs, lockd, tss.cr3
[4.]
Linux version 2.2.10 (root@m1.megaloman.sk) (gcc version egcs-2.91.66 \
19990314/Linux (egcs-1.1.2 release)) #20 Tue Jun 15 09:06:40 EDT 1999
[5.]
Unable to handle kernel paging request at virtual address c834c284
current->tss.cr3 = 07a65000, %cr3 = 07a65000
*pde = 00000000
Oops = 002
CPU: 0
EIP: 0010:[<c0116301>]
EFLAGS: 00010282
eax: c834c280 ebx: 00000000 ecx: c6aa6cc0 edx: c0280000
esi: c6aa6cc0 edi: c03a1578 ebp: 00000000 esp: c7831f3c
ds: 0018 es: 0018 ss: 0018
Process rateup (pid: 8850, process nr.: 55, stackpage=c7831000
Stack: 00000000 00001000 c027ed18 00000000 00000000 40015000 c1c567a0 c6911694
00000000 00000001 00000000 c6aa6cc0 c011b4c3 c6911680 c6911694 c7831f8c
c0116410 c6911680 ffffffea 00000000 00000000 00001000 40014000 00000000
<this has been written to console>
[6.]
i do not know how to trigger this error.
[7.]
[7.1.]
-- Versions installed: (if some fields are empty or looks
-- unusual then possibly you have very old versions)
Linux m1.megaloman.sk 2.2.10 #20 Tue Jun 15 09:06:40 EDT 1999 i586 unknown
Kernel modules 2.1.121
Gnu C egcs-2.91.66
Binutils 2.9.1.0.23
Linux C Library 2.1.1
Dynamic linker ldd (GNU libc) 2.1.1
Procps 2.0.2
Mount 2.9o
Net-tools 1.52
Kbd [option...]
Sh-utils 1.16
Modules Loaded
- kbd: console-tools 19990302-13 from RedHat
[7.2.]
processor : 0
vendor_id : GenuineIntel
cpu family : 5
model : 4
model name : Pentium MMX
stepping : 3
cpu MHz : 200.458378
fdiv_bug : no
hlt_bug : no
sep_bug : no
f00f_bug : yes
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr mce cx8 mmx
bogomips : 399.77
[7.3.]
no modules
[7.4.]
Attached devices:
Host: scsi0 Channel: 00 Id: 01 Lun: 00
Vendor: SEAGATE Model: ST51080N Rev: 0913
Type: Direct-Access ANSI SCSI revision: 02
[7.5.]
portion of /var/log/messages which contains "unable ..." messages (a lot of
them), shutdown sequence and boot sequence [as attachemnt, gziped]
[8.]
i'm using RedHat i386 linux based on RedHat 6.0 RPMs mostly but with
significant number of packages rebuild by me using egcs-1.1.{1,2}. kernel is
compiled from common source files from ftp.kernel.org (not RedHat kernel).
NFS looks like affected but while at this last "incident" i'm using
knfsd-1.4-2 and knfsd-clients-1.4-2 (rebuild by me from RedHat SRPM),
previously i was using nfs-{server,server-clinets}-2.2.beta{37,44} but same
"unable to handle ..." error has occured with those versions of NFS too.
also X windows are slightly unstable (core dump) but i do not know whether
it is related.
peter hanecak
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/