[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#631526: marked as done (linux-image-2.6.32-5-686-bigmem: "mmu_update failed" with >1017M of memory and loaded from pv-grub-x86_32.gz in xen 4.0.1)

Your message dated Sun, 29 May 2016 21:24:52 +0100
with message-id d3c8e39c-1ea5-4aa5-93e6-98be75a69ccf@decadent.org.uk
and subject line Closing bugs assigned to linux-2.6 package
has caused the Debian Bug report #631526,
regarding linux-image-2.6.32-5-686-bigmem: "mmu_update failed" with >1017M of memory and loaded from pv-grub-x86_32.gz in xen 4.0.1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
631526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631526
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.32-5-686-bigmem
Version: 2.6.32-34squeeze1
Severity: normal

I'm running Xen 3.4.2 and 4.0.1 dom0s (on centos 5.5). I compiled
pvgrub from those upstream versions of xen, and when
/usr/lib/xen/boot/pv-grub-x86_32.gz tries to load the
2.6.32-5-686-bigmem kernel it fails:
  Booting 'Debian GNU/Linux, kernel 2.6.32-5-686-bigmem'

  root  (hd0,0)
   Filesystem type is ext2fs, partition type 0x83
   kernel  /boot/vmlinuz-2.6.32-5-686-bigmem root=/dev/xvda1 
   initrd  /boot/initrd.img-2.6.32-5-686-bigmem

   ERROR: mmu_update failed with rc=-22
   Do_exit called!
   base is 0x3ff3fcd8 caller is 0x4d477
   base is 0x3ff3fd08 caller is 0x59a06
   base is 0x3ff3fd68 caller is 0x59c50
   base is 0x3ff3fdb8 caller is 0x17f41
   base is 0x3ff3fe28 caller is 0x3ac8
   base is 0x3ff3fe48 caller is 0x8b7a
   base is 0x3ff3fe58 caller is 0xa433
   base is 0x3ff3fe78 caller is 0x10059
   base is 0x3ff3fef8 caller is 0x10679
   base is 0x3ff3ff68 caller is 0x40a1
   base is 0x3ff3ff88 caller is 0x4eacc
   base is 0x3ff3fff0 caller is 0x31ad

memory = is set to 1024, but if its set to 1017 or less, it
works. If I load the kernel directly in /etc/xen/, the kernel
works with memory=1024. Below is the entire domU config file.
Thanks!

kernel = "/usr/lib/xen/boot/pv-grub-x86_32.gz"
#kernel = "/home/nick/vmlinuz-2.6.32-5-686-bigmem"
#ramdisk = "/home/nick/initrd.img-2.6.32-5-686-bigmem"
extra = "(hd1,0)/boot/grub/menu.lst"
#extra = "root=/dev/xvda1 ro"
cpu_weight=1024
vcpus=2
cpus="1-7"

#should really be 1024 but pvgrub won't load the debian 2.6.32-5-686-bigmem kernel with 1024 of memory
memory = 1017
name = "andy"
vif = ['vifname=andy,ip=123.123.123.123,bridge=xenbr0,mac=aa:00:00:0d:5f:be' ]
disk = [
        'phy:/dev/guests/andy,xvda,w',
        'phy:/dev/guests/i386rescue,xvde,r',
        'phy:/dev/guests/distros,xvdf,r'
]

--- End Message ---
--- Begin Message --- 
Version: 3.4.1-1~experimental.1+rm

Debian 6.0 Long Term Support has ended, and the 'linux-2.6' source
package will no longer be updated.  This bug was reassigned to the
'linux' source package earlier today, but I am now closing it on the
assumption that it does not affect the kernel versions in newer Debian
releases.

If you can still reproduce this bug in a newer release, please reopen
the bug report and reassign it to 'src:linux' and the affected version
of the package.  You can find the package version for the running
kernel by running:

    uname -v

or the versions of all installed kernel packages by running:

    dpkg -l 'linux-image-[34]*' | grep ^.i

and looking at the third column.

I apologise that we weren't able to provide a specific resolution for
this bug.

Ben.

-- 
Ben Hutchings - Debian developer, member of Linux kernel and LTS teams

--- End Message ---
Reply to: