Hello all, I have a debian sarge hardware node and the 2.6.8 kernel has been fetched from kernel.org patched with openvz-022stab07. I also used the smp config file. Additionally I did enable xfs support. Now however I received a kernel oops. The kernel oops occured during a copy action (cp). I have pasted the message I saw on the terminal below Does this make sense to anybody? Any help is gratefully appreciated... Regards, Kim Unable to handle kernel paging request at virtual address 9b4a19fc printing eip: c011a843 *pde = 00000000 Oops: 0000 [#1] SMP Modules linked in: simfs vznetdev vzdquota vzmon vzdev af_packet ipt_length ipt_ ttl ipt_tcpmss ipt_TCPMSS iptable_mangle iptable_filter ipt_multiport ipt_limit ipt_tos ipt_REJECT ip_tables sg sr_mod ehci_hcd ohci_hcd usbcore tg3 e100 mii id e_cd cdrom ide_scsi CPU: 11, VCPU: 393221:524295 EIP: 0060:[<c011a843>] Not tainted EFLAGS: 00010086 (2.6.8-elex-openvz-022stab077) EIP is at activate_task+0x33/0x1b0 eax: 9b4a19e0 ebx: c354b000 ecx: 000001a4 edx: 0001e17e esi: f3e1b260 edi: 00000001 ebp: dbeb5048 esp: dbeb5018 ds: 007b es: 007b ss: 0068 Unable to handle kernel paging request at virtual address 00090008 printing eip: c01063f7 *pde = 00000000 File erased !
1) Is there the whole oops text in /var/log/messages? I mean, that you've posted not all information about oops: usually call trace exists in oops text, something like that: Quote: ... kernel: Call Trace: kernel: [prune_dcache+246/320] prune_dcache+0xf6/0x140 kernel: [shrink_dcache_memory+27/80] shrink_dcache_memory+0x1b/0x50 kernel: [shrink_slab+311/400] shrink_slab+0x137/0x190 kernel: [balance_pgdat+416/656] balance_pgdat+0x1a0/0x290 kernel: [kswapd+221/240] kswapd+0xdd/0xf0 kernel: [kswapd+0/240] kswapd+0x0/0xf0 kernel: [autoremove_wake_function+0/64] autoremove_wake_function+0x0/0x40 kernel: [autoremove_wake_function+0/64] autoremove_wake_function+0x0/0x40 kernel: [kernel_thread_helper+5/16] kernel_thread_helper+0x5/0x10 kernel: Code: 83 78 24 00 75 0a 50 e8 10 fe ff ff 83 c4 04 c3 50 e8 06 ff ff ff 83 c4 04 c3 89 f6 53 8b 5c 24 08 85 db 74 55 8b 83 98 00 00 00 <8b> 40 24 83 bb 24 01 00 00 20 75 08 0f 0b 4c 04 f1 7e 45 c0 85 ... Such information is highly usefull for us, to understand the reason of oops. 2) Do you use xfs on /vz partion? 3) Have you copied inside VPS or on HN? Thanks.
Can you please check if oops text is available in some file (like /var/log/messages) and if yes, give us the full oops text (the best way is to file a bug to http://bugzilla.openvz.org/).
1) Is there the whole oops text in /var/log/messages? No, I do not see any trace stack in my complete /var/log folder 2) Do you use xfs on /vz partion? Yes I use xfs for /vz on an lvm volume (and also for the other partitions btw) 3) Have you copied inside VPS or on HN? I copied data on the Hn from one VPS to antoher. The machine has 2 VPS's, both VPS's where running The info I saw has been copied from the serial console, in our company we use serial port redirection and all data is being sent to the serial port which is being captured by device. The info I already pasted is comming from there Regards, Kim
That's excellent that you have serial console set up! Can you attach the full oops report here, including some preceding lines as well?
Hi Kir, Well, the only output I saw on my serial console is the one listed in the original post My serial console redirection has been set up in grub with the following statements: serial --unit=0 --speed=9600 --word=8 --parity=no --stop=1 terminal --timeout=10 serial console title Debian GNU/Linux, kernel 2.6.8-elex-openvz-022stab077 root (hd0,0) kernel /vmlinuz-2.6.8-openvz-022stab077 root=/dev/md1 ro console=tty0 console=ttyS0,9600n initrd /initrd.img-2.6.8-openvz-022stab077 savedefault boot I have also enabled a tty in /etc/inittab: T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100 Regards, Kim
I see from your oops, that kernel can't even print full oops text. When kernel tries to output information second oops occurs: Quote: ds: 007b es: 007b ss: 0068 Unable to handle kernel paging request at virtual address 9b4a19fc printing eip: c011a843 *pde = 00000000 .... ds: 007b es: 007b ss: 0068 Unable to handle kernel paging request at virtual address 00090008 printing eip: c01063f7 *pde = 00000000 Can you check memory on your node please? BTW, what did happen after oops? The node in question hanged or rebooted or worked further? Thanks.
Hi, Here is a screendump of the current mem usage: Cpu(s): 0.0% us, 0.0% sy, 0.0% ni, 100.0% id, 0.0% wa, 0.0% hi, 0.0% si Mem: 3100624k total, 3079184k used, 21440k free, 39664k buffers Swap: 1959912k total, 0k used, 1959912k free, 2863528k cached After the oops the complete machine hanged and I saw the earlier posted message on the serial console, the only action I could take was cutting the power of the machine and starting it up again. Regards, Kim
Quote: Can you check memory on your node please? I meant check your RAM for errors You can use something like memtest86 programm.