I get this during the running of a script that creates a VE.

The relevant part of the script goes like this:

- - - - - - - --
vzctl create ${VM_NO} --ostemplate debian-4.0-local --config vps.basic 
|| { echo "Error creating VM"; exit 1; }

vzctl set ${VM_NO} --privvmpages 32767:65535 --save
vzctl set ${VM_NO} --name ${VM_NAME} --save
vzctl set ${VM_NO} --onboot yes --save
- - - - - - - - -

I think the error happens during the create or the setting of 
privvmpages, otherwise I'd see more (or less) output.

The server is a very bog standard Debian Etch (minimal system plus sudo, 
ssh, ntp, less, dnsutils, locale, vzctl, vzquota, vzprocps, vzdump, and 
vzctl-ostmpl-debian.  I have made minor changes to the template 
(changing /etc/apt/sources.txt, modifying resolv.conf with a search and 
ndots clause, and setting a few environment variables in /etc/profile). 
I have updated the kernel from debian.systs.org (i'm using ovzkernel-2.6.18)

here's the error:

vs1:~# mk-svn 101 /root/svn-dump.gz
Creating VE private area (debian-4.0-local)

Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
vs1 kernel: ------------[ cut here ]------------

Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
vs1 kernel: kernel BUG at kernel/ub/ub_mem.c:387!

Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
vs1 kernel: invalid opcode: 0000 [#1]

Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
vs1 kernel: esi: 00000202   edi: c10a0500   ebp: 00000080   esp: d3cbfea8

Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
vs1 kernel: ds: 007b   es: 007b   ss: 0068

Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
vs1 kernel: Process gzip (pid: 4931, veid: 0, ti=d3cbf000 task=d752e660 
task.ti=d3cbf000)

Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
vs1 kernel: Stack: c10a0500 c050a068 d752e660 000600d2 c050a068 c01505ec 
c10a0500 00000000

Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
vs1 kernel:        000600d2 d7f7ea00 000600d2 00000000 00000010 c10a0500 
c01785ae 094896ed

Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
vs1 kernel:        00000000 00001000 00000001 cecdec00 00000000 00000000 
c0178c09 d6b57000

Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
vs1 kernel:  Call Trace:

Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
vs1 kernel: Code: 5c 24 04 8b 74 24 08 8b 7c 24 0c 8b 6c 24 10 83 c4 14 
c3 56 9d 8b 77 20 85 f6 75 1c 89 1c 24 e8 49 e5 ff ff b8 f4 ff ff ff eb 
d4 <0f> 0b 66 b8 83 01 b8 1d 54 49 c0 eb c2 0f 0b 66 b8 89 01 b8 1d

Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
vs1 kernel: EIP: [<c013866e>] ub_page_charge+0xae/0xd0 SS:ESP 0068:d3cbfea8

Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
vs1 kernel: CPU:    0, VCPU: 0.0

Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
vs1 kernel: EIP is at ub_page_charge+0xae/0xd0

Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
vs1 kernel: eax: 00000001   ebx: c05ec480   ecx: 00000000   edx: c05ed360

Steve

On 1/08/2007 1:42 PM, Steve Hodges wrote:
> I get this during the running of a script that creates a VE.
>

I probably should add that I don't see it very often.  This may be the 
third time.  And I've used that same script to create hundreds of VEs 
(mostly to test the script).

Steve

Steve Hodges wrote:
> On 1/08/2007 1:42 PM, Steve Hodges wrote:
>> I get this during the running of a script that creates a VE.
>>
>
> I probably should add that I don't see it very often.  This may be the 
> third time.  And I've used that same script to create hundreds of VEs 
> (mostly to test the script).

What kernel version is it?

Steve,

it very much looks like a hardware memory corruption :/
Though I have no your exact vmlinux at hands, I suppose ub is loaded in %esi
and is compared to 0. In your case esi==0x202, which is a 2 bit change.

Plz check your memory with memtest86 (http://wiki.openvz.org/Hardware_testing)

Thanks,
Kirill

Steve Hodges wrote:
> I get this during the running of a script that creates a VE.
> 
> The relevant part of the script goes like this:
> 
> - - - - - - - --
> vzctl create ${VM_NO} --ostemplate debian-4.0-local --config vps.basic 
> || { echo "Error creating VM"; exit 1; }
> 
> vzctl set ${VM_NO} --privvmpages 32767:65535 --save
> vzctl set ${VM_NO} --name ${VM_NAME} --save
> vzctl set ${VM_NO} --onboot yes --save
> - - - - - - - - -
> 
> I think the error happens during the create or the setting of 
> privvmpages, otherwise I'd see more (or less) output.
> 
> The server is a very bog standard Debian Etch (minimal system plus sudo, 
> ssh, ntp, less, dnsutils, locale, vzctl, vzquota, vzprocps, vzdump, and 
> vzctl-ostmpl-debian.  I have made minor changes to the template 
> (changing /etc/apt/sources.txt, modifying resolv.conf with a search and 
> ndots clause, and setting a few environment variables in /etc/profile). 
> I have updated the kernel from debian.systs.org (i'm using ovzkernel-2.6.18)
> 
> here's the error:
> 
> vs1:~# mk-svn 101 /root/svn-dump.gz
> Creating VE private area (debian-4.0-local)
> 
> Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
> vs1 kernel: ------------[ cut here ]------------
> 
> Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
> vs1 kernel: kernel BUG at kernel/ub/ub_mem.c:387!
> 
> Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
> vs1 kernel: invalid opcode: 0000 [#1]
> 
> Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
> vs1 kernel: esi: 00000202   edi: c10a0500   ebp: 00000080   esp: d3cbfea8
> 
> Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
> vs1 kernel: ds: 007b   es: 007b   ss: 0068
> 
> Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
> vs1 kernel: Process gzip (pid: 4931, veid: 0, ti=d3cbf000 task=d752e660 
> task.ti=d3cbf000)
> 
> Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
> vs1 kernel: Stack: c10a0500 c050a068 d752e660 000600d2 c050a068 c01505ec 
> c10a0500 00000000
> 
> Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
> vs1 kernel:        000600d2 d7f7ea00 000600d2 00000000 00000010 c10a0500 
> c01785ae 094896ed
> 
> Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
> vs1 kernel:        00000000 00001000 00000001 cecdec00 00000000 00000000 
> c0178c09 d6b57000
> 
> Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
> vs1 kernel:  Call Trace:
> 
> Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
> vs1 kernel: Code: 5c 24 04 8b 74 24 08 8b 7c 24 0c 8b 6c 24 10 83 c4 14 
> c3 56 9d 8b 77 20 85 f6 75 1c 89 1c 24 e8 49 e5 ff ff b8 f4 ff ff ff eb 
> d4 <0f> 0b 66 b8 83 01 b8 1d 54 49 c0 eb c2 0f 0b 66 b8 89 01 b8 1d
> 
> Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
> vs1 kernel: EIP: [<c013866e>] ub_page_charge+0xae/0xd0 SS:ESP 0068:d3cbfea8
> 
> Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
> vs1 kernel: CPU:    0, VCPU: 0.0
> 
> Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
> vs1 kernel: EIP is at ub_page_charge+0xae/0xd0
> 
> Message from syslogd@vs1 at Wed Aug  1 13:21:40 2007 ...
> vs1 kernel: eax: 00000001   ebx: c05ec480   ecx: 00000000   edx: c05ed360
> 
> Steve