Gerry Reno
2010-Apr-23 17:50 UTC
[Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
I previously had the pv_ops dom0 2.6.31.6 kernel built and running on my hardware (amd phenom ii x4 quad-core) just fine under karmic. But that kernel had issues with rxchecksumming. So I upgraded the server to lucid and am now trying to compile a new pv_ops dom0 kernel for it. Now, yesterday I carefully built the latest 2.6.32.10(xen/stable) pv_ops dom0 kernel twice. Once from the config in the email Lucid pv_ops dom0 howto and once from the lucid server config modified by adding all the XEN configurations. I get the same result both ways. After building the kernel, I try to start the pv_ops dom0 kernel as domU just to make sure it runs and it crashes right at the start of boot complaining like this: __vmallic_node+0xa2/0xb0 ? alloc_large_system_hash+0x15/0x21 ? inet_init+0x0/0x209 __vmalloc+0x22/0x30 alloc_large_system_hash+0x15/0x21a ? inet_init+0x0/0x209 ? inet_init+0x0/0x209 tcp_init+0xa3//0x37e inet_init+0x14b/0x209 do_one_initcall+0x3c/0x10a kernel_init+0x159/0x1af child_rip+0xa/0x20 Code: d0 49 8b 04 24 48 85 c0 75 ec eb c5 55 48 89 e5 48 8.... 9 5d e8 4c 89 65 f0 4c 89 6d f8 0f 1f 44 00 00 48 89 e5 48 8.... RIP [<ffffffff810f4f5f>] __free_pages+0x1f/0x90 ---[ end trace e93713a9d40cd06d ]--- Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: swapper Tainted: G D W 2.6.32.10 #4 panic+0x78/0x136 ? mm_release+0x60/0x130 do_exit+0x6ca/0x7f0 oops_end+0xaf/0xf0 die+0x5b/0x90 do_general_protection+0x152/0x160 general_protection+0x25/0x30 ? __free_pages+0x1f/0x90 __vunmap+0x7a/0x110 vfree+0x2a/0x30 __vmalloc_area_node+0x15c/0x190 ? alloc_large_system_hash+0x15a/0x21a __vmalloc_node+0xa2/0xb0 ? alloc_large_system_hash+0x15a/0x21a ? inet_init+0x0/0x209 ? inet_init+0x0/0x209 tcp_init+0xa3//0x37e inet_init+0x14b/0x209 do_one_initcall+0x3c/0x10a kernel_init+0x159/0x1af child_rip+0xa/0x20 ? kernel_init+0x10/0x1af ? child_rip+0x0/0x20 I fired up the old 2.6.31.6 kernel with lucid and it boots just fine as domU. Can anyone shed some light on what may be the problem here and how I can build a working 2.6.32.10 pv_ops dom0 kernel for this hardware? -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2010-Apr-23 18:27 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
I''ve just was able to reproduce Thiago''s instruction on
Lucid RC for Xen 4.0 & 2.6.32.10 pvops kernel ( C2D E8400 , ASUS P5Q-E, 8 GB
RAM) . ACPI Processor
has been disabled, what is particular MB issue
Quote :-
1.Clone JF''s Git Repo:
cd /usr/src
git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
linux-2.6-xen
cd linux-2.6-xen
git checkout -b xen/stable origin/xen/stable
2. Configure, compile and install:
make menuconfig # Enabled the dom0 support and the Xen backend as usual on U
9.10, F12
make -j2
chmod g-s /usr/src -R
make deb-pkg
dpkg -i ../linux-image*2.6.32.10*.deb
depmod 2.6.32.10
update-initramfs -c -k 2.6.32.10
update-grub
echo "xen-evtchn" >> /etc/modules
3- Download and install the latest Xen:
Preparing your environment:
apt-get build-dep xen-3.3
aptitude install uuid-dev iasl texinfo
Download and compile:
cd /usr/src
Uncompress xen-4.0.0.tar.gz
cd xen-4.0.0
make xen
make tools
make install-xen
make install-tools PYTHON_PREFIX_ARG
update-rc.d xend defaults 20 21
update-rc.d xendomains defaults 21 20
4. Add to /boot/grub/grub.cfg
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the ''exec tail'' line above.
menuentry "Xen 4.0 / Ubuntu 10.4 RC kernel 2.6.32.10 pvops" {
insmod ext2
set root=(hd1,4)
multiboot (hd1,4)/xen.gz dummy=dummy
module (hd1,4)/vmlinuz-2.6.32.10 dummy=dummy root=/dev/sdb5 ro console=tty0
module (hd1,4)/initrd.img-2.6.32.10
Quote ends.
--- On Fri, 4/23/10, Gerry Reno <greno@verizon.net> wrote:
From: Gerry Reno <greno@verizon.net>
Subject: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
To: xen-devel@lists.xensource.com
Date: Friday, April 23, 2010, 1:50 PM
I previously had the pv_ops dom0 2.6.31.6 kernel built and running on my
hardware (amd phenom ii x4 quad-core) just fine under karmic. But that kernel
had issues with rxchecksumming. So I upgraded the server to lucid and am now
trying to compile a new pv_ops dom0 kernel for it.
Now, yesterday I carefully built the latest 2.6.32.10(xen/stable) pv_ops dom0
kernel twice. Once from the config in the email Lucid pv_ops dom0 howto and
once from the lucid server config modified by adding all the XEN
configurations. I get the same result both ways. After building the kernel, I
try to start the pv_ops dom0 kernel as domU just to make sure it runs and it
crashes right at the start of boot complaining like this:
__vmallic_node+0xa2/0xb0
? alloc_large_system_hash+0x15/0x21
? inet_init+0x0/0x209
__vmalloc+0x22/0x30
alloc_large_system_hash+0x15/0x21a
? inet_init+0x0/0x209
? inet_init+0x0/0x209
tcp_init+0xa3//0x37e
inet_init+0x14b/0x209
do_one_initcall+0x3c/0x10a
kernel_init+0x159/0x1af
child_rip+0xa/0x20
Code: d0 49 8b 04 24 48 85 c0 75 ec eb c5 55 48 89 e5 48 8....
9 5d e8 4c 89 65 f0 4c 89 6d f8 0f 1f 44 00 00 48 89 e5 48 8....
RIP [<ffffffff810f4f5f>] __free_pages+0x1f/0x90
---[ end trace e93713a9d40cd06d ]---
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: swapper Tainted: G D W 2.6.32.10 #4
panic+0x78/0x136
? mm_release+0x60/0x130
do_exit+0x6ca/0x7f0
oops_end+0xaf/0xf0
die+0x5b/0x90
do_general_protection+0x152/0x160
general_protection+0x25/0x30
? __free_pages+0x1f/0x90
__vunmap+0x7a/0x110
vfree+0x2a/0x30
__vmalloc_area_node+0x15c/0x190
? alloc_large_system_hash+0x15a/0x21a
__vmalloc_node+0xa2/0xb0
? alloc_large_system_hash+0x15a/0x21a
? inet_init+0x0/0x209
? inet_init+0x0/0x209
tcp_init+0xa3//0x37e
inet_init+0x14b/0x209
do_one_initcall+0x3c/0x10a
kernel_init+0x159/0x1af
child_rip+0xa/0x20
? kernel_init+0x10/0x1af
? child_rip+0x0/0x20
I fired up the old 2.6.31.6 kernel with lucid and it boots just fine as domU.
Can anyone shed some light on what may be the problem here and how I can build a
working 2.6.32.10 pv_ops dom0 kernel for this hardware?
-Gerry
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Boris Derzhavets
2010-Apr-23 18:55 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
I skipped first instruction ( before kernel build ):
# aptitude install build-essential libncurses5-dev dpkg-dev debhelper fakeroot
Boris.
--- On Fri, 4/23/10, Boris Derzhavets <bderzhavets@yahoo.com> wrote:
From: Boris Derzhavets <bderzhavets@yahoo.com>
Subject: Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
To: xen-devel@lists.xensource.com, "Gerry Reno"
<greno@verizon.net>
Date: Friday, April 23, 2010, 2:27 PM
I''ve just was able to reproduce Thiago''s instruction on
Lucid RC for Xen 4.0 & 2.6.32.10 pvops kernel ( C2D E8400 , ASUS P5Q-E, 8 GB
RAM) . ACPI Processor
has been disabled, what is particular MB issue
Quote :-
1.Clone JF''s Git Repo:
cd /usr/src
git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
linux-2.6-xen
cd linux-2.6-xen
git checkout -b xen/stable origin/xen/stable
2. Configure, compile and install:
make menuconfig # Enabled the dom0 support and the Xen backend as usual on U
9.10, F12
make -j2
chmod g-s /usr/src -R
make deb-pkg
dpkg -i ../linux-image*2.6.32.10*.deb
depmod 2.6.32.10
update-initramfs -c -k
2.6.32.10
update-grub
echo "xen-evtchn" >> /etc/modules
3- Download and install the latest Xen:
Preparing your environment:
apt-get build-dep xen-3.3
aptitude install uuid-dev iasl texinfo
Download and compile:
cd /usr/src
Uncompress xen-4.0.0.tar.gz
cd xen-4.0.0
make xen
make tools
make install-xen
make install-tools PYTHON_PREFIX_ARG
update-rc.d xend defaults 20 21
update-rc.d xendomains defaults 21 20
4. Add to /boot/grub/grub.cfg
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the ''exec tail'' line above.
menuentry "Xen 4.0 / Ubuntu 10.4 RC kernel 2.6.32.10 pvops" {
insmod ext2
set root=(hd1,4)
multiboot (hd1,4)/xen.gz
dummy=dummy
module (hd1,4)/vmlinuz-2.6.32.10 dummy=dummy root=/dev/sdb5 ro console=tty0
module (hd1,4)/initrd.img-2.6.32.10
Quote ends.
--- On Fri, 4/23/10, Gerry Reno <greno@verizon.net> wrote:
From: Gerry Reno <greno@verizon.net>
Subject: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
To: xen-devel@lists.xensource.com
Date: Friday, April 23, 2010, 1:50 PM
I previously had the pv_ops dom0 2.6.31.6 kernel built and running on my
hardware (amd phenom ii x4 quad-core) just fine under karmic. But that kernel
had issues with rxchecksumming. So I upgraded the server to lucid and am now
trying to compile a new pv_ops dom0 kernel for it.
Now, yesterday I carefully built the latest 2.6.32.10(xen/stable) pv_ops dom0
kernel twice.
Once from the config in the email Lucid pv_ops dom0 howto and once from the
lucid server config modified by adding all the XEN configurations. I get the
same result both ways. After building the kernel, I try to start the pv_ops
dom0 kernel as domU just to make sure it runs and it crashes right at the start
of boot complaining like this:
__vmallic_node+0xa2/0xb0
? alloc_large_system_hash+0x15/0x21
? inet_init+0x0/0x209
__vmalloc+0x22/0x30
alloc_large_system_hash+0x15/0x21a
? inet_init+0x0/0x209
? inet_init+0x0/0x209
tcp_init+0xa3//0x37e
inet_init+0x14b/0x209
do_one_initcall+0x3c/0x10a
kernel_init+0x159/0x1af
child_rip+0xa/0x20
Code: d0 49 8b 04 24 48 85 c0 75 ec eb c5 55 48 89 e5 48 8....
9 5d e8 4c 89 65 f0 4c 89 6d f8 0f 1f 44 00 00 48 89 e5 48 8....
RIP [<ffffffff810f4f5f>] __free_pages+0x1f/0x90
---[ end trace e93713a9d40cd06d ]---
Kernel panic - not syncing: Attempted to kill
init!
Pid: 1, comm: swapper Tainted: G D W 2.6.32.10 #4
panic+0x78/0x136
? mm_release+0x60/0x130
do_exit+0x6ca/0x7f0
oops_end+0xaf/0xf0
die+0x5b/0x90
do_general_protection+0x152/0x160
general_protection+0x25/0x30
? __free_pages+0x1f/0x90
__vunmap+0x7a/0x110
vfree+0x2a/0x30
__vmalloc_area_node+0x15c/0x190
? alloc_large_system_hash+0x15a/0x21a
__vmalloc_node+0xa2/0xb0
? alloc_large_system_hash+0x15a/0x21a
? inet_init+0x0/0x209
? inet_init+0x0/0x209
tcp_init+0xa3//0x37e
inet_init+0x14b/0x209
do_one_initcall+0x3c/0x10a
kernel_init+0x159/0x1af
child_rip+0xa/0x20
? kernel_init+0x10/0x1af
? child_rip+0x0/0x20
I fired up the old 2.6.31.6 kernel with lucid and it boots just fine as domU.
Can anyone shed some light on what may be the problem here and how I can build a
working 2.6.32.10 pv_ops dom0 kernel for this hardware?
-Gerry
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
-----Inline Attachment Follows-----
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Gerry Reno
2010-Apr-23 20:38 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
Boris Derzhavets wrote:> I skipped first instruction ( before kernel build ): > > # aptitude install build-essential libncurses5-dev dpkg-dev debhelper > fakeroot > > Boris. > > --- On *Fri, 4/23/10, Boris Derzhavets /<bderzhavets@yahoo.com>/* wrote: > > > From: Boris Derzhavets <bderzhavets@yahoo.com> > Subject: Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on > AMD quad-core > To: xen-devel@lists.xensource.com, "Gerry Reno" <greno@verizon.net> > Date: Friday, April 23, 2010, 2:27 PM > > I''ve just was able to reproduce Thiago''s instruction on Lucid RC > for Xen 4.0 & 2.6.32.10 pvops kernel ( C2D E8400 , ASUS P5Q-E, 8 > GB RAM) . ACPI Processor > has been disabled, what is particular MB issue > > Quote :- > > 1.Clone JF''s Git Repo: > > cd /usr/src > git clone > git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git > linux-2.6-xen > cd linux-2.6-xen > git checkout -b xen/stable origin/xen/stable > > > 2. Configure, compile and install: > > make menuconfig # Enabled the dom0 support and the Xen backend as > usual on U 9.10, F12 > > make -j2 > chmod g-s /usr/src -R > make deb-pkg > dpkg -i ../linux-image*2.6.32.10*.deb > depmod 2.6.32.10 > update-initramfs -c -k 2.6.32.10 > update-grub > echo "xen-evtchn" >> /etc/modules > > 3- Download and install the latest Xen: > > Preparing your environment: > > apt-get build-dep xen-3.3 > aptitude install uuid-dev iasl texinfo > > Download and compile: > > cd /usr/src > Uncompress xen-4.0.0.tar.gz > cd xen-4.0.0 > make xen > make tools > make install-xen > make install-tools PYTHON_PREFIX_ARG> > update-rc.d xend defaults 20 21 > update-rc.d xendomains defaults 21 20 > > > 4. Add to /boot/grub/grub.cfg > > # This file provides an easy way to add custom menu entries. > Simply type the > # menu entries you want to add after this comment. Be careful not > to change > # the ''exec tail'' line above. > menuentry "Xen 4.0 / Ubuntu 10.4 RC kernel 2.6.32.10 pvops" { > insmod ext2 > set root=(hd1,4) > multiboot (hd1,4)/xen.gz dummy=dummy > module (hd1,4)/vmlinuz-2.6.32.10 dummy=dummy root=/dev/sdb5 ro > console=tty0 > module (hd1,4)/initrd.img-2.6.32.10 > > Quote ends. > > > --- On *Fri, 4/23/10, Gerry Reno /<greno@verizon.net>/* wrote: > > > From: Gerry Reno <greno@verizon.net> > Subject: [Xen-devel] Cannot load latest 2.6.32.10 kernel on > AMD quad-core > To: xen-devel@lists.xensource.com > Date: Friday, April 23, 2010, 1:50 PM > > I previously had the pv_ops dom0 2.6.31.6 kernel built and > running on my hardware (amd phenom ii x4 quad-core) just fine > under karmic. But that kernel had issues with > rxchecksumming. So I upgraded the server to lucid and am now > trying to compile a new pv_ops dom0 kernel for it. > > Now, yesterday I carefully built the latest > 2.6.32.10(xen/stable) pv_ops dom0 kernel twice. Once from the > config in the email Lucid pv_ops dom0 howto and once from the > lucid server config modified by adding all the XEN > configurations. I get the same result both ways. After > building the kernel, I try to start the pv_ops dom0 kernel as > domU just to make sure it runs and it crashes right at the > start of boot complaining like this: > > __vmallic_node+0xa2/0xb0 > ? alloc_large_system_hash+0x15/0x21 > ? inet_init+0x0/0x209 > __vmalloc+0x22/0x30 > alloc_large_system_hash+0x15/0x21a > ? inet_init+0x0/0x209 > ? inet_init+0x0/0x209 > tcp_init+0xa3//0x37e > inet_init+0x14b/0x209 > do_one_initcall+0x3c/0x10a > kernel_init+0x159/0x1af > child_rip+0xa/0x20 > Code: d0 49 8b 04 24 48 85 c0 75 ec eb c5 55 48 89 e5 48 8.... > 9 5d e8 4c 89 65 f0 4c 89 6d f8 0f 1f 44 00 00 48 89 e5 48 8.... > RIP [<ffffffff810f4f5f>] __free_pages+0x1f/0x90 > ---[ end trace e93713a9d40cd06d ]--- > Kernel panic - not syncing: Attempted to kill init! > Pid: 1, comm: swapper Tainted: G D W 2.6.32.10 #4 > panic+0x78/0x136 > ? mm_release+0x60/0x130 > do_exit+0x6ca/0x7f0 > oops_end+0xaf/0xf0 > die+0x5b/0x90 > do_general_protection+0x152/0x160 > general_protection+0x25/0x30 > ? __free_pages+0x1f/0x90 > __vunmap+0x7a/0x110 > vfree+0x2a/0x30 > __vmalloc_area_node+0x15c/0x190 > ? alloc_large_system_hash+0x15a/0x21a > __vmalloc_node+0xa2/0xb0 > ? alloc_large_system_hash+0x15a/0x21a > ? inet_init+0x0/0x209 > ? inet_init+0x0/0x209 > tcp_init+0xa3//0x37e > inet_init+0x14b/0x209 > do_one_initcall+0x3c/0x10a > kernel_init+0x159/0x1af > child_rip+0xa/0x20 > ? kernel_init+0x10/0x1af > ? child_rip+0x0/0x20 > > I fired up the old 2.6.31.6 kernel with lucid and it boots > just fine as domU. > > Can anyone shed some light on what may be the problem here and > how I can build a working 2.6.32.10 pv_ops dom0 kernel for > this hardware? > > -Gerry > > > > > -----Inline Attachment Follows----- > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > </mc/compose?to=Xen-devel@lists.xensource.com> > http://lists.xensource.com/xen-devel > >Boris, Those are the exact steps that I used to build the kernel. At the end of step 2, I try to boot the new kernel as domU just to make sure it works and this is where I get the stacktrace. I did not have this problem building and running 2.6.31.6 as either domU or dom0. And I think this may be related to this MB using AMD Phenom II Quad-Core. -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2010-Apr-23 21:31 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
Then i would try to disable backend drivers ( block,blktap,network) and rebuild the kernel for test in DomU. Boris. --- On Fri, 4/23/10, Gerry Reno <greno@verizon.net> wrote: From: Gerry Reno <greno@verizon.net> Subject: Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core To: xen-devel@lists.xensource.com Date: Friday, April 23, 2010, 4:38 PM Boris Derzhavets wrote:> I skipped first instruction ( before kernel build ): > > # aptitude install build-essential libncurses5-dev dpkg-dev debhelper > fakeroot > > Boris. > > --- On *Fri, 4/23/10, Boris Derzhavets /<bderzhavets@yahoo.com>/* wrote: > > > From: Boris Derzhavets <bderzhavets@yahoo.com> > Subject: Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on > AMD quad-core > To: xen-devel@lists.xensource.com, "Gerry Reno" <greno@verizon.net> > Date: Friday, April 23, 2010, 2:27 PM > > I''ve just was able to reproduce Thiago''s instruction on Lucid RC > for Xen 4.0 & 2.6.32.10 pvops kernel ( C2D E8400 , ASUS P5Q-E, 8 > GB RAM) . ACPI Processor > has been disabled, what is particular MB issue > > Quote :- > > 1.Clone JF''s Git Repo: > > cd /usr/src > git clone > git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git > linux-2.6-xen > cd linux-2.6-xen > git checkout -b xen/stable origin/xen/stable > > > 2. Configure, compile and install: > > make menuconfig # Enabled the dom0 support and the Xen backend as > usual on U 9.10, F12 > > make -j2 > chmod g-s /usr/src -R > make deb-pkg > dpkg -i ../linux-image*2.6.32.10*.deb > depmod 2.6.32.10 > update-initramfs -c -k 2.6.32.10 > update-grub > echo "xen-evtchn" >> /etc/modules > > 3- Download and install the latest Xen: > > Preparing your environment: > > apt-get build-dep xen-3.3 > aptitude install uuid-dev iasl texinfo > > Download and compile: > > cd /usr/src > Uncompress xen-4.0.0.tar.gz > cd xen-4.0.0 > make xen > make tools > make install-xen > make install-tools PYTHON_PREFIX_ARG> > update-rc.d xend defaults 20 21 > update-rc.d xendomains defaults 21 20 > > > 4. Add to /boot/grub/grub.cfg > > # This file provides an easy way to add custom menu entries. > Simply type the > # menu entries you want to add after this comment. Be careful not > to change > # the ''exec tail'' line above. > menuentry "Xen 4.0 / Ubuntu 10.4 RC kernel 2.6.32.10 pvops" { > insmod ext2 > set root=(hd1,4) > multiboot (hd1,4)/xen.gz dummy=dummy > module (hd1,4)/vmlinuz-2.6.32.10 dummy=dummy root=/dev/sdb5 ro > console=tty0 > module (hd1,4)/initrd.img-2.6.32.10 > > Quote ends. > > > --- On *Fri, 4/23/10, Gerry Reno /<greno@verizon.net>/* wrote: > > > From: Gerry Reno <greno@verizon.net> > Subject: [Xen-devel] Cannot load latest 2.6.32.10 kernel on > AMD quad-core > To: xen-devel@lists.xensource.com > Date: Friday, April 23, 2010, 1:50 PM > > I previously had the pv_ops dom0 2.6.31.6 kernel built and > running on my hardware (amd phenom ii x4 quad-core) just fine > under karmic. But that kernel had issues with > rxchecksumming. So I upgraded the server to lucid and am now > trying to compile a new pv_ops dom0 kernel for it. > > Now, yesterday I carefully built the latest > 2.6.32.10(xen/stable) pv_ops dom0 kernel twice. Once from the > config in the email Lucid pv_ops dom0 howto and once from the > lucid server config modified by adding all the XEN > configurations. I get the same result both ways. After > building the kernel, I try to start the pv_ops dom0 kernel as > domU just to make sure it runs and it crashes right at the > start of boot complaining like this: > > __vmallic_node+0xa2/0xb0 > ? alloc_large_system_hash+0x15/0x21 > ? inet_init+0x0/0x209 > __vmalloc+0x22/0x30 > alloc_large_system_hash+0x15/0x21a > ? inet_init+0x0/0x209 > ? inet_init+0x0/0x209 > tcp_init+0xa3//0x37e > inet_init+0x14b/0x209 > do_one_initcall+0x3c/0x10a > kernel_init+0x159/0x1af > child_rip+0xa/0x20 > Code: d0 49 8b 04 24 48 85 c0 75 ec eb c5 55 48 89 e5 48 8.... > 9 5d e8 4c 89 65 f0 4c 89 6d f8 0f 1f 44 00 00 48 89 e5 48 8.... > RIP [<ffffffff810f4f5f>] __free_pages+0x1f/0x90 > ---[ end trace e93713a9d40cd06d ]--- > Kernel panic - not syncing: Attempted to kill init! > Pid: 1, comm: swapper Tainted: G D W 2.6.32.10 #4 > panic+0x78/0x136 > ? mm_release+0x60/0x130 > do_exit+0x6ca/0x7f0 > oops_end+0xaf/0xf0 > die+0x5b/0x90 > do_general_protection+0x152/0x160 > general_protection+0x25/0x30 > ? __free_pages+0x1f/0x90 > __vunmap+0x7a/0x110 > vfree+0x2a/0x30 > __vmalloc_area_node+0x15c/0x190 > ? alloc_large_system_hash+0x15a/0x21a > __vmalloc_node+0xa2/0xb0 > ? alloc_large_system_hash+0x15a/0x21a > ? inet_init+0x0/0x209 > ? inet_init+0x0/0x209 > tcp_init+0xa3//0x37e > inet_init+0x14b/0x209 > do_one_initcall+0x3c/0x10a > kernel_init+0x159/0x1af > child_rip+0xa/0x20 > ? kernel_init+0x10/0x1af > ? child_rip+0x0/0x20 > > I fired up the old 2.6.31.6 kernel with lucid and it boots > just fine as domU. > > Can anyone shed some light on what may be the problem here and > how I can build a working 2.6.32.10 pv_ops dom0 kernel for > this hardware? > > -Gerry > > > > > -----Inline Attachment Follows----- > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > </mc/compose?to=Xen-devel@lists.xensource.com> > http://lists.xensource.com/xen-devel > >Boris, Those are the exact steps that I used to build the kernel. At the end of step 2, I try to boot the new kernel as domU just to make sure it works and this is where I get the stacktrace. I did not have this problem building and running 2.6.31.6 as either domU or dom0. And I think this may be related to this MB using AMD Phenom II Quad-Core. -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-Apr-24 06:12 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
Boris Derzhavets wrote:> Then i would try to disable backend drivers ( block,blktap,network) > and rebuild the kernel for test in DomU. > > Boris. >Ok, I disabled packet and inet and now getting a different error. Something about address collision and BAR 3, can''t setup and message about ACPI_PSS objects. So I google this for a while and find that many many other AMD users having similar messages/problems with the newer kernels. It seems there is some problem between ACPI and PIIX4 SMBUS. No BIOS update seems to fix it. Maybe a BIOS issue that needs a quirk. This particular machine has MB: Gigabyte GAMA790GP-UD4H w/AMD Phenom II X4. I''ve tried noacpi on boot line but didn''t help. Any suggestions? -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-Apr-24 06:32 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
Gerry Reno wrote:> Boris Derzhavets wrote: >> Then i would try to disable backend drivers ( block,blktap,network) >> and rebuild the kernel for test in DomU. >> >> Boris. >> > Ok, I disabled packet and inet and now getting a different error. > Something about address collision and BAR 3, can''t setup and message > about ACPI_PSS objects. So I google this for a while and find that > many many other AMD users having similar messages/problems with the > newer kernels. It seems there is some problem between ACPI and PIIX4 > SMBUS. No BIOS update seems to fix it. Maybe a BIOS issue that needs > a quirk. This particular machine has MB: Gigabyte GAMA790GP-UD4H > w/AMD Phenom II X4. I''ve tried noacpi on boot line but didn''t help. > Any suggestions? > > -GerryI just booted the Lucid kernel 2.6.32-21-server standard kernel and it has similar messages but it will boot fine. Where the powernow-k8 BAR 3 error is, instead of saying ''can''t setup'' like dom0 kernel, it says ''can''t allocate resource''. "Cool n Quiet" (freq scaling) is OFF in BIOS with this machine which isn''t a problem for this machine since it is a small server. Once again, any suggestions to compiling a bootable kernel? -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2010-Apr-24 07:34 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
Gerry, Can you boot Dom0 with 2.6.32.10 under Xen 4.X on top of Ubuntu Lucid RC Server? Boris. --- On Sat, 4/24/10, Gerry Reno <greno@verizon.net> wrote: From: Gerry Reno <greno@verizon.net> Subject: Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core To: xen-devel@lists.xensource.com Date: Saturday, April 24, 2010, 2:32 AM Gerry Reno wrote:> Boris Derzhavets wrote: >> Then i would try to disable backend drivers ( block,blktap,network) >> and rebuild the kernel for test in DomU. >> >> Boris. >> > Ok, I disabled packet and inet and now getting a different error. Something about address collision and BAR 3, can''t setup and message about ACPI_PSS objects. So I google this for a while and find that many many other AMD users having similar messages/problems with the newer kernels. It seems there is some problem between ACPI and PIIX4 SMBUS. No BIOS update seems to fix it. Maybe a BIOS issue that needs a quirk. This particular machine has MB: Gigabyte GAMA790GP-UD4H w/AMD Phenom II X4. I''ve tried noacpi on boot line but didn''t help. Any suggestions? > > -GerryI just booted the Lucid kernel 2.6.32-21-server standard kernel and it has similar messages but it will boot fine. Where the powernow-k8 BAR 3 error is, instead of saying ''can''t setup'' like dom0 kernel, it says ''can''t allocate resource''. "Cool n Quiet" (freq scaling) is OFF in BIOS with this machine which isn''t a problem for this machine since it is a small server. Once again, any suggestions to compiling a bootable kernel? -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-Apr-24 16:41 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
Boris Derzhavets wrote:> Gerry, > Can you boot Dom0 with 2.6.32.10 under Xen 4.X on top of Ubuntu Lucid > RC Server? > > Boris. >No, when I try to boot it as dom0 then I see errors about ''cannot locate IOAPIC for GSI 9'' and then the same ACPI_PSS object errors and then ACPI conflicts with PIIX4_SMBUS and finally something like ''cannot allocate MMIO region''. Then all I get is a blank screen. -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2010-Apr-24 17:30 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
I can load 2.6.32.10 under Xen 4.0 on ASUS P5Q3 (Q9550) and cannot on ASUS P5Q-E (C2D E8400) both based on ( Intel P45 + ICHR10 ), but different RAM DDR3 vs DDR2. ACPI 2 Support & ACPI APIC are enabled on both boards However, Disabling option <> processor allows to load 2.6.32.10 on ASUS P5Q-E allows to 2.6.32.10 on ASUS P5Q-E. [*] Power management and ACPI options ---> [*] ACPI (Advanced Configuration and Power Interface) Support ---> [*] Deprecated /proc/acpi files [*] Deprecated power /proc/acpi directories < > ACPI 4.0 power meter [*] Future power /sys interface [*] Deprecated /proc/acpi/event support <*> AC Adapter <*> Battery <*> Button <M> Video <*> Fan -*- Dock -> < > Processor -*- NUMA support [ ] Debug Statements <*> PCI slot detection driver <*> Container and Module Devices <M> Smart Battery System If you are interested view my the most recent reports to Yu Ke. Thread name :- Failure to load the most recent kernel 2.6.32.10 ( xen/stable) under Xen 4.0 on F12 (serial log) Boris. --- On Sat, 4/24/10, Gerry Reno <greno@verizon.net> wrote: From: Gerry Reno <greno@verizon.net> Subject: Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core To: xen-devel@lists.xensource.com Date: Saturday, April 24, 2010, 12:41 PM Boris Derzhavets wrote:> Gerry, > Can you boot Dom0 with 2.6.32.10 under Xen 4.X on top of Ubuntu Lucid RC Server? > > Boris. >No, when I try to boot it as dom0 then I see errors about ''cannot locate IOAPIC for GSI 9'' and then the same ACPI_PSS object errors and then ACPI conflicts with PIIX4_SMBUS and finally something like ''cannot allocate MMIO region''. Then all I get is a blank screen. -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2010-Apr-24 17:37 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
I believe you have to be aware of issue bellow. Boris. --- On Sat, 4/24/10, Gerry Reno <greno@verizon.net> wrote: From: Gerry Reno <greno@verizon.net> Subject: Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core To: xen-devel@lists.xensource.com Date: Saturday, April 24, 2010, 12:41 PM Boris Derzhavets wrote:> Gerry, > Can you boot Dom0 with 2.6.32.10 under Xen 4.X on top of Ubuntu Lucid RC Server? > > Boris. >No, when I try to boot it as dom0 then I see errors about ''cannot locate IOAPIC for GSI 9'' and then the same ACPI_PSS object errors and then ACPI conflicts with PIIX4_SMBUS and finally something like ''cannot allocate MMIO region''. Then all I get is a blank screen. -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2010-Apr-24 17:41 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
I am pretty sure Yu Ke will ask you to obtain a serial log, when problem will be escalated to him. Boris. --- On Sat, 4/24/10, Gerry Reno <greno@verizon.net> wrote: From: Gerry Reno <greno@verizon.net> Subject: Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core To: xen-devel@lists.xensource.com Date: Saturday, April 24, 2010, 12:41 PM Boris Derzhavets wrote:> Gerry, > Can you boot Dom0 with 2.6.32.10 under Xen 4.X on top of Ubuntu Lucid RC Server? > > Boris. >No, when I try to boot it as dom0 then I see errors about ''cannot locate IOAPIC for GSI 9'' and then the same ACPI_PSS object errors and then ACPI conflicts with PIIX4_SMBUS and finally something like ''cannot allocate MMIO region''. Then all I get is a blank screen. -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-Apr-24 18:07 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
Boris Derzhavets wrote:> I am pretty sure Yu Ke will ask you to obtain a serial log, when > problem will be escalated > to him. > > Boris. > > - >I don''t see a serial port on the board. ???? -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2010-Apr-24 18:18 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
There is serial (cable) via RJ45 ( Ethernet). Of course, if it''s not your expense. Boris. --- On Sat, 4/24/10, Gerry Reno <greno@verizon.net> wrote: From: Gerry Reno <greno@verizon.net> Subject: Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core To: xen-devel@lists.xensource.com Date: Saturday, April 24, 2010, 2:07 PM Boris Derzhavets wrote:> I am pretty sure Yu Ke will ask you to obtain a serial log, when > problem will be escalated > to him. > > Boris. > > - >I don''t see a serial port on the board. ???? -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-Apr-24 22:24 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
Boris Derzhavets wrote:> There is serial (cable) via RJ45 ( Ethernet). Of course, if it''s not > your expense. > > Boris. >Found a USB-USB null modem cable at usbgear.com but will kernel support this for serial console? -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2010-Apr-25 06:44 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
On Sat, Apr 24, 2010 at 06:24:05PM -0400, Gerry Reno wrote:> Boris Derzhavets wrote: >> There is serial (cable) via RJ45 ( Ethernet). Of course, if it''s not >> your expense. >> >> Boris. >> > Found a USB-USB null modem cable at usbgear.com but will kernel support > this for serial console? >http://wiki.xensource.com/xenwiki/XenSerialConsole -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-Apr-25 06:53 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
Gerry Reno wrote:> Boris Derzhavets wrote: >> There is serial (cable) via RJ45 ( Ethernet). Of course, if it''s >> not your expense. >> >> Boris. >> > Found a USB-USB null modem cable at usbgear.com but will kernel > support this for serial console? > > -GerryOk, without a serial port on this machine the best I can do is use a USB-Serial convertor which I realize will not provide BIOS or GRUB messages. To start with I changed the kernel boot line adding: console=ttyUSB0,115200n8 and I setup minicom on the other machine. At first minicom would only give me unreadable characters so I assumed a baud mismatch and began testing other rates. At 57600n8 in minicom I get this: AT+GCAP AT+GCAP AT+GCAP this is with both the standard lucid kernel and the pv_ops dom0 kernel using console=ttyUSB0,115200n8. Any ideas on how to get more output? And I don''t know how to configure xen line to add console or if usb serial console is even possible with xen. -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2010-Apr-25 10:22 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
On Sun, Apr 25, 2010 at 02:53:08AM -0400, Gerry Reno wrote:> Gerry Reno wrote: >> Boris Derzhavets wrote: >>> There is serial (cable) via RJ45 ( Ethernet). Of course, if it''s >>> not your expense. >>> >>> Boris. >>> >> Found a USB-USB null modem cable at usbgear.com but will kernel >> support this for serial console? >> >> -Gerry > Ok, without a serial port on this machine the best I can do is use a > USB-Serial convertor which I realize will not provide BIOS or GRUB > messages. To start with I changed the kernel boot line adding: > console=ttyUSB0,115200n8 and I setup minicom on the other machine. At > first minicom would only give me unreadable characters so I assumed a > baud mismatch and began testing other rates. At 57600n8 in minicom I > get this: > AT+GCAP > AT+GCAP > AT+GCAP > > this is with both the standard lucid kernel and the pv_ops dom0 kernel > using console=ttyUSB0,115200n8. Any ideas on how to get more output? > And I don''t know how to configure xen line to add console or if usb > serial console is even possible with xen. >http://wiki.xensource.com/xenwiki/XenSerialConsole USB serial is not possible as a serial console for Xen hypervisor. USB drivers are in dom0 linux kernel, so Xen boot messages cannot be sent to USB serial since linux is loaded only after Xen hypervisor. -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2010-Apr-25 11:16 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
Per Wiki:- 2) If your computer running Xen doesn''t have a real physical serial port you can add a PCI add-on serial card with a DB9 serial connector. This is a good option for many computers. seems to be the cheapest solution. No matter for AMD or Intel. Thanks Pasi once again. Boris. --- On Sun, 4/25/10, Pasi Kärkkäinen <pasik@iki.fi> wrote: From: Pasi Kärkkäinen <pasik@iki.fi> Subject: Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core To: "Gerry Reno" <greno@verizon.net> Cc: xen-devel@lists.xensource.com Date: Sunday, April 25, 2010, 2:44 AM On Sat, Apr 24, 2010 at 06:24:05PM -0400, Gerry Reno wrote:> Boris Derzhavets wrote: >> There is serial (cable) via RJ45 ( Ethernet). Of course, if it''s not >> your expense. >> >> Boris. >> > Found a USB-USB null modem cable at usbgear.com but will kernel support > this for serial console? >http://wiki.xensource.com/xenwiki/XenSerialConsole -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-Apr-25 15:37 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
Boris Derzhavets wrote:> Per Wiki:- > > 2) If your computer running Xen doesn''t have a real physical serial > port you can add a PCI add-on serial card with a DB9 serial connector. > This is a good option for many computers. > > seems to be the cheapest solution. No matter for AMD or Intel. > Thanks Pasi once again. > > Boris. > > > > - >I''ll check if there are any open slots and see if I can find an addon serial card. But besides that, the output from the kernel over ttyUSB0 still doesn''t look right. You should be able to get some kernel output I would think. -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2010-Apr-25 16:10 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
> You should be able to get some kernel output I would think.Yes, i have COM1 on both boards. No problems. Boris. --- On Sun, 4/25/10, Gerry Reno <greno@verizon.net> wrote: From: Gerry Reno <greno@verizon.net> Subject: Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core To: xen-devel@lists.xensource.com Date: Sunday, April 25, 2010, 11:37 AM Boris Derzhavets wrote:> Per Wiki:- > > 2) If your computer running Xen doesn''t have a real physical serial port you can add a PCI add-on serial card with a DB9 serial connector. This is a good option for many computers. > > seems to be the cheapest solution. No matter for AMD or Intel. > Thanks Pasi once again. > > Boris. > > > > - >I''ll check if there are any open slots and see if I can find an addon serial card. But besides that, the output from the kernel over ttyUSB0 still doesn''t look right. You should be able to get some kernel output I would think. -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-Apr-25 22:15 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
Gerry Reno wrote:> Boris Derzhavets wrote: >> Per Wiki:- >> >> 2) If your computer running Xen doesn''t have a real physical serial >> port you can add a PCI add-on serial card with a DB9 serial >> connector. This is a good option for many computers. >> >> seems to be the cheapest solution. No matter for AMD or Intel. >> Thanks Pasi once again. >> >> Boris. >> >> >> >> - >> > I''ll check if there are any open slots and see if I can find an addon > serial card.<snip> Well, I could not find even one local electronics/computer store that carried a serial port card. Had to order it online which will take some time. Maybe I can capture a video of the boot sequence. -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Mike Viau
2010-Apr-25 23:18 UTC
RE: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
> Sun, 25 Apr 2010 09:10:11 -0700 <bderzhavets@yahoo.com> wrote: >>But besides that, the output from the kernel over ttyUSB0 still doesn''t look right. You should be able to get some kernel output I would think.>Yes, i have COM1 on both boards. No problems.>Boris.Just to clarify, do you really use a ttyUSB0 (via an usb to serial adapter) and it works on you kernel command line to log messages or do just use your ttyUSB serial port (in dom0 for example) to console into your Linux machine? Thanks. -M --- On Sun, 4/25/10, Gerry Reno <greno@verizon.net> wrote: From: Gerry Reno <greno@verizon.net> Subject: Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core To: xen-devel@lists.xensource.com Date: Sunday, April 25, 2010, 11:37 AM Boris Derzhavets wrote:> Per Wiki:- > > 2) If your computer running Xen doesn''t have a real physical serial port you can add a PCI add-on serial card with a DB9 serial connector. This is a good option for many computers. > > seems to be the cheapest solution. No matter for AMD orIntel.> Thanks Pasi once again. > > Boris. > > > > - >I''ll check if there are any open slots and see if I can find an addon serial card. But besides that, the output from the kernel over ttyUSB0 still doesn''t look right. You should be able to get some kernel output I would think. -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _________________________________________________________________ Hotmail & Messenger are available on your phone. Try now. http://go.microsoft.com/?linkid=9724461 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-Apr-26 00:49 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
On 04/25/2010 07:18 PM, Mike Viau wrote:> > Sun, 25 Apr 2010 09:10:11 -0700 <bderzhavets@yahoo.com> wrote: > >>But besides that, the output from the kernel over ttyUSB0 still doesn''t look right. You should be able to get some kernel output I would think. > >Yes, i have COM1 on both boards. No problems. > > >Boris. > > Just to clarify, do you really use a ttyUSB0 (via an usb to serial > adapter) and it works on you kernel command line to log messages or do > just use your ttyUSB serial port (in dom0 for example) to console into > your Linux machine? > > Thanks. > > -M > >Not sure who you''re addressing, but yes I have a USB-Serial adapter and ttyUSB0 I have put on the kernel command line, BUT it isn''t working very well. All it shows in minicom right now is AT+GCAP AT+GCAP AT+GCAP when the system boots up. -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-Apr-26 02:10 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
On 04/25/2010 06:15 PM, Gerry Reno wrote:> Gerry Reno wrote: >> Boris Derzhavets wrote: >>> Per Wiki:- >>> >>> 2) If your computer running Xen doesn''t have a real physical serial >>> port you can add a PCI add-on serial card with a DB9 serial >>> connector. This is a good option for many computers. >>> >>> seems to be the cheapest solution. No matter for AMD or Intel. >>> Thanks Pasi once again. >>> >>> Boris. >>> >>> >>> >>> - >>> >> I''ll check if there are any open slots and see if I can find an addon >> serial card. > <snip> > > Well, I could not find even one local electronics/computer store that > carried a serial port card. Had to order it online which will take > some time. Maybe I can capture a video of the boot sequence. > > -Gerry >I tried to capture some video of the pv_ops dom0 2.6.32.10 boot sequence problem on Gigabyte AMD hardware and I posted it on youtube. Here''s the link: http://www.youtube.com/watch?v=OcuwH7S-qZA It was a little fuzzy before the upload but got real fuzzy afterwards. But I think you can make out the critical parts. -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Mike Viau
2010-Apr-26 02:10 UTC
RE: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
Sun, 25 Apr 2010 20:49:38 -0400 <greno@verizon.net> wrote:
On 04/25/2010 07:18 PM, Mike Viau wrote:
>
Sun, 25 Apr 2010 09:10:11 -0700 <bderzhavets@yahoo.com> wrote:
>>But besides that, the output from the kernel over ttyUSB0 still
doesn''t look right. You should be able to get some kernel output I
would think.
>Yes, i have COM1 on both boards. No problems.
>Boris.
Just to clarify, do you really use a ttyUSB0 (via an usb to serial
adapter) and it works on you kernel command line to log messages or do
just use your ttyUSB serial port (in dom0 for example) to console into
your Linux machine?
Thanks.
-M
Not sure who you''re addressing, but yes I have a USB-Serial adapter and
ttyUSB0 I have put on the kernel command line, BUT it isn''t working
very well. All it shows in minicom right now is
AT+GCAP
AT+GCAP
AT+GCAP
when the system boots up.
Not sure what the AT+GCAP messages are all about, but it may or may not have to
do with modem commands. See
http://http://en.wikipedia.org/wiki/Hayes_command_set
Has anyone ever successfully used a USB-Serial adapter and ttyUSB0 to work on
the kernel command line to get boot messages?
It seems to go against what the wiki @
http://wiki.xensource.com/xenwiki/XenSerialConsole
[quote]
USB serial adapter doesn''t work for the computer running Xen (*), but
it
works for the other computer that is only used to view and log the
serial console.
[/quote]
-M
_________________________________________________________________
Videos that have everyone talking! Now also in HD!
http://go.microsoft.com/?linkid=9724465
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Gerry Reno
2010-Apr-26 02:18 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
On 04/25/2010 10:10 PM, Mike Viau wrote:> Sun, 25 Apr 2010 20:49:38 -0400 <greno@verizon.net> wrote: > > On 04/25/2010 07:18 PM, Mike Viau wrote: > > > Sun, 25 Apr 2010 09:10:11 -0700 <bderzhavets@yahoo.com> > <mailto:bderzhavets@yahoo.com> wrote: > > >>But besides that, the output from the kernel over ttyUSB0 still doesn''t look right. You should be able to get some kernel output I would think. > > >Yes, i have COM1 on both boards. No problems. > > >Boris. > > Just to clarify, do you really use a ttyUSB0 (via an usb to serial > adapter) and it works on you kernel command line to log messages > or do just use your ttyUSB serial port (in dom0 for example) to > console into your Linux machine? > > Thanks. > > -M > > > Not sure who you''re addressing, but yes I have a USB-Serial > adapter and ttyUSB0 I have put on the kernel command line, BUT it > isn''t working very well. All it shows in minicom right now is > AT+GCAP > AT+GCAP > AT+GCAP > when the system boots up. > > Not sure what the AT+GCAP messages are all about, but it may or may > not have to do with modem commands. See > http://http://en.wikipedia.org/wiki/Hayes_command_set > <http://http//en.wikipedia.org/wiki/Hayes_command_set> > > Has anyone ever successfully used a USB-Serial adapter and ttyUSB0 to > work on the kernel command line to get boot messages? > > It seems to go against what the wiki @ > http://wiki.xensource.com/xenwiki/XenSerialConsole > > [quote] > USB serial adapter doesn''t work for the computer running Xen (*), but > it works for the other computer that is only used to view and log the > serial console. > [/quote] > > > -MThat''s referring to the Xen kernel not the linux kernel. At some point USB-Serial may have to be supported by Linux kernel as well as Xen hypervisor kernel if 16550 cards get scarce. -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-Apr-26 04:12 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
On 04/25/2010 10:10 PM, Gerry Reno wrote:> On 04/25/2010 06:15 PM, Gerry Reno wrote: >> Gerry Reno wrote: >>> Boris Derzhavets wrote: >>>> Per Wiki:- >>>> >>>> 2) If your computer running Xen doesn''t have a real physical serial >>>> port you can add a PCI add-on serial card with a DB9 serial >>>> connector. This is a good option for many computers. >>>> >>>> seems to be the cheapest solution. No matter for AMD or Intel. >>>> Thanks Pasi once again. >>>> >>>> Boris. >>>> >>>> >>>> >>>> - >>>> >>> I''ll check if there are any open slots and see if I can find an >>> addon serial card. >> <snip> >> >> Well, I could not find even one local electronics/computer store that >> carried a serial port card. Had to order it online which will take >> some time. Maybe I can capture a video of the boot sequence. >> >> -Gerry >> > I tried to capture some video of the pv_ops dom0 2.6.32.10 boot > sequence problem on Gigabyte AMD hardware and I posted it on youtube. > Here''s the link: http://www.youtube.com/watch?v=OcuwH7S-qZA > It was a little fuzzy before the upload but got real fuzzy > afterwards. But I think you can make out the critical parts. > > -GerryI uploaded another take and it came out a little better: http://www.youtube.com/watch?v=n7fW7yjrIEM -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2010-Apr-26 20:04 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
On Mon, Apr 26, 2010 at 12:12:13AM -0400, Gerry Reno wrote:> On 04/25/2010 10:10 PM, Gerry Reno wrote: >> On 04/25/2010 06:15 PM, Gerry Reno wrote: >>> Gerry Reno wrote: >>>> Boris Derzhavets wrote: >>>>> Per Wiki:- >>>>> >>>>> 2) If your computer running Xen doesn''t have a real physical >>>>> serial port you can add a PCI add-on serial card with a DB9 >>>>> serial connector. This is a good option for many computers. >>>>> >>>>> seems to be the cheapest solution. No matter for AMD or Intel. >>>>> Thanks Pasi once again. >>>>> >>>>> Boris. >>>>> >>>>> >>>>> >>>>> - >>>>> >>>> I''ll check if there are any open slots and see if I can find an >>>> addon serial card. >>> <snip> >>> >>> Well, I could not find even one local electronics/computer store that >>> carried a serial port card. Had to order it online which will take >>> some time. Maybe I can capture a video of the boot sequence. >>> >>> -Gerry >>> >> I tried to capture some video of the pv_ops dom0 2.6.32.10 boot >> sequence problem on Gigabyte AMD hardware and I posted it on youtube. >> Here''s the link: http://www.youtube.com/watch?v=OcuwH7S-qZA >> It was a little fuzzy before the upload but got real fuzzy afterwards. >> But I think you can make out the critical parts. >> >> -Gerry > > I uploaded another take and it came out a little better: > http://www.youtube.com/watch?v=n7fW7yjrIEM >You seem to be missing most of the dom0 linux kernel boot messages.. Please paste your grub.conf. -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-Apr-26 21:26 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
On 04/26/2010 04:04 PM, Pasi Kärkkäinen wrote:> On Mon, Apr 26, 2010 at 12:12:13AM -0400, Gerry Reno wrote: >> On 04/25/2010 10:10 PM, Gerry Reno wrote: >>> On 04/25/2010 06:15 PM, Gerry Reno wrote: >>>> Gerry Reno wrote: >>>>> Boris Derzhavets wrote: >>>>>> Per Wiki:- >>>>>> >>>>>> 2) If your computer running Xen doesn''t have a real physical >>>>>> serial port you can add a PCI add-on serial card with a DB9 >>>>>> serial connector. This is a good option for many computers. >>>>>> >>>>>> seems to be the cheapest solution. No matter for AMD or Intel. >>>>>> Thanks Pasi once again. >>>>>> >>>>>> Boris. >>>>>> >>>>>> >>>>>> >>>>>> - >>>>>> >>>>> I''ll check if there are any open slots and see if I can find an >>>>> addon serial card. >>>> <snip> >>>> >>>> Well, I could not find even one local electronics/computer store that >>>> carried a serial port card. Had to order it online which will take >>>> some time. Maybe I can capture a video of the boot sequence. >>>> >>>> -Gerry >>>> >>> I tried to capture some video of the pv_ops dom0 2.6.32.10 boot >>> sequence problem on Gigabyte AMD hardware and I posted it on youtube. >>> Here''s the link: http://www.youtube.com/watch?v=OcuwH7S-qZA >>> It was a little fuzzy before the upload but got real fuzzy afterwards. >>> But I think you can make out the critical parts. >>> >>> -Gerry >> >> I uploaded another take and it came out a little better: >> http://www.youtube.com/watch?v=n7fW7yjrIEM >> > > You seem to be missing most of the dom0 linux kernel boot messages.. > > Please paste your grub.conf. > > -- Pasi > >Pasi, my grub.conf is attached. -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2010-Apr-26 21:52 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
On Mon, Apr 26, 2010 at 05:26:54PM -0400, Gerry Reno wrote:> On 04/26/2010 04:04 PM, Pasi Kärkkäinen wrote: >> On Mon, Apr 26, 2010 at 12:12:13AM -0400, Gerry Reno wrote: >>> On 04/25/2010 10:10 PM, Gerry Reno wrote: >>>> On 04/25/2010 06:15 PM, Gerry Reno wrote: >>>>> Gerry Reno wrote: >>>>>> Boris Derzhavets wrote: >>>>>>> Per Wiki:- >>>>>>> >>>>>>> 2) If your computer running Xen doesn''t have a real physical >>>>>>> serial port you can add a PCI add-on serial card with a DB9 >>>>>>> serial connector. This is a good option for many computers. >>>>>>> >>>>>>> seems to be the cheapest solution. No matter for AMD or Intel. >>>>>>> Thanks Pasi once again. >>>>>>> >>>>>>> Boris. >>>>>>> >>>>>>> >>>>>>> >>>>>>> - >>>>>>> >>>>>> I''ll check if there are any open slots and see if I can find an >>>>>> addon serial card. >>>>> <snip> >>>>> >>>>> Well, I could not find even one local electronics/computer store that >>>>> carried a serial port card. Had to order it online which will take >>>>> some time. Maybe I can capture a video of the boot sequence. >>>>> >>>>> -Gerry >>>>> >>>> I tried to capture some video of the pv_ops dom0 2.6.32.10 boot >>>> sequence problem on Gigabyte AMD hardware and I posted it on youtube. >>>> Here''s the link: http://www.youtube.com/watch?v=OcuwH7S-qZA >>>> It was a little fuzzy before the upload but got real fuzzy afterwards. >>>> But I think you can make out the critical parts. >>>> >>>> -Gerry >>> >>> I uploaded another take and it came out a little better: >>> http://www.youtube.com/watch?v=n7fW7yjrIEM >>> >> >> You seem to be missing most of the dom0 linux kernel boot messages.. >> >> Please paste your grub.conf. >> >> -- Pasi >> >> > Pasi, my grub.conf is attached. >Ok, fix it to be like this: module /vmlinuz-2.6.32.10 root=/dev/mapper/vg--grp--01--23--02--2-LogVol00 dummy=dummy ro earlyprintk=xen console=hvc0 console=ttyS0 console=ttyUSB0,115200n8 text aka remove "quiet" and add "earlyprintk=xen console=hvc0" -- Pasi> -Gerry >> # grub.conf generated by anaconda > # > # Note that you do not have to rerun grub after making changes to this file > # NOTICE: You have a /boot partition. This means that > # all kernel and initrd paths are relative to /boot/, eg. > # root (hd0,0) > # kernel /vmlinuz-version ro root=/dev/VolGroup01/LogVol00 > # initrd /initrd-version.img > #boot=/dev/md0 > default=4 > timeout=5 > splashimage=(hd0,0)/grub/splash.xpm.gz > hiddenmenu > title Ubuntu UEC-Node kernel 2.6.31.6 > root (hd4,0) > kernel /vmlinuz-2.6.31.6 root=/dev/mapper/vg--grp--01--23--02--2-LogVol00 ro quiet console=tty0 console=ttyS0 text > module /initrd.img-2.6.31.6 > title Ubuntu UEC-Node kernel 2.6.31.6 (pv_ops dom0) > root (hd4,0) > kernel /xen-3.4.2.gz dummy=dummy dom0_mem=1024M vga=text-80x50 loglvl=all guest_loglvl=all > module /vmlinuz-2.6.32.10 root=/dev/mapper/vg--grp--01--23--02--2-LogVol00 dummy=dummy ro quiet console=tty0 console=ttyS0 text > module /initrd.img-2.6.32.10 > title Ubuntu UEC-Node kernel 2.6.32.10 > root (hd4,0) > kernel /vmlinuz-2.6.32.10 root=/dev/mapper/vg--grp--01--23--02--2-LogVol00 vga=ext ro quiet splash console=ttyUSB0,115200n8 text idle=nomwait > initrd /initrd.img-2.6.32.10 > title Ubuntu UEC-Node kernel 2.6.32.10 (pv_ops dom0) > root (hd4,0) > kernel /xen-4.0.0-rc8.gz dummy=dummy dom0_mem=1024M vga=text-80x50 loglvl=all guest_loglvl=all > module /vmlinuz-2.6.32.10 root=/dev/mapper/vg--grp--01--23--02--2-LogVol00 dummy=dummy ro quiet console=tty0 console=ttyS0 console=ttyUSB0,115200n8 text > module /initrd.img-2.6.32.10 > title Ubuntu UEC-Node (Lucid Lynx) 2.6.32-21 > root (hd4,0) > kernel /vmlinuz-2.6.32-21-server root=/dev/mapper/vg--grp--01--23--02--2-LogVol00 ro quiet splash console=ttyS0 console=ttyUSB0,115200n8 > initrd /initrd.img-2.6.32-21-server > >> _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-Apr-26 23:36 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
On 04/26/2010 05:52 PM, Pasi Kärkkäinen wrote:> On Mon, Apr 26, 2010 at 05:26:54PM -0400, Gerry Reno wrote: > >> On 04/26/2010 04:04 PM, Pasi Kärkkäinen wrote: >> >>> On Mon, Apr 26, 2010 at 12:12:13AM -0400, Gerry Reno wrote: >>> >>>> On 04/25/2010 10:10 PM, Gerry Reno wrote: >>>> >>>>> On 04/25/2010 06:15 PM, Gerry Reno wrote: >>>>> >>>>>> Gerry Reno wrote: >>>>>> >>>>>>> Boris Derzhavets wrote: >>>>>>> >>>>>>>> Per Wiki:- >>>>>>>> >>>>>>>> 2) If your computer running Xen doesn''t have a real physical >>>>>>>> serial port you can add a PCI add-on serial card with a DB9 >>>>>>>> serial connector. This is a good option for many computers. >>>>>>>> >>>>>>>> seems to be the cheapest solution. No matter for AMD or Intel. >>>>>>>> Thanks Pasi once again. >>>>>>>> >>>>>>>> Boris. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> - >>>>>>>> >>>>>>>> >>>>>>> I''ll check if there are any open slots and see if I can find an >>>>>>> addon serial card. >>>>>>> >>>>>> <snip> >>>>>> >>>>>> Well, I could not find even one local electronics/computer store that >>>>>> carried a serial port card. Had to order it online which will take >>>>>> some time. Maybe I can capture a video of the boot sequence. >>>>>> >>>>>> -Gerry >>>>>> >>>>>> >>>>> I tried to capture some video of the pv_ops dom0 2.6.32.10 boot >>>>> sequence problem on Gigabyte AMD hardware and I posted it on youtube. >>>>> Here''s the link: http://www.youtube.com/watch?v=OcuwH7S-qZA >>>>> It was a little fuzzy before the upload but got real fuzzy afterwards. >>>>> But I think you can make out the critical parts. >>>>> >>>>> -Gerry >>>>> >>>> I uploaded another take and it came out a little better: >>>> http://www.youtube.com/watch?v=n7fW7yjrIEM >>>> >>>> >>> You seem to be missing most of the dom0 linux kernel boot messages.. >>> >>> Please paste your grub.conf. >>> >>> -- Pasi >>> >>> >>> >> Pasi, my grub.conf is attached. >> >> > Ok, fix it to be like this: > > module /vmlinuz-2.6.32.10 root=/dev/mapper/vg--grp--01--23--02--2-LogVol00 dummy=dummy ro earlyprintk=xen console=hvc0 console=ttyS0 console=ttyUSB0,115200n8 text > > aka remove "quiet" and add "earlyprintk=xen console=hvc0" > > -- Pasi > >Pasi, this gave some more output. Sorry the video is fuzzy but this happens by youtube postprocessing. Here is new link: http://www.youtube.com/watch?v=jePyapeHpSI -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-Apr-27 00:00 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
On 04/26/2010 07:36 PM, Gerry Reno wrote:> On 04/26/2010 05:52 PM, Pasi Kärkkäinen wrote: >> On Mon, Apr 26, 2010 at 05:26:54PM -0400, Gerry Reno wrote: >>> On 04/26/2010 04:04 PM, Pasi Kärkkäinen wrote: >>>> On Mon, Apr 26, 2010 at 12:12:13AM -0400, Gerry Reno wrote: >>>>> On 04/25/2010 10:10 PM, Gerry Reno wrote: >>>>>> On 04/25/2010 06:15 PM, Gerry Reno wrote: >>>>>>> Gerry Reno wrote: >>>>>>>> Boris Derzhavets wrote: >>>>>>>>> Per Wiki:- >>>>>>>>> >>>>>>>>> 2) If your computer running Xen doesn''t have a real physical >>>>>>>>> serial port you can add a PCI add-on serial card with a DB9 >>>>>>>>> serial connector. This is a good option for many computers. >>>>>>>>> >>>>>>>>> seems to be the cheapest solution. No matter for AMD or Intel. >>>>>>>>> Thanks Pasi once again. >>>>>>>>> >>>>>>>>> Boris. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> - >>>>>>>>> >>>>>>>> I''ll check if there are any open slots and see if I can find an >>>>>>>> addon serial card. >>>>>>> <snip> >>>>>>> >>>>>>> Well, I could not find even one local electronics/computer store >>>>>>> that >>>>>>> carried a serial port card. Had to order it online which will take >>>>>>> some time. Maybe I can capture a video of the boot sequence. >>>>>>> >>>>>>> -Gerry >>>>>>> >>>>>> I tried to capture some video of the pv_ops dom0 2.6.32.10 boot >>>>>> sequence problem on Gigabyte AMD hardware and I posted it on >>>>>> youtube. >>>>>> Here''s the link: http://www.youtube.com/watch?v=OcuwH7S-qZA >>>>>> It was a little fuzzy before the upload but got real fuzzy >>>>>> afterwards. >>>>>> But I think you can make out the critical parts. >>>>>> >>>>>> -Gerry >>>>> I uploaded another take and it came out a little better: >>>>> http://www.youtube.com/watch?v=n7fW7yjrIEM >>>>> >>>> You seem to be missing most of the dom0 linux kernel boot messages.. >>>> >>>> Please paste your grub.conf. >>>> >>>> -- Pasi >>>> >>>> >>> Pasi, my grub.conf is attached. >>> >> Ok, fix it to be like this: >> >> module /vmlinuz-2.6.32.10 >> root=/dev/mapper/vg--grp--01--23--02--2-LogVol00 dummy=dummy ro >> earlyprintk=xen console=hvc0 console=ttyS0 console=ttyUSB0,115200n8 text >> >> aka remove "quiet" and add "earlyprintk=xen console=hvc0" >> >> -- Pasi >> > > Pasi, this gave some more output. Sorry the video is fuzzy but this > happens by youtube postprocessing. Here is new link: > http://www.youtube.com/watch?v=jePyapeHpSI > > -GerryIf you have somewhere I can ftp original video file, it is clearer. File is about 90 MB. -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-Apr-27 02:48 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
On 04/26/2010 08:00 PM, Gerry Reno wrote:> On 04/26/2010 07:36 PM, Gerry Reno wrote: >> On 04/26/2010 05:52 PM, Pasi Kärkkäinen wrote: >>> On Mon, Apr 26, 2010 at 05:26:54PM -0400, Gerry Reno wrote: >>>> On 04/26/2010 04:04 PM, Pasi Kärkkäinen wrote: >>>>> On Mon, Apr 26, 2010 at 12:12:13AM -0400, Gerry Reno wrote: >>>>>> On 04/25/2010 10:10 PM, Gerry Reno wrote: >>>>>>> On 04/25/2010 06:15 PM, Gerry Reno wrote: >>>>>>>> Gerry Reno wrote: >>>>>>>>> Boris Derzhavets wrote: >>>>>>>>>> Per Wiki:- >>>>>>>>>> >>>>>>>>>> 2) If your computer running Xen doesn''t have a real physical >>>>>>>>>> serial port you can add a PCI add-on serial card with a DB9 >>>>>>>>>> serial connector. This is a good option for many computers. >>>>>>>>>> >>>>>>>>>> seems to be the cheapest solution. No matter for AMD or Intel. >>>>>>>>>> Thanks Pasi once again. >>>>>>>>>> >>>>>>>>>> Boris. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> - >>>>>>>>>> >>>>>>>>> I''ll check if there are any open slots and see if I can find an >>>>>>>>> addon serial card. >>>>>>>> <snip> >>>>>>>> >>>>>>>> Well, I could not find even one local electronics/computer >>>>>>>> store that >>>>>>>> carried a serial port card. Had to order it online which will >>>>>>>> take >>>>>>>> some time. Maybe I can capture a video of the boot sequence. >>>>>>>> >>>>>>>> -Gerry >>>>>>>> >>>>>>> I tried to capture some video of the pv_ops dom0 2.6.32.10 boot >>>>>>> sequence problem on Gigabyte AMD hardware and I posted it on >>>>>>> youtube. >>>>>>> Here''s the link: http://www.youtube.com/watch?v=OcuwH7S-qZA >>>>>>> It was a little fuzzy before the upload but got real fuzzy >>>>>>> afterwards. >>>>>>> But I think you can make out the critical parts. >>>>>>> >>>>>>> -Gerry >>>>>> I uploaded another take and it came out a little better: >>>>>> http://www.youtube.com/watch?v=n7fW7yjrIEM >>>>>> >>>>> You seem to be missing most of the dom0 linux kernel boot messages.. >>>>> >>>>> Please paste your grub.conf. >>>>> >>>>> -- Pasi >>>>> >>>>> >>>> Pasi, my grub.conf is attached. >>>> >>> Ok, fix it to be like this: >>> >>> module /vmlinuz-2.6.32.10 >>> root=/dev/mapper/vg--grp--01--23--02--2-LogVol00 dummy=dummy ro >>> earlyprintk=xen console=hvc0 console=ttyS0 console=ttyUSB0,115200n8 >>> text >>> >>> aka remove "quiet" and add "earlyprintk=xen console=hvc0" >>> >>> -- Pasi >>> >> >> Pasi, this gave some more output. Sorry the video is fuzzy but this >> happens by youtube postprocessing. Here is new link: >> http://www.youtube.com/watch?v=jePyapeHpSI >> >> -Gerry > If you have somewhere I can ftp original video file, it is clearer. > File is about 90 MB. > > -Gerry >Original video is posted here: http://greno-misc.googlecode.com/files/MOV03932.MPG -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2010-Apr-27 09:15 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
On Mon, Apr 26, 2010 at 10:48:44PM -0400, Gerry Reno wrote:>>>>>> >>>>> Pasi, my grub.conf is attached. >>>>> >>>> Ok, fix it to be like this: >>>> >>>> module /vmlinuz-2.6.32.10 >>>> root=/dev/mapper/vg--grp--01--23--02--2-LogVol00 dummy=dummy ro >>>> earlyprintk=xen console=hvc0 console=ttyS0 console=ttyUSB0,115200n8 >>>> text >>>> >>>> aka remove "quiet" and add "earlyprintk=xen console=hvc0" >>>> >>>> -- Pasi >>>> >>> >>> Pasi, this gave some more output. Sorry the video is fuzzy but this >>> happens by youtube postprocessing. Here is new link: >>> http://www.youtube.com/watch?v=jePyapeHpSI >>> >>> -Gerry >> If you have somewhere I can ftp original video file, it is clearer. >> File is about 90 MB. >> >> -Gerry >> > Original video is posted here: > http://greno-misc.googlecode.com/files/MOV03932.MPG >It''s very difficult to see the problem from that video :( We''d really need a serial console log. Also you I wonder why the screen goes blank in the end? Before that it seems to mount the root (?) filesystem OK.. Do you have some console font/videomode thingie configured? See the "Dom0 console gets all weird and corrupted in the end of the boot process" from: http://wiki.xensource.com/xenwiki/XenParavirtOps Also please add "nomodeset" option to the end of the pvops kernel boot options, like suggested on pvops examples/docs. -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-Apr-27 17:35 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
On 04/27/2010 05:15 AM, Pasi Kärkkäinen wrote:> On Mon, Apr 26, 2010 at 10:48:44PM -0400, Gerry Reno wrote: > >>>>>>> >>>>>> Pasi, my grub.conf is attached. >>>>>> >>>>>> >>>>> Ok, fix it to be like this: >>>>> >>>>> module /vmlinuz-2.6.32.10 >>>>> root=/dev/mapper/vg--grp--01--23--02--2-LogVol00 dummy=dummy ro >>>>> earlyprintk=xen console=hvc0 console=ttyS0 console=ttyUSB0,115200n8 >>>>> text >>>>> >>>>> aka remove "quiet" and add "earlyprintk=xen console=hvc0" >>>>> >>>>> -- Pasi >>>>> >>>>> >>>> Pasi, this gave some more output. Sorry the video is fuzzy but this >>>> happens by youtube postprocessing. Here is new link: >>>> http://www.youtube.com/watch?v=jePyapeHpSI >>>> >>>> -Gerry >>>> >>> If you have somewhere I can ftp original video file, it is clearer. >>> File is about 90 MB. >>> >>> -Gerry >>> >>> >> Original video is posted here: >> http://greno-misc.googlecode.com/files/MOV03932.MPG >> >> > It''s very difficult to see the problem from that video :( > We''d really need a serial console log. > > Also you I wonder why the screen goes blank in the end? > Before that it seems to mount the root (?) filesystem OK.. > > Do you have some console font/videomode thingie configured? > See the "Dom0 console gets all weird and corrupted in the end of the boot process" from: > http://wiki.xensource.com/xenwiki/XenParavirtOps > > Also please add "nomodeset" option to the end of the pvops kernel boot options, > like suggested on pvops examples/docs. > > -- Pasi > >Ok, I finally got a little more output using nomodeset. There is a soft lockup bug. Attaching screenshots. -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-Apr-29 13:54 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
On 04/27/2010 01:35 PM, Gerry Reno wrote:> On 04/27/2010 05:15 AM, Pasi Kärkkäinen wrote: >> On Mon, Apr 26, 2010 at 10:48:44PM -0400, Gerry Reno wrote: >>>>>>> Pasi, my grub.conf is attached. >>>>>>> >>>>>> Ok, fix it to be like this: >>>>>> >>>>>> module /vmlinuz-2.6.32.10 >>>>>> root=/dev/mapper/vg--grp--01--23--02--2-LogVol00 dummy=dummy ro >>>>>> earlyprintk=xen console=hvc0 console=ttyS0 console=ttyUSB0,115200n8 >>>>>> text >>>>>> >>>>>> aka remove "quiet" and add "earlyprintk=xen console=hvc0" >>>>>> >>>>>> -- Pasi >>>>>> >>>>> Pasi, this gave some more output. Sorry the video is fuzzy but this >>>>> happens by youtube postprocessing. Here is new link: >>>>> http://www.youtube.com/watch?v=jePyapeHpSI >>>>> >>>>> -Gerry >>>> If you have somewhere I can ftp original video file, it is clearer. >>>> File is about 90 MB. >>>> >>>> -Gerry >>>> >>> Original video is posted here: >>> http://greno-misc.googlecode.com/files/MOV03932.MPG >>> >> It''s very difficult to see the problem from that video :( >> We''d really need a serial console log. >> >> Also you I wonder why the screen goes blank in the end? >> Before that it seems to mount the root (?) filesystem OK.. >> >> Do you have some console font/videomode thingie configured? >> See the "Dom0 console gets all weird and corrupted in the end of the >> boot process" from: >> http://wiki.xensource.com/xenwiki/XenParavirtOps >> >> Also please add "nomodeset" option to the end of the pvops kernel >> boot options, >> like suggested on pvops examples/docs. >> >> -- Pasi >> > Ok, I finally got a little more output using nomodeset. There is a > soft lockup bug. Attaching screenshots. > > -Gerry >I''ve been changing various settings trying to figure out what is the problem and today after a very long wait (> 5 min) I was able to see a login prompt. But things are not well. During the boot I now see: XENBUS: Unable to read cpu state. XENBUS: Unable to read cpu state. XENBUS: Unable to read cpu state. XENBUS: Unable to read cpu state. and while logged in I get a lot of these type of messages every few minutes: INFO: task xxxxxxx:nnn blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. and I notice a number of errors in the xen logs with I''m attaching. Can someone look at these logs and see if there is anything I can do on my end to help fix the problem? -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Mike Viau
2010-Apr-29 14:41 UTC
RE: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
> Thu, 29 Apr 2010 09:54:07 -0400 <greno@verizon.net> wrote: on AMD quad-core > > On 04/27/2010 01:35 PM, Gerry Reno wrote: > > On 04/27/2010 05:15 AM, Pasi Kärkkäinen wrote: > >> On Mon, Apr 26, 2010 at 10:48:44PM -0400, Gerry Reno wrote: > >>>>>>> Pasi, my grub.conf is attached. > >>>>>>> > >>>>>> Ok, fix it to be like this: > >>>>>> > >>>>>> module /vmlinuz-2.6.32.10 > >>>>>> root=/dev/mapper/vg--grp--01--23--02--2-LogVol00 dummy=dummy ro > >>>>>> earlyprintk=xen console=hvc0 console=ttyS0 console=ttyUSB0,115200n8 > >>>>>> text > >>>>>> > >>>>>> aka remove "quiet" and add "earlyprintk=xen console=hvc0" > >>>>>> > >>>>>> -- Pasi > >>>>>> > >>>>> Pasi, this gave some more output. Sorry the video is fuzzy but this > >>>>> happens by youtube postprocessing. Here is new link: > >>>>> http://www.youtube.com/watch?v=jePyapeHpSI > >>>>> > >>>>> -Gerry > >>>> If you have somewhere I can ftp original video file, it is clearer. > >>>> File is about 90 MB. > >>>> > >>>> -Gerry > >>>> > >>> Original video is posted here: > >>> http://greno-misc.googlecode.com/files/MOV03932.MPG > >>> > >> It''s very difficult to see the problem from that video :( > >> We''d really need a serial console log. > >> > >> Also you I wonder why the screen goes blank in the end? > >> Before that it seems to mount the root (?) filesystem OK.. > >> > >> Do you have some console font/videomode thingie configured? > >> See the "Dom0 console gets all weird and corrupted in the end of the > >> boot process" from: > >> http://wiki.xensource.com/xenwiki/XenParavirtOps > >> > >> Also please add "nomodeset" option to the end of the pvops kernel > >> boot options, > >> like suggested on pvops examples/docs. > >> > >> -- Pasi > >> > > Ok, I finally got a little more output using nomodeset. There is a > > soft lockup bug. Attaching screenshots. > > > > -Gerry > > > > I''ve been changing various settings trying to figure out what is the > problem and today after a very long wait (> 5 min) I was able to see a > login prompt. But things are not well. During the boot I now see: > XENBUS: Unable to read cpu state. > XENBUS: Unable to read cpu state. > XENBUS: Unable to read cpu state. > XENBUS: Unable to read cpu state. >I get these message on boot too (note there is not long delay to get these messages but they do appear closer to the end of my boot up sequence). FYI, it has not affected XEN for as far as I could see.> and while logged in I get a lot of these type of messages every few minutes: > INFO: task xxxxxxx:nnn blocked for more than 120 seconds. > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > > and I notice a number of errors in the xen logs with I''m attaching. > > Can someone look at these logs and see if there is anything I can do on > my end to help fix the problem? > > -Gerry > > >_________________________________________________________________ Live connected. Get Hotmail & Messenger on your phone. http://go.microsoft.com/?linkid=9724462 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-Apr-29 14:46 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
On 04/29/2010 10:41 AM, Mike Viau wrote:> > Thu, 29 Apr 2010 09:54:07 -0400 <greno@verizon.net> wrote: on AMD > quad-core > > > > On 04/27/2010 01:35 PM, Gerry Reno wrote: > > > On 04/27/2010 05:15 AM, Pasi Kärkkäinen wrote: > > >> On Mon, Apr 26, 2010 at 10:48:44PM -0400, Gerry Reno wrote: > > >>>>>>> Pasi, my grub.conf is attached. > > >>>>>>> > > >>>>>> Ok, fix it to be like this: > > >>>>>> > > >>>>>> module /vmlinuz-2.6.32.10 > > >>>>>> root=/dev/mapper/vg--grp--01--23--02--2-LogVol00 dummy=dummy ro > > >>>>>> earlyprintk=xen console=hvc0 console=ttyS0 > console=ttyUSB0,115200n8 > > >>>>>> text > > >>>>>> > > >>>>>> aka remove "quiet" and add "earlyprintk=xen console=hvc0" > > >>>>>> > > >>>>>> -- Pasi > > >>>>>> > > >>>>> Pasi, this gave some more output. Sorry the video is fuzzy but > this > > >>>>> happens by youtube postprocessing. Here is new link: > > >>>>> http://www.youtube.com/watch?v=jePyapeHpSI > > >>>>> > > >>>>> -Gerry > > >>>> If you have somewhere I can ftp original video file, it is clearer. > > >>>> File is about 90 MB. > > >>>> > > >>>> -Gerry > > >>>> > > >>> Original video is posted here: > > >>> http://greno-misc.googlecode.com/files/MOV03932.MPG > > >>> > > >> It''s very difficult to see the problem from that video :( > > >> We''d really need a serial console log. > > >> > > >> Also you I wonder why the screen goes blank in the end? > > >> Before that it seems to mount the root (?) filesystem OK.. > > >> > > >> Do you have some console font/videomode thingie configured? > > >> See the "Dom0 console gets all weird and corrupted in the end of the > > >> boot process" from: > > >> http://wiki.xensource.com/xenwiki/XenParavirtOps > > >> > > >> Also please add "nomodeset" option to the end of the pvops kernel > > >> boot options, > > >> like suggested on pvops examples/docs. > > >> > > >> -- Pasi > > >> > > > Ok, I finally got a little more output using nomodeset. There is a > > > soft lockup bug. Attaching screenshots. > > > > > > -Gerry > > > > > > > I''ve been changing various settings trying to figure out what is the > > problem and today after a very long wait (> 5 min) I was able to see a > > login prompt. But things are not well. During the boot I now see: > > XENBUS: Unable to read cpu state. > > XENBUS: Unable to read cpu state. > > XENBUS: Unable to read cpu state. > > XENBUS: Unable to read cpu state. > > > > I get these message on boot too (note there is not long delay to get > these messages but they do appear closer to the end of my boot up > sequence). FYI, it has not affected XEN for as far as I could see. > > > > and while logged in I get a lot of these type of messages every few > minutes: > > INFO: task xxxxxxx:nnn blocked for more than 120 seconds. > > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this > message. > > > > and I notice a number of errors in the xen logs with I''m attaching. > > > > Can someone look at these logs and see if there is anything I can do on > > my end to help fix the problem? > > > > -Gerry > >Mike, what processor are you running on? -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Mike Viau
2010-Apr-29 15:11 UTC
RE: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
Thu, 29 Apr 2010 10:46:51 -0400 <greno@verizon.net> wrote:>> I''ve been changing various settings trying to figure out what isthe>> problem and today after a very long wait (> 5 min) I was ableto see a>> login prompt. But things are not well. During the boot I now see:>> XENBUS: Unable to read cpu state.>> XENBUS: Unable to read cpu state.>> XENBUS: Unable to read cpu state.>> XENBUS: Unable to read cpu state.>>> I get these message on boot too (note there is not long delay to getthese messages but they do appear closer to the end of my boot up sequence). FYI, it has not affected XEN for as far as I could see. Mike, what processor are you running on? A fairly recent Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 30 model name : Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz stepping : 5 cpu MHz : 2800.132 cache size : 8192 KB fpu : yes fpu_exception : yes cpuid level : 11 wp : yes flags : fpu de tsc msr pae cx8 apic sep mtrr cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc rep_good nonstop_tsc aperfmperf pni est ssse3 cx16 sse4_1 sse4_2 popcnt hypervisor lahf_lm ida bogomips : 5600.26 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: _________________________________________________________________ Hotmail & Messenger. Get them on your phone now. http://go.microsoft.com/?linkid=9724463 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-Apr-29 16:50 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
On 04/29/2010 11:11 AM, Mike Viau wrote:> Thu, 29 Apr 2010 10:46:51 -0400 <greno@verizon.net> wrote: > > >> I''ve been changing various settings trying to figure out what > is the > >> problem and today after a very long wait (> 5 min) I was able > to see a > >> login prompt. But things are not well. During the boot I now see: > >> XENBUS: Unable to read cpu state. > >> XENBUS: Unable to read cpu state. > >> XENBUS: Unable to read cpu state. > >> XENBUS: Unable to read cpu state. > >> > > > I get these message on boot too (note there is not long delay to > get these messages but they do appear closer to the end of my boot > up sequence). FYI, it has not affected XEN for as far as I could see. > > Mike, what processor are you running on? > > > > A fairly recent Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz > > processor : 0 > vendor_id : GenuineIntel > cpu family : 6 > model : 30 > model name : Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz > stepping : 5 > cpu MHz : 2800.132 > cache size : 8192 KB > fpu : yes > fpu_exception : yes > cpuid level : 11 > wp : yes > flags : fpu de tsc msr pae cx8 apic sep mtrr cmov pat > clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc > rep_good nonstop_tsc aperfmperf pni est ssse3 cx16 sse4_1 sse4_2 > popcnt hypervisor lahf_lm ida > bogomips : 5600.26 > clflush size : 64 > cache_alignment : 64 > address sizes : 36 bits physical, 48 bits virtual > power management: > > >Intel processors do not seem to have the same problem for some reason. I did see though a large number of "soft lockup" bugs reported for Lucid Lynx recently (2.6.32-21). The problem I''m seeing is just with the latest pv_ops dom0 kernel on AMD hardware. Before I tore down the previous Xen installation in order to load 4.0.0-rc8 I was running 2.6.31.6 and xen 3.4.1 which worked with the exception of the checksumming problem which turned out to be a blocker. But now something has changed between 2.6.31.6 and 2.6.32.10 that seriously affected AMD processor hardware with a "soft lockup" problem. -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2010-May-03 16:18 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
On Fri, Apr 23, 2010 at 01:50:40PM -0400, Gerry Reno wrote:> I previously had the pv_ops dom0 2.6.31.6 kernel built and running on my > hardware (amd phenom ii x4 quad-core) just fine under karmic. But that > kernel had issues with rxchecksumming. So I upgraded the server to > lucid and am now trying to compile a new pv_ops dom0 kernel for it. > > Now, yesterday I carefully built the latest 2.6.32.10(xen/stable) pv_ops > dom0 kernel twice. Once from the config in the email Lucid pv_ops dom0 > howto and once from the lucid server config modified by adding all theGerry, Can you attach your .config file ? I am not seeing it anywhere in the thread. Also is this x86_64 or i386 build? If it is i386 do you have CONFIG_NUMA enabled? If so, what happens if you disable that? Can you also tell me which Phenom it is? 940? _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-May-03 17:18 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
On 05/03/2010 12:18 PM, Konrad Rzeszutek Wilk wrote:> On Fri, Apr 23, 2010 at 01:50:40PM -0400, Gerry Reno wrote: > >> I previously had the pv_ops dom0 2.6.31.6 kernel built and running on my >> hardware (amd phenom ii x4 quad-core) just fine under karmic. But that >> kernel had issues with rxchecksumming. So I upgraded the server to >> lucid and am now trying to compile a new pv_ops dom0 kernel for it. >> >> Now, yesterday I carefully built the latest 2.6.32.10(xen/stable) pv_ops >> dom0 kernel twice. Once from the config in the email Lucid pv_ops dom0 >> howto and once from the lucid server config modified by adding all the >> > Gerry, > > Can you attach your .config file ? I am not seeing it anywhere in the > thread. Also is this x86_64 or i386 build? If it is i386 do you have > CONFIG_NUMA enabled? If so, what happens if you disable that? > > Can you also tell me which Phenom it is? 940? > >Konrad, I attached my .config file and /proc/cpuinfo. The build was x86_64. The cpu is AMD Phenom II x4 940. -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2010-May-03 20:36 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
On Mon, May 03, 2010 at 01:18:44PM -0400, Gerry Reno wrote:> On 05/03/2010 12:18 PM, Konrad Rzeszutek Wilk wrote: >> On Fri, Apr 23, 2010 at 01:50:40PM -0400, Gerry Reno wrote: >> >>> I previously had the pv_ops dom0 2.6.31.6 kernel built and running on my >>> hardware (amd phenom ii x4 quad-core) just fine under karmic. But that >>> kernel had issues with rxchecksumming. So I upgraded the server to >>> lucid and am now trying to compile a new pv_ops dom0 kernel for it. >>> >>> Now, yesterday I carefully built the latest 2.6.32.10(xen/stable) pv_ops >>> dom0 kernel twice. Once from the config in the email Lucid pv_ops dom0 >>> howto and once from the lucid server config modified by adding all the >>> >> Gerry, >> >> Can you attach your .config file ? I am not seeing it anywhere in the >> thread. Also is this x86_64 or i386 build? If it is i386 do you have >> CONFIG_NUMA enabled? If so, what happens if you disable that? >> >> Can you also tell me which Phenom it is? 940? >> >> > > Konrad, I attached my .config file and /proc/cpuinfo. The build was > x86_64. The cpu is AMD Phenom II x4 940.When I use your .config I get these: [ 10.781056] ------------[ cut here ]------------ [ 10.785736] WARNING: at /home/konrad/git/neb.64/linux-up/mm/vmalloc.c:1AMD-BOOT #7 [ 10.790016] Call Trace: [ 10.790016] [<ffffffff810660cb>] warn_slowpath_common+0x7b/0xc0 [ 10.790016] [<ffffffff81066124>] warn_slowpath_null+0x14/0x20 [ 10.790016] [<ffffffff8111bb19>] vmap_page_range_noflush+0x2d9/0x370 [ 10.790016] [<ffffffff8111cfaf>] ? __vmalloc_area_node+0x5f/0x190 [ 10.790016] [<ffffffff8100fadd>] ? xen_force_evtchn_callback+0xd/0x10 [ 10.790016] [<ffffffff8111bbe2>] map_vm_area+0x32/0x50 [ 10.790016] [<ffffffff8111d050>] __vmalloc_area_node+0x100/0x190 [ 10.790016] [<ffffffff8111d0f7>] __vmalloc_area+0x17/0x20 [ 10.790016] [<ffffffff8103592e>] module_alloc+0x5e/0x60 [ 10.790016] [<ffffffff8109b8c6>] module_alloc_update_bounds+0x16/0x50 [ 10.790016] [<ffffffff8109e479>] load_module+0x989/0x1ce0 [ 10.790016] [<ffffffff8113f8a5>] ? vfs_read+0xb5/0x1a0 [ 10.790016] [<ffffffff8109f849>] sys_init_module+0x79/0x250 [ 10.790016] [<ffffffff810140f2>] system_call_fastpath+0x16/0x1b [ 10.790016] ---[ end trace a7919e7f17c0a727 ]--- FATAL: Error inserting xen_kbdfront (/lib/modules/2.6.32.12AMD-BOOT/kernel/drivers/input/xen-kbdfront.ko): Cannot allocate memory Is this about the same thing you see? (the calltrace being of interest here). _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-May-03 21:23 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
On 05/03/2010 04:36 PM, Konrad Rzeszutek Wilk wrote:> On Mon, May 03, 2010 at 01:18:44PM -0400, Gerry Reno wrote: > >> On 05/03/2010 12:18 PM, Konrad Rzeszutek Wilk wrote: >> >>> On Fri, Apr 23, 2010 at 01:50:40PM -0400, Gerry Reno wrote: >>> >>> >>>> I previously had the pv_ops dom0 2.6.31.6 kernel built and running on my >>>> hardware (amd phenom ii x4 quad-core) just fine under karmic. But that >>>> kernel had issues with rxchecksumming. So I upgraded the server to >>>> lucid and am now trying to compile a new pv_ops dom0 kernel for it. >>>> >>>> Now, yesterday I carefully built the latest 2.6.32.10(xen/stable) pv_ops >>>> dom0 kernel twice. Once from the config in the email Lucid pv_ops dom0 >>>> howto and once from the lucid server config modified by adding all the >>>> >>>> >>> Gerry, >>> >>> Can you attach your .config file ? I am not seeing it anywhere in the >>> thread. Also is this x86_64 or i386 build? If it is i386 do you have >>> CONFIG_NUMA enabled? If so, what happens if you disable that? >>> >>> Can you also tell me which Phenom it is? 940? >>> >>> >>> >> Konrad, I attached my .config file and /proc/cpuinfo. The build was >> x86_64. The cpu is AMD Phenom II x4 940. >> > When I use your .config I get these: > > [ 10.781056] ------------[ cut here ]------------ > [ 10.785736] WARNING: at > /home/konrad/git/neb.64/linux-up/mm/vmalloc.c:1AMD-BOOT #7 > [ 10.790016] Call Trace: > [ 10.790016] [<ffffffff810660cb>] warn_slowpath_common+0x7b/0xc0 > [ 10.790016] [<ffffffff81066124>] warn_slowpath_null+0x14/0x20 > [ 10.790016] [<ffffffff8111bb19>] vmap_page_range_noflush+0x2d9/0x370 > [ 10.790016] [<ffffffff8111cfaf>] ? __vmalloc_area_node+0x5f/0x190 > [ 10.790016] [<ffffffff8100fadd>] ? xen_force_evtchn_callback+0xd/0x10 > [ 10.790016] [<ffffffff8111bbe2>] map_vm_area+0x32/0x50 > [ 10.790016] [<ffffffff8111d050>] __vmalloc_area_node+0x100/0x190 > [ 10.790016] [<ffffffff8111d0f7>] __vmalloc_area+0x17/0x20 > [ 10.790016] [<ffffffff8103592e>] module_alloc+0x5e/0x60 > [ 10.790016] [<ffffffff8109b8c6>] module_alloc_update_bounds+0x16/0x50 > [ 10.790016] [<ffffffff8109e479>] load_module+0x989/0x1ce0 > [ 10.790016] [<ffffffff8113f8a5>] ? vfs_read+0xb5/0x1a0 > [ 10.790016] [<ffffffff8109f849>] sys_init_module+0x79/0x250 > [ 10.790016] [<ffffffff810140f2>] system_call_fastpath+0x16/0x1b > [ 10.790016] ---[ end trace a7919e7f17c0a727 ]--- > FATAL: Error inserting xen_kbdfront > (/lib/modules/2.6.32.12AMD-BOOT/kernel/drivers/input/xen-kbdfront.ko): > Cannot allocate memory > > Is this about the same thing you see? (the calltrace being of interest > here). > >The screen output goes by so fast I cannot tell if this call trace is in it. I''m still waiting for a serial card to show up so I can capture the output. When I boot the 2.6.32.10 kernel under Xen pv_ops dom0 it will either start showing "soft lockup" bugs or it just hangs after XENBUS: Unable to read cpu state. If I boot the 2.6.32.10 kernel without Xen then it just hangs - no output at all. -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-May-05 00:42 UTC
Re: [Xen-devel] Cannot load latest 2.6.32.10 kernel on AMD quad-core
On 05/03/2010 05:23 PM, Gerry Reno wrote:> On 05/03/2010 04:36 PM, Konrad Rzeszutek Wilk wrote: >> On Mon, May 03, 2010 at 01:18:44PM -0400, Gerry Reno wrote: >>> On 05/03/2010 12:18 PM, Konrad Rzeszutek Wilk wrote: >>>> On Fri, Apr 23, 2010 at 01:50:40PM -0400, Gerry Reno wrote: >>>> >>>>> I previously had the pv_ops dom0 2.6.31.6 kernel built and running >>>>> on my >>>>> hardware (amd phenom ii x4 quad-core) just fine under karmic. But >>>>> that >>>>> kernel had issues with rxchecksumming. So I upgraded the server to >>>>> lucid and am now trying to compile a new pv_ops dom0 kernel for it. >>>>> >>>>> Now, yesterday I carefully built the latest 2.6.32.10(xen/stable) >>>>> pv_ops >>>>> dom0 kernel twice. Once from the config in the email Lucid pv_ops >>>>> dom0 >>>>> howto and once from the lucid server config modified by adding all >>>>> the >>>>> >>>> Gerry, >>>> >>>> Can you attach your .config file ? I am not seeing it anywhere in the >>>> thread. Also is this x86_64 or i386 build? If it is i386 do you have >>>> CONFIG_NUMA enabled? If so, what happens if you disable that? >>>> >>>> Can you also tell me which Phenom it is? 940? >>>> >>>> >>> Konrad, I attached my .config file and /proc/cpuinfo. The build was >>> x86_64. The cpu is AMD Phenom II x4 940. >> When I use your .config I get these: >> >> [ 10.781056] ------------[ cut here ]------------ >> [ 10.785736] WARNING: at >> /home/konrad/git/neb.64/linux-up/mm/vmalloc.c:1AMD-BOOT #7 >> [ 10.790016] Call Trace: >> [ 10.790016] [<ffffffff810660cb>] warn_slowpath_common+0x7b/0xc0 >> [ 10.790016] [<ffffffff81066124>] warn_slowpath_null+0x14/0x20 >> [ 10.790016] [<ffffffff8111bb19>] vmap_page_range_noflush+0x2d9/0x370 >> [ 10.790016] [<ffffffff8111cfaf>] ? __vmalloc_area_node+0x5f/0x190 >> [ 10.790016] [<ffffffff8100fadd>] ? >> xen_force_evtchn_callback+0xd/0x10 >> [ 10.790016] [<ffffffff8111bbe2>] map_vm_area+0x32/0x50 >> [ 10.790016] [<ffffffff8111d050>] __vmalloc_area_node+0x100/0x190 >> [ 10.790016] [<ffffffff8111d0f7>] __vmalloc_area+0x17/0x20 >> [ 10.790016] [<ffffffff8103592e>] module_alloc+0x5e/0x60 >> [ 10.790016] [<ffffffff8109b8c6>] >> module_alloc_update_bounds+0x16/0x50 >> [ 10.790016] [<ffffffff8109e479>] load_module+0x989/0x1ce0 >> [ 10.790016] [<ffffffff8113f8a5>] ? vfs_read+0xb5/0x1a0 >> [ 10.790016] [<ffffffff8109f849>] sys_init_module+0x79/0x250 >> [ 10.790016] [<ffffffff810140f2>] system_call_fastpath+0x16/0x1b >> [ 10.790016] ---[ end trace a7919e7f17c0a727 ]--- >> FATAL: Error inserting xen_kbdfront >> (/lib/modules/2.6.32.12AMD-BOOT/kernel/drivers/input/xen-kbdfront.ko): >> Cannot allocate memory >> >> Is this about the same thing you see? (the calltrace being of interest >> here). >> > The screen output goes by so fast I cannot tell if this call trace is > in it. I''m still waiting for a serial card to show up so I can > capture the output. When I boot the 2.6.32.10 kernel under Xen pv_ops > dom0 it will either start showing "soft lockup" bugs or it just hangs > after XENBUS: Unable to read cpu state. If I boot the 2.6.32.10 > kernel without Xen then it just hangs - no output at all. > > -Gerry >Finally, my serial port header cables showed up so I installed them and now have some console output. Case 1: Xen 4.0.0-rc8 / pv_ops dom0 kernel 2.6.32.10 After playing around with the order of the consoles on the xen and kernel lines I am able to get a login prompt but only after quite a long time (4-5 mins). It seems like something is stealing processor cycles. And the behavior is not consistent, on different boots I get different errors at times. Case 1: pv_ops domU kernel 2.6.32.10 (no xen dom0) The kernel shows a lot of errors and just hangs. Attached: console output for both cases plus menu.lst -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2010-May-05 17:54 UTC
Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush
> Finally, my serial port header cables showed up so I installed them and > now have some console output. > > Case 1: Xen 4.0.0-rc8 / pv_ops dom0 kernel 2.6.32.10 > > After playing around with the order of the consoles on the xen and > kernel lines I am able to get a login prompt but only after quite a long > time (4-5 mins). It seems like something is stealing processor cycles. > And the behavior is not consistent, on different boots I get different > errors at times. > > > Case 1: pv_ops domU kernel 2.6.32.10 (no xen dom0) > > The kernel shows a lot of errors and just hangs. > > > > Attached: console output for both cases plus menu.lst > > -Gerry > > >> [ 0.000000] Initializing cgroup subsys cpuset > [ 0.000000] Initializing cgroup subsys cpu > [ 0.000000] Linux version 2.6.32.10 (root@grp-01-23-02) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #12 SMP Sat Apr0 > [ 0.000000] Command line: root=/dev/mapper/vg--grp--01--23--02--2-LogVol00 vga=ext ro console=tty0,115200n8 consolet > [ 0.000000] KERNEL supported cpus: > [ 0.000000] Intel GenuineIntel > [ 0.000000] AMD AuthenticAMD > [ 0.000000] Centaur CentaurHauls > [ 0.000000] BIOS-provided physical RAM map: > [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable) > [ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved) > [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) > [ 0.000000] BIOS-e820: 0000000000100000 - 00000000afde0000 (usable) > [ 0.000000] BIOS-e820: 00000000afde0000 - 00000000afde3000 (ACPI NVS) > [ 0.000000] BIOS-e820: 00000000afde3000 - 00000000afdf0000 (ACPI data) > [ 0.000000] BIOS-e820: 00000000afdf0000 - 00000000afe00000 (reserved) > [ 0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved) > [ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved) > [ 0.000000] BIOS-e820: 0000000100000000 - 0000000230000000 (usable) > [ 0.000000] DMI 2.4 present. > [ 0.000000] last_pfn = 0x230000 max_arch_pfn = 0x400000000 > [ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 > [ 0.000000] last_pfn = 0xafde0 max_arch_pfn = 0x400000000 > [ 0.000000] Scanning 1 areas for low memory corruption > [ 0.000000] modified physical RAM map: > [ 0.000000] modified: 0000000000000000 - 0000000000001000 (usable) > [ 0.000000] modified: 0000000000001000 - 0000000000006000 (reserved) > [ 0.000000] modified: 0000000000006000 - 000000000009f800 (usable) > [ 0.000000] modified: 000000000009f800 - 00000000000a0000 (reserved) > [ 0.000000] modified: 00000000000f0000 - 0000000000100000 (reserved) > [ 0.000000] modified: 0000000000100000 - 00000000afde0000 (usable) > [ 0.000000] modified: 00000000afde0000 - 00000000afde3000 (ACPI NVS) > [ 0.000000] modified: 00000000afde3000 - 00000000afdf0000 (ACPI data) > [ 0.000000] modified: 00000000afdf0000 - 00000000afe00000 (reserved) > [ 0.000000] modified: 00000000e0000000 - 00000000f0000000 (reserved) > [ 0.000000] modified: 00000000fec00000 - 0000000100000000 (reserved) > [ 0.000000] modified: 0000000100000000 - 0000000230000000 (usable) > [ 0.000000] Using GB pages for direct mapping > [ 0.000000] init_memory_mapping: 0000000000000000-00000000afde0000 > [ 0.000000] init_memory_mapping: 0000000100000000-0000000230000000 > [ 0.000000] RAMDISK: 33d29000 - 37fef12a > [ 0.000000] ACPI: RSDP 00000000000f75d0 00014 (v00 GBT ) > [ 0.000000] ACPI: RSDT 00000000afde3000 00038 (v01 GBT GBTUACPI 42302E31 GBTU 01010101) > [ 0.000000] ACPI: FACP 00000000afde3040 00074 (v01 GBT GBTUACPI 42302E31 GBTU 01010101) > [ 0.000000] ACPI: DSDT 00000000afde30c0 06E65 (v01 GBT GBTUACPI 00001000 MSFT 03000000) > [ 0.000000] ACPI: FACS 00000000afde0000 00040 > [ 0.000000] ACPI: HPET 00000000afdea000 00038 (v01 GBT GBTUACPI 42302E31 GBTU 00000098) > [ 0.000000] ACPI: MCFG 00000000afdea040 0003C (v01 GBT GBTUACPI 42302E31 GBTU 01010101) > [ 0.000000] ACPI: TAMG 00000000afdea080 0030A (v01 GBT GBT B0 5455312E BG?? 53450101) > [ 0.000000] ACPI: APIC 00000000afde9f40 00084 (v01 GBT GBTUACPI 42302E31 GBTU 01010101) > [ 0.000000] Scanning NUMA topology in Northbridge 24 > [ 0.000000] No NUMA configuration found > [ 0.000000] Faking a node at 0000000000000000-0000000230000000 > [ 0.000000] Bootmem setup node 0 0000000000000000-0000000230000000 > [ 0.000000] NODE_DATA [000000000000b000 - 000000000000ffff] > [ 0.000000] bootmap [0000000000010000 - 0000000000055fff] pages 46 > [ 0.000000] (8 early reservations) ==> bootmem [0000000000 - 0230000000] > [ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] > [ 0.000000] #1 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000] > [ 0.000000] #2 [0001000000 - 0001a51864] TEXT DATA BSS ==> [0001000000 - 0001a51864] > [ 0.000000] #3 [0033d29000 - 0037fef12a] RAMDISK ==> [0033d29000 - 0037fef12a] > [ 0.000000] #4 [000009f800 - 0000100000] BIOS reserved ==> [000009f800 - 0000100000] > [ 0.000000] #5 [0001a52000 - 0001a520fe] BRK ==> [0001a52000 - 0001a520fe] > [ 0.000000] #6 [0000008000 - 000000a000] PGTABLE ==> [0000008000 - 000000a000] > [ 0.000000] #7 [000000a000 - 000000b000] PGTABLE ==> [000000a000 - 000000b000] > [ 0.000000] found SMP MP-table at [ffff8800000f5c30] f5c30 > [ 0.000000] Zone PFN ranges: > [ 0.000000] DMA 0x00000000 -> 0x00001000 > [ 0.000000] DMA32 0x00001000 -> 0x00100000 > [ 0.000000] Normal 0x00100000 -> 0x00230000 > [ 0.000000] Movable zone start PFN for each node > [ 0.000000] early_node_map[4] active PFN ranges > [ 0.000000] 0: 0x00000000 -> 0x00000001 > [ 0.000000] 0: 0x00000006 -> 0x0000009f > [ 0.000000] 0: 0x00000100 -> 0x000afde0 > [ 0.000000] 0: 0x00100000 -> 0x00230000 > [ 0.000000] ACPI: PM-Timer IO Port: 0x4008 > [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) > [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled) > [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1]) > [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1]) > [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1]) > [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1]) > [ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) > [ 0.000000] IOAPIC[0]: apic_id 2, version 33, address 0xfec00000, GSI 0-23 > [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) > [ 0.000000] Using ACPI (MADT) for SMP configuration information > [ 0.000000] ACPI: HPET id: 0x10b9a201 base: 0xfed00000 > [ 0.000000] SMP: Allowing 4 CPUs, 0 hotplug CPUs > [ 0.000000] PM: Registered nosave memory: 0000000000001000 - 0000000000006000 > [ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000 > [ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000 > [ 0.000000] PM: Registered nosave memory: 00000000000f0000 - 0000000000100000 > [ 0.000000] PM: Registered nosave memory: 00000000afde0000 - 00000000afde3000 > [ 0.000000] PM: Registered nosave memory: 00000000afde3000 - 00000000afdf0000 > [ 0.000000] PM: Registered nosave memory: 00000000afdf0000 - 00000000afe00000 > [ 0.000000] PM: Registered nosave memory: 00000000afe00000 - 00000000e0000000 > [ 0.000000] PM: Registered nosave memory: 00000000e0000000 - 00000000f0000000 > [ 0.000000] PM: Registered nosave memory: 00000000f0000000 - 00000000fec00000 > [ 0.000000] PM: Registered nosave memory: 00000000fec00000 - 0000000100000000 > [ 0.000000] Allocating PCI resources starting at afe00000 (gap: afe00000:30200000) > [ 0.000000] Booting paravirtualized kernel on bare hardware > [ 0.000000] NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:4 nr_node_ids:1 > [ 0.000000] PERCPU: Embedded 30 pages/cpu @ffff880008a00000 s91416 r8192 d23272 u524288 > [ 0.000000] pcpu-alloc: s91416 r8192 d23272 u524288 alloc=1*2097152 > [ 0.000000] pcpu-alloc: [0] 0 1 2 3 > [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1933972 > [ 0.000000] Policy zone: Normal > [ 0.000000] Kernel command line: root=/dev/mapper/vg--grp--01--23--02--2-LogVol00 vga=ext ro console=tty0,115200n8 t > [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes) > [ 0.000000] Initializing CPU#0 > [ 0.000000] Checking aperture... > [ 0.000000] No AGP bridge found > [ 0.000000] Node 0: aperture @ 20000000 size 32 MB > [ 0.000000] Aperture pointing to e820 RAM. Ignoring. > [ 0.000000] Memory: 7605344k/9175040k available (5523k kernel code, 1313304k absent, 256392k reserved, 3053k data, 8) > [ 0.000000] SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 > [ 0.000000] Hierarchical RCU implementation. > [ 0.000000] NR_IRQS:4352 nr_irqs:440 > [ 0.000000] Console: colour VGA+ 80x50 > [ 0.000000] console [tty0] enabled > [ 0.000000] console [ttyS0] enabled > [ 0.000000] allocated 78643200 bytes of page_cgroup > [ 0.000000] please try ''cgroup_disable=memory'' option if you don''t want memory cgroups > [ 0.000000] HPET: 4 timers in total, 1 timers will be used for per-cpu timer > [ 0.000000] Fast TSC calibration using PIT > [ 0.000000] Detected 3013.747 MHz processor. > [ 0.030006] Calibrating delay loop (skipped), value calculated using timer frequency.. 6027.48 BogoMIPS (lpj=3013743) > [ 0.050017] Security Framework initialized > [ 0.054134] SELinux: Disabled at boot. > [ 0.058452] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes) > [ 0.063393] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes) > [ 0.071575] Mount-cache hash table entries: 256 > [ 0.080121] Initializing cgroup subsys ns > [ 0.084147] Initializing cgroup subsys cpuacct > [ 0.090004] Initializing cgroup subsys memory > [ 0.094384] Initializing cgroup subsys devices > [ 0.100002] Initializing cgroup subsys freezer > [ 0.104466] Initializing cgroup subsys net_cls > [ 0.108943] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) > [ 0.110002] CPU: L2 Cache: 512K (64 bytes/line) > [ 0.120003] CPU 0/0x0 -> Node 0 > [ 0.123163] CPU: Physical Processor ID: 0 > [ 0.127190] CPU: Processor Core ID: 0 > [ 0.130002] mce: CPU supports 6 MCE banks > [ 0.134042] using C1E aware idle routine > [ 0.137986] Performance Events: AMD PMU driver. > [ 0.141521] ... version: 0 > [ 0.145549] ... bit width: 48 > [ 0.150001] ... generic registers: 4 > [ 0.154024] ... value mask: 0000ffffffffffff > [ 0.160001] ... max period: 00007fffffffffff > [ 0.165330] ... fixed-purpose events: 0 > [ 0.170001] ... event mask: 000000000000000f > [ 0.176667] ACPI: Core revision 20090903 > [ 0.200029] ftrace: converting mcount calls to 0f 1f 44 00 00 > [ 0.210008] ftrace: allocating 21751 entries in 86 pages > [ 0.225172] Setting APIC routing to flat > [ 0.230490] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 > [ 0.336570] CPU0: AMD Phenom(tm) II X4 940 Processor stepping 02 > [ 0.350000] Booting processor 1 APIC 0x1 ip 0x6000 > [ 0.040000] Initializing CPU#1 > [ 0.040000] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) > [ 0.040000] CPU: L2 Cache: 512K (64 bytes/line) > [ 0.040000] CPU 1/0x1 -> Node 0 > [ 0.040000] CPU: Physical Processor ID: 0 > [ 0.040000] CPU: Processor Core ID: 1 > [ 0.500087] CPU1: AMD Phenom(tm) II X4 940 Processor stepping 02 > [ 0.521266] checking TSC synchronization [CPU#0 -> CPU#1]: passed. > [ 0.530052] Booting processor 2 APIC 0x2 ip 0x6000 > [ 0.040000] Initializing CPU#2 > [ 0.040000] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) > [ 0.040000] CPU: L2 Cache: 512K (64 bytes/line) > [ 0.040000] CPU 2/0x2 -> Node 0 > [ 0.040000] CPU: Physical Processor ID: 0 > [ 0.040000] CPU: Processor Core ID: 3 > [ 0.700082] CPU2: AMD Phenom(tm) II X4 940 Processor stepping 02 > [ 0.721263] checking TSC synchronization [CPU#0 -> CPU#2]: passed. > [ 0.730058] Booting processor 3 APIC 0x3 ip 0x6000 > [ 0.040000] Initializing CPU#3 > [ 0.040000] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) > [ 0.040000] CPU: L2 Cache: 512K (64 bytes/line) > [ 0.040000] CPU 3/0x3 -> Node 0 > [ 0.040000] CPU: Physical Processor ID: 0 > [ 0.040000] CPU: Processor Core ID: 2 > [ 0.900091] CPU3: AMD Phenom(tm) II X4 940 Processor stepping 02 > [ 0.921264] checking TSC synchronization [CPU#0 -> CPU#3]: passed. > [ 0.930009] Brought up 4 CPUs > [ 0.940001] Total of 4 processors activated (24110.25 BogoMIPS). > [ 0.950170] devtmpfs: initialized > [ 0.954622] regulator: core version 0.5 > [ 0.958500] Time: 0:10:44 Date: 05/05/10 > [ 0.960041] NET: Registered protocol family 16 > [ 0.964594] TOM: 00000000d0000000 aka 3328M > [ 0.970012] TOM2: 0000000230000000 aka 8960M > [ 0.974339] ACPI: bus type pci registered > [ 0.978424] PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255 > [ 0.980002] PCI: MCFG area at e0000000 reserved in E820 > [ 0.995600] PCI: Using MMCONFIG at e0000000 - efffffff > [ 1.000001] PCI: Using configuration type 1 for base access > [ 1.006220] bio: create slab <bio-0> at 0 > [ 1.020358] ACPI: Interpreter enabled > [ 1.024052] ACPI: (supports S0 S1 S4 S5) > [ 1.028207] ACPI: Using IOAPIC for interrupt routing > [ 1.033096] ACPI Warning: Incorrect checksum in table [??????"???] - 00, should be A6 (20090903/tbutils-314) > [ 1.042365] ACPI: No dock devices found. > [ 1.046409] ACPI: PCI Root Bridge [PCI0] (0000:00) > [ 1.050128] pci 0000:00:0a.0: PME# supported from D0 D3hot D3cold > [ 1.060002] pci 0000:00:0a.0: PME# disabled > [ 1.064490] pci 0000:00:12.2: PME# supported from D0 D1 D2 D3hot > [ 1.070003] pci 0000:00:12.2: PME# disabled > [ 1.074404] pci 0000:00:13.2: PME# supported from D0 D1 D2 D3hot > [ 1.080004] pci 0000:00:13.2: PME# disabled > [ 1.084437] pci 0000:00:14.2: PME# supported from D0 D3hot D3cold > [ 1.090003] pci 0000:00:14.2: PME# disabled > [ 1.094608] pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold > [ 1.100003] pci 0000:02:00.0: PME# disabled > [ 1.104387] pci 0000:03:0e.0: PME# supported from D0 D1 D2 D3hot > [ 1.110004] pci 0000:03:0e.0: PME# disabled > [ 1.114240] pci 0000:00:14.4: transparent bridge > [ 1.132377] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 11) *0, disabled. > [ 1.140299] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 11) *0, disabled. > [ 1.148292] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 11) *0, disabled. > [ 1.153425] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11) *0, disabled. > [ 1.163451] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11) *0, disabled. > [ 1.172355] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11) *0, disabled. > [ 1.180286] ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 6 7 10 11) *0, disabled. > [ 1.188293] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11) *0, disabled. > [ 1.193491] vgaarb: device added: PCI:0000:01:05.0,decodes=io+mem,owns=io+mem,locks=none > [ 1.200002] vgaarb: loaded > [ 1.202810] SCSI subsystem initialized > [ 1.210142] usbcore: registered new interface driver usbfs > [ 1.215652] usbcore: registered new interface driver hub > [ 1.220016] usbcore: registered new device driver usb > [ 1.225157] ACPI: WMI: Mapper loaded > [ 1.230001] PCI: Using ACPI for IRQ routing > [ 1.234206] pci 0000:00:00.0: BAR 3: address space collision on of device [0xe0000000-0xffffffff] > [ 1.240001] pci 0000:00:00.0: BAR 3: can''t allocate resource > [ 1.250004] NetLabel: Initializing > [ 1.253432] NetLabel: domain hash size = 128 > [ 1.257807] NetLabel: protocols = UNLABELED CIPSOv4 > [ 1.260009] NetLabel: unlabeled traffic allowed by default > [ 1.265630] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 24, 0 > [ 1.271470] hpet0: 4 comparators, 32-bit 14.318180 MHz counter > [ 1.281005] Switching to clocksource tsc > [ 1.285069] pnp: PnP ACPI init > [ 1.285069] ACPI: bus type pnp registered > [ 1.289814] pnp 00:0c: mem resource (0xd1c00-0xd3fff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling > [ 1.299767] pnp 00:0c: mem resource (0xf0000-0xf7fff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling > [ 1.309708] pnp 00:0c: mem resource (0xf8000-0xfbfff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling > [ 1.319646] pnp 00:0c: mem resource (0xfc000-0xfffff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling > [ 1.329587] pnp 00:0c: mem resource (0x0-0x9ffff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling > [ 1.339181] pnp 00:0c: mem resource (0x100000-0xafddffff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling > [ 1.349524] pnp: PnP ACPI: found 13 devices > [ 1.353738] ACPI: ACPI bus type pnp unregistered > [ 1.358377] system 00:01: ioport range 0x4d0-0x4d1 has been reserved > [ 1.364773] system 00:01: ioport range 0x220-0x225 has been reserved > [ 1.371159] system 00:01: ioport range 0x290-0x294 has been reserved > [ 1.377523] system 00:02: ioport range 0x4100-0x411f has been reserved > [ 1.384089] system 00:02: ioport range 0x228-0x22f has been reserved > [ 1.390470] system 00:02: ioport range 0x40b-0x40b has been reserved > [ 1.396832] system 00:02: ioport range 0x4d6-0x4d6 has been reserved > [ 1.403229] system 00:02: ioport range 0xc00-0xc01 has been reserved > [ 1.409597] system 00:02: ioport range 0xc14-0xc14 has been reserved > [ 1.415992] system 00:02: ioport range 0xc50-0xc52 has been reserved > [ 1.422370] system 00:02: ioport range 0xc6c-0xc6d has been reserved > [ 1.428735] system 00:02: ioport range 0xc6f-0xc6f has been reserved > [ 1.435128] system 00:02: ioport range 0xcd0-0xcd1 has been reserved > [ 1.441509] system 00:02: ioport range 0xcd2-0xcd3 has been reserved > [ 1.447871] system 00:02: ioport range 0xcd4-0xcdf has been reserved > [ 1.454266] system 00:02: ioport range 0x4000-0x40fe has been reserved > [ 1.460818] system 00:02: ioport range 0x4210-0x4217 has been reserved > [ 1.467355] system 00:02: ioport range 0xb00-0xb0f has been reserved > [ 1.473748] system 00:02: ioport range 0xb10-0xb1f has been reserved > [ 1.480128] system 00:02: ioport range 0xb20-0xb3f has been reserved > [ 1.486493] system 00:0b: iomem range 0xe0000000-0xefffffff has been reserved > [ 1.493667] system 00:0c: iomem range 0xafde0000-0xafdfffff could not be reserved > [ 1.501182] system 00:0c: iomem range 0xffff0000-0xffffffff has been reserved > [ 1.508330] system 00:0c: iomem range 0xafef0000-0xcfeeffff could not be reserved > [ 1.515856] system 00:0c: iomem range 0xfec00000-0xfec00fff could not be reserved > [ 1.523369] system 00:0c: iomem range 0xfee00000-0xfee00fff has been reserved > [ 1.530534] system 00:0c: iomem range 0xfff80000-0xfffeffff has been reserved > [ 1.542754] pci 0000:00:01.0: PCI bridge, secondary bus 0000:01 > [ 1.548689] pci 0000:00:01.0: IO window: 0xe000-0xefff > [ 1.554050] pci 0000:00:01.0: MEM window: 0xfde00000-0xfdffffff > [ 1.560175] pci 0000:00:01.0: PREFETCH window: 0x000000d0000000-0x000000dfffffff > [ 1.567754] pci 0000:00:0a.0: PCI bridge, secondary bus 0000:02 > [ 1.573722] pci 0000:00:0a.0: IO window: 0xd000-0xdfff > [ 1.579047] pci 0000:00:0a.0: MEM window: 0xfdd00000-0xfddfffff > [ 1.585181] pci 0000:00:0a.0: PREFETCH window: 0x000000fda00000-0x000000fdafffff > [ 1.592775] pci 0000:00:14.4: PCI bridge, secondary bus 0000:03 > [ 1.598711] pci 0000:00:14.4: IO window: 0xc000-0xcfff > [ 1.604067] pci 0000:00:14.4: MEM window: 0xfdc00000-0xfdcfffff > [ 1.610193] pci 0000:00:14.4: PREFETCH window: 0xfdb00000-0xfdbfffff > [ 1.616751] pci 0000:00:0a.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 > [ 1.623549] NET: Registered protocol family 2 > [ 1.628090] IP route cache hash table entries: 262144 (order: 9, 2097152 bytes) > [ 1.636549] ------------[ cut here ]------------ > [ 1.641209] WARNING: at mm/vmalloc.c:110 vmap_page_range_noflush+0x301/0x380() > [ 1.648440] Hardware name: GA-MA790GP-UD4H > [ 1.652582] Modules linked in: > [ 1.655710] Pid: 1, comm: swapper Not tainted 2.6.32.10 #12 > [ 1.661321] Call Trace: > [ 1.663801] [<ffffffff8106602b>] warn_slowpath_common+0x7b/0xc0 > [ 1.669819] [<ffffffff81066084>] warn_slowpath_null+0x14/0x20 > [ 1.675698] [<ffffffff8111bb31>] vmap_page_range_noflush+0x301/0x380 > [ 1.682164] [<ffffffff8111bbe2>] map_vm_area+0x32/0x50 > [ 1.687402] [<ffffffff8111d010>] __vmalloc_area_node+0x100/0x190 > [ 1.693535] [<ffffffff81898700>] ? alloc_large_system_hash+0x15e/0x222 > [ 1.700172] [<ffffffff8111cf02>] __vmalloc_node+0xa2/0xb0 > [ 1.705671] [<ffffffff81898700>] ? alloc_large_system_hash+0x15e/0x222 > [ 1.712324] [<ffffffff818b4a72>] ? inet_init+0x0/0x209 > [ 1.717562] [<ffffffff8111d282>] __vmalloc+0x22/0x30 > [ 1.722653] [<ffffffff81898700>] alloc_large_system_hash+0x15e/0x222 > [ 1.729916] [<ffffffff818b4a72>] ? inet_init+0x0/0x209 > [ 1.735186] [<ffffffff818b4a72>] ? inet_init+0x0/0x209 > [ 1.740438] [<ffffffff818b44b6>] tcp_init+0xa3/0x383 > [ 1.745505] [<ffffffff818b4bbd>] inet_init+0x14b/0x209 > [ 1.750772] [<ffffffff8100a04c>] do_one_initcall+0x3c/0x1a0 > [ 1.756451] [<ffffffff8187972c>] kernel_init+0x15a/0x1b0 > [ 1.761890] [<ffffffff810150ea>] child_rip+0xa/0x20 > [ 1.766870] [<ffffffff818795d2>] ? kernel_init+0x0/0x1b0 > [ 1.772307] [<ffffffff810150e0>] ? child_rip+0x0/0x20 > [ 1.777461] ---[ end trace e93713a9d40cd06c ]--- > [ 1.782160] general protection fault: 0000 [#1] SMPThis is the same error I''ve gotten. Now thought I can''t reproduce it (after I slimmed down the .config to build less modules). Try ''nopat'' as a command line parameter. Also, you might want to update your kernel. The 2.6.32.12 is out _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-May-06 03:18 UTC
Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush
On 05/05/2010 01:54 PM, Konrad Rzeszutek Wilk wrote:>> Finally, my serial port header cables showed up so I installed them and >> now have some console output. >> >> Case 1: Xen 4.0.0-rc8 / pv_ops dom0 kernel 2.6.32.10 >> >> After playing around with the order of the consoles on the xen and >> kernel lines I am able to get a login prompt but only after quite a long >> time (4-5 mins). It seems like something is stealing processor cycles. >> And the behavior is not consistent, on different boots I get different >> errors at times. >> >> >> Case 1: pv_ops domU kernel 2.6.32.10 (no xen dom0) >> >> The kernel shows a lot of errors and just hangs. >> >> >> >> Attached: console output for both cases plus menu.lst >> >> -Gerry >> >> >> >> > >> [ 0.000000] Initializing cgroup subsys cpuset >> [ 0.000000] Initializing cgroup subsys cpu >> [ 0.000000] Linux version 2.6.32.10 (root@grp-01-23-02) (gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) ) #12 SMP Sat Apr0 >> [ 0.000000] Command line: root=/dev/mapper/vg--grp--01--23--02--2-LogVol00 vga=ext ro console=tty0,115200n8 consolet >> [ 0.000000] KERNEL supported cpus: >> [ 0.000000] Intel GenuineIntel >> [ 0.000000] AMD AuthenticAMD >> [ 0.000000] Centaur CentaurHauls >> [ 0.000000] BIOS-provided physical RAM map: >> [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable) >> [ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved) >> [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) >> [ 0.000000] BIOS-e820: 0000000000100000 - 00000000afde0000 (usable) >> [ 0.000000] BIOS-e820: 00000000afde0000 - 00000000afde3000 (ACPI NVS) >> [ 0.000000] BIOS-e820: 00000000afde3000 - 00000000afdf0000 (ACPI data) >> [ 0.000000] BIOS-e820: 00000000afdf0000 - 00000000afe00000 (reserved) >> [ 0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved) >> [ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved) >> [ 0.000000] BIOS-e820: 0000000100000000 - 0000000230000000 (usable) >> [ 0.000000] DMI 2.4 present. >> [ 0.000000] last_pfn = 0x230000 max_arch_pfn = 0x400000000 >> [ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 >> [ 0.000000] last_pfn = 0xafde0 max_arch_pfn = 0x400000000 >> [ 0.000000] Scanning 1 areas for low memory corruption >> [ 0.000000] modified physical RAM map: >> [ 0.000000] modified: 0000000000000000 - 0000000000001000 (usable) >> [ 0.000000] modified: 0000000000001000 - 0000000000006000 (reserved) >> [ 0.000000] modified: 0000000000006000 - 000000000009f800 (usable) >> [ 0.000000] modified: 000000000009f800 - 00000000000a0000 (reserved) >> [ 0.000000] modified: 00000000000f0000 - 0000000000100000 (reserved) >> [ 0.000000] modified: 0000000000100000 - 00000000afde0000 (usable) >> [ 0.000000] modified: 00000000afde0000 - 00000000afde3000 (ACPI NVS) >> [ 0.000000] modified: 00000000afde3000 - 00000000afdf0000 (ACPI data) >> [ 0.000000] modified: 00000000afdf0000 - 00000000afe00000 (reserved) >> [ 0.000000] modified: 00000000e0000000 - 00000000f0000000 (reserved) >> [ 0.000000] modified: 00000000fec00000 - 0000000100000000 (reserved) >> [ 0.000000] modified: 0000000100000000 - 0000000230000000 (usable) >> [ 0.000000] Using GB pages for direct mapping >> [ 0.000000] init_memory_mapping: 0000000000000000-00000000afde0000 >> [ 0.000000] init_memory_mapping: 0000000100000000-0000000230000000 >> [ 0.000000] RAMDISK: 33d29000 - 37fef12a >> [ 0.000000] ACPI: RSDP 00000000000f75d0 00014 (v00 GBT ) >> [ 0.000000] ACPI: RSDT 00000000afde3000 00038 (v01 GBT GBTUACPI 42302E31 GBTU 01010101) >> [ 0.000000] ACPI: FACP 00000000afde3040 00074 (v01 GBT GBTUACPI 42302E31 GBTU 01010101) >> [ 0.000000] ACPI: DSDT 00000000afde30c0 06E65 (v01 GBT GBTUACPI 00001000 MSFT 03000000) >> [ 0.000000] ACPI: FACS 00000000afde0000 00040 >> [ 0.000000] ACPI: HPET 00000000afdea000 00038 (v01 GBT GBTUACPI 42302E31 GBTU 00000098) >> [ 0.000000] ACPI: MCFG 00000000afdea040 0003C (v01 GBT GBTUACPI 42302E31 GBTU 01010101) >> [ 0.000000] ACPI: TAMG 00000000afdea080 0030A (v01 GBT GBT B0 5455312E BG?? 53450101) >> [ 0.000000] ACPI: APIC 00000000afde9f40 00084 (v01 GBT GBTUACPI 42302E31 GBTU 01010101) >> [ 0.000000] Scanning NUMA topology in Northbridge 24 >> [ 0.000000] No NUMA configuration found >> [ 0.000000] Faking a node at 0000000000000000-0000000230000000 >> [ 0.000000] Bootmem setup node 0 0000000000000000-0000000230000000 >> [ 0.000000] NODE_DATA [000000000000b000 - 000000000000ffff] >> [ 0.000000] bootmap [0000000000010000 - 0000000000055fff] pages 46 >> [ 0.000000] (8 early reservations) ==> bootmem [0000000000 - 0230000000] >> [ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] >> [ 0.000000] #1 [0000006000 - 0000008000] TRAMPOLINE ==> [0000006000 - 0000008000] >> [ 0.000000] #2 [0001000000 - 0001a51864] TEXT DATA BSS ==> [0001000000 - 0001a51864] >> [ 0.000000] #3 [0033d29000 - 0037fef12a] RAMDISK ==> [0033d29000 - 0037fef12a] >> [ 0.000000] #4 [000009f800 - 0000100000] BIOS reserved ==> [000009f800 - 0000100000] >> [ 0.000000] #5 [0001a52000 - 0001a520fe] BRK ==> [0001a52000 - 0001a520fe] >> [ 0.000000] #6 [0000008000 - 000000a000] PGTABLE ==> [0000008000 - 000000a000] >> [ 0.000000] #7 [000000a000 - 000000b000] PGTABLE ==> [000000a000 - 000000b000] >> [ 0.000000] found SMP MP-table at [ffff8800000f5c30] f5c30 >> [ 0.000000] Zone PFN ranges: >> [ 0.000000] DMA 0x00000000 -> 0x00001000 >> [ 0.000000] DMA32 0x00001000 -> 0x00100000 >> [ 0.000000] Normal 0x00100000 -> 0x00230000 >> [ 0.000000] Movable zone start PFN for each node >> [ 0.000000] early_node_map[4] active PFN ranges >> [ 0.000000] 0: 0x00000000 -> 0x00000001 >> [ 0.000000] 0: 0x00000006 -> 0x0000009f >> [ 0.000000] 0: 0x00000100 -> 0x000afde0 >> [ 0.000000] 0: 0x00100000 -> 0x00230000 >> [ 0.000000] ACPI: PM-Timer IO Port: 0x4008 >> [ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) >> [ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) >> [ 0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled) >> [ 0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled) >> [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1]) >> [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1]) >> [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1]) >> [ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] dfl dfl lint[0x1]) >> [ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) >> [ 0.000000] IOAPIC[0]: apic_id 2, version 33, address 0xfec00000, GSI 0-23 >> [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) >> [ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) >> [ 0.000000] Using ACPI (MADT) for SMP configuration information >> [ 0.000000] ACPI: HPET id: 0x10b9a201 base: 0xfed00000 >> [ 0.000000] SMP: Allowing 4 CPUs, 0 hotplug CPUs >> [ 0.000000] PM: Registered nosave memory: 0000000000001000 - 0000000000006000 >> [ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000 >> [ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000 >> [ 0.000000] PM: Registered nosave memory: 00000000000f0000 - 0000000000100000 >> [ 0.000000] PM: Registered nosave memory: 00000000afde0000 - 00000000afde3000 >> [ 0.000000] PM: Registered nosave memory: 00000000afde3000 - 00000000afdf0000 >> [ 0.000000] PM: Registered nosave memory: 00000000afdf0000 - 00000000afe00000 >> [ 0.000000] PM: Registered nosave memory: 00000000afe00000 - 00000000e0000000 >> [ 0.000000] PM: Registered nosave memory: 00000000e0000000 - 00000000f0000000 >> [ 0.000000] PM: Registered nosave memory: 00000000f0000000 - 00000000fec00000 >> [ 0.000000] PM: Registered nosave memory: 00000000fec00000 - 0000000100000000 >> [ 0.000000] Allocating PCI resources starting at afe00000 (gap: afe00000:30200000) >> [ 0.000000] Booting paravirtualized kernel on bare hardware >> [ 0.000000] NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:4 nr_node_ids:1 >> [ 0.000000] PERCPU: Embedded 30 pages/cpu @ffff880008a00000 s91416 r8192 d23272 u524288 >> [ 0.000000] pcpu-alloc: s91416 r8192 d23272 u524288 alloc=1*2097152 >> [ 0.000000] pcpu-alloc: [0] 0 1 2 3 >> [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1933972 >> [ 0.000000] Policy zone: Normal >> [ 0.000000] Kernel command line: root=/dev/mapper/vg--grp--01--23--02--2-LogVol00 vga=ext ro console=tty0,115200n8 t >> [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes) >> [ 0.000000] Initializing CPU#0 >> [ 0.000000] Checking aperture... >> [ 0.000000] No AGP bridge found >> [ 0.000000] Node 0: aperture @ 20000000 size 32 MB >> [ 0.000000] Aperture pointing to e820 RAM. Ignoring. >> [ 0.000000] Memory: 7605344k/9175040k available (5523k kernel code, 1313304k absent, 256392k reserved, 3053k data, 8) >> [ 0.000000] SLUB: Genslabs=14, HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 >> [ 0.000000] Hierarchical RCU implementation. >> [ 0.000000] NR_IRQS:4352 nr_irqs:440 >> [ 0.000000] Console: colour VGA+ 80x50 >> [ 0.000000] console [tty0] enabled >> [ 0.000000] console [ttyS0] enabled >> [ 0.000000] allocated 78643200 bytes of page_cgroup >> [ 0.000000] please try ''cgroup_disable=memory'' option if you don''t want memory cgroups >> [ 0.000000] HPET: 4 timers in total, 1 timers will be used for per-cpu timer >> [ 0.000000] Fast TSC calibration using PIT >> [ 0.000000] Detected 3013.747 MHz processor. >> [ 0.030006] Calibrating delay loop (skipped), value calculated using timer frequency.. 6027.48 BogoMIPS (lpj=3013743) >> [ 0.050017] Security Framework initialized >> [ 0.054134] SELinux: Disabled at boot. >> [ 0.058452] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes) >> [ 0.063393] Inode-cache hash table entries: 524288 (order: 10, 4194304 bytes) >> [ 0.071575] Mount-cache hash table entries: 256 >> [ 0.080121] Initializing cgroup subsys ns >> [ 0.084147] Initializing cgroup subsys cpuacct >> [ 0.090004] Initializing cgroup subsys memory >> [ 0.094384] Initializing cgroup subsys devices >> [ 0.100002] Initializing cgroup subsys freezer >> [ 0.104466] Initializing cgroup subsys net_cls >> [ 0.108943] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) >> [ 0.110002] CPU: L2 Cache: 512K (64 bytes/line) >> [ 0.120003] CPU 0/0x0 -> Node 0 >> [ 0.123163] CPU: Physical Processor ID: 0 >> [ 0.127190] CPU: Processor Core ID: 0 >> [ 0.130002] mce: CPU supports 6 MCE banks >> [ 0.134042] using C1E aware idle routine >> [ 0.137986] Performance Events: AMD PMU driver. >> [ 0.141521] ... version: 0 >> [ 0.145549] ... bit width: 48 >> [ 0.150001] ... generic registers: 4 >> [ 0.154024] ... value mask: 0000ffffffffffff >> [ 0.160001] ... max period: 00007fffffffffff >> [ 0.165330] ... fixed-purpose events: 0 >> [ 0.170001] ... event mask: 000000000000000f >> [ 0.176667] ACPI: Core revision 20090903 >> [ 0.200029] ftrace: converting mcount calls to 0f 1f 44 00 00 >> [ 0.210008] ftrace: allocating 21751 entries in 86 pages >> [ 0.225172] Setting APIC routing to flat >> [ 0.230490] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 >> [ 0.336570] CPU0: AMD Phenom(tm) II X4 940 Processor stepping 02 >> [ 0.350000] Booting processor 1 APIC 0x1 ip 0x6000 >> [ 0.040000] Initializing CPU#1 >> [ 0.040000] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) >> [ 0.040000] CPU: L2 Cache: 512K (64 bytes/line) >> [ 0.040000] CPU 1/0x1 -> Node 0 >> [ 0.040000] CPU: Physical Processor ID: 0 >> [ 0.040000] CPU: Processor Core ID: 1 >> [ 0.500087] CPU1: AMD Phenom(tm) II X4 940 Processor stepping 02 >> [ 0.521266] checking TSC synchronization [CPU#0 -> CPU#1]: passed. >> [ 0.530052] Booting processor 2 APIC 0x2 ip 0x6000 >> [ 0.040000] Initializing CPU#2 >> [ 0.040000] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) >> [ 0.040000] CPU: L2 Cache: 512K (64 bytes/line) >> [ 0.040000] CPU 2/0x2 -> Node 0 >> [ 0.040000] CPU: Physical Processor ID: 0 >> [ 0.040000] CPU: Processor Core ID: 3 >> [ 0.700082] CPU2: AMD Phenom(tm) II X4 940 Processor stepping 02 >> [ 0.721263] checking TSC synchronization [CPU#0 -> CPU#2]: passed. >> [ 0.730058] Booting processor 3 APIC 0x3 ip 0x6000 >> [ 0.040000] Initializing CPU#3 >> [ 0.040000] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) >> [ 0.040000] CPU: L2 Cache: 512K (64 bytes/line) >> [ 0.040000] CPU 3/0x3 -> Node 0 >> [ 0.040000] CPU: Physical Processor ID: 0 >> [ 0.040000] CPU: Processor Core ID: 2 >> [ 0.900091] CPU3: AMD Phenom(tm) II X4 940 Processor stepping 02 >> [ 0.921264] checking TSC synchronization [CPU#0 -> CPU#3]: passed. >> [ 0.930009] Brought up 4 CPUs >> [ 0.940001] Total of 4 processors activated (24110.25 BogoMIPS). >> [ 0.950170] devtmpfs: initialized >> [ 0.954622] regulator: core version 0.5 >> [ 0.958500] Time: 0:10:44 Date: 05/05/10 >> [ 0.960041] NET: Registered protocol family 16 >> [ 0.964594] TOM: 00000000d0000000 aka 3328M >> [ 0.970012] TOM2: 0000000230000000 aka 8960M >> [ 0.974339] ACPI: bus type pci registered >> [ 0.978424] PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255 >> [ 0.980002] PCI: MCFG area at e0000000 reserved in E820 >> [ 0.995600] PCI: Using MMCONFIG at e0000000 - efffffff >> [ 1.000001] PCI: Using configuration type 1 for base access >> [ 1.006220] bio: create slab<bio-0> at 0 >> [ 1.020358] ACPI: Interpreter enabled >> [ 1.024052] ACPI: (supports S0 S1 S4 S5) >> [ 1.028207] ACPI: Using IOAPIC for interrupt routing >> [ 1.033096] ACPI Warning: Incorrect checksum in table [??????"???] - 00, should be A6 (20090903/tbutils-314) >> [ 1.042365] ACPI: No dock devices found. >> [ 1.046409] ACPI: PCI Root Bridge [PCI0] (0000:00) >> [ 1.050128] pci 0000:00:0a.0: PME# supported from D0 D3hot D3cold >> [ 1.060002] pci 0000:00:0a.0: PME# disabled >> [ 1.064490] pci 0000:00:12.2: PME# supported from D0 D1 D2 D3hot >> [ 1.070003] pci 0000:00:12.2: PME# disabled >> [ 1.074404] pci 0000:00:13.2: PME# supported from D0 D1 D2 D3hot >> [ 1.080004] pci 0000:00:13.2: PME# disabled >> [ 1.084437] pci 0000:00:14.2: PME# supported from D0 D3hot D3cold >> [ 1.090003] pci 0000:00:14.2: PME# disabled >> [ 1.094608] pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold >> [ 1.100003] pci 0000:02:00.0: PME# disabled >> [ 1.104387] pci 0000:03:0e.0: PME# supported from D0 D1 D2 D3hot >> [ 1.110004] pci 0000:03:0e.0: PME# disabled >> [ 1.114240] pci 0000:00:14.4: transparent bridge >> [ 1.132377] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 11) *0, disabled. >> [ 1.140299] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 11) *0, disabled. >> [ 1.148292] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 11) *0, disabled. >> [ 1.153425] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 10 11) *0, disabled. >> [ 1.163451] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11) *0, disabled. >> [ 1.172355] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11) *0, disabled. >> [ 1.180286] ACPI: PCI Interrupt Link [LNK0] (IRQs 3 4 5 6 7 10 11) *0, disabled. >> [ 1.188293] ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11) *0, disabled. >> [ 1.193491] vgaarb: device added: PCI:0000:01:05.0,decodes=io+mem,owns=io+mem,locks=none >> [ 1.200002] vgaarb: loaded >> [ 1.202810] SCSI subsystem initialized >> [ 1.210142] usbcore: registered new interface driver usbfs >> [ 1.215652] usbcore: registered new interface driver hub >> [ 1.220016] usbcore: registered new device driver usb >> [ 1.225157] ACPI: WMI: Mapper loaded >> [ 1.230001] PCI: Using ACPI for IRQ routing >> [ 1.234206] pci 0000:00:00.0: BAR 3: address space collision on of device [0xe0000000-0xffffffff] >> [ 1.240001] pci 0000:00:00.0: BAR 3: can''t allocate resource >> [ 1.250004] NetLabel: Initializing >> [ 1.253432] NetLabel: domain hash size = 128 >> [ 1.257807] NetLabel: protocols = UNLABELED CIPSOv4 >> [ 1.260009] NetLabel: unlabeled traffic allowed by default >> [ 1.265630] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 24, 0 >> [ 1.271470] hpet0: 4 comparators, 32-bit 14.318180 MHz counter >> [ 1.281005] Switching to clocksource tsc >> [ 1.285069] pnp: PnP ACPI init >> [ 1.285069] ACPI: bus type pnp registered >> [ 1.289814] pnp 00:0c: mem resource (0xd1c00-0xd3fff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling >> [ 1.299767] pnp 00:0c: mem resource (0xf0000-0xf7fff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling >> [ 1.309708] pnp 00:0c: mem resource (0xf8000-0xfbfff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling >> [ 1.319646] pnp 00:0c: mem resource (0xfc000-0xfffff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling >> [ 1.329587] pnp 00:0c: mem resource (0x0-0x9ffff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling >> [ 1.339181] pnp 00:0c: mem resource (0x100000-0xafddffff) overlaps 0000:00:00.0 BAR 3 (0x0-0x1fffffff), disabling >> [ 1.349524] pnp: PnP ACPI: found 13 devices >> [ 1.353738] ACPI: ACPI bus type pnp unregistered >> [ 1.358377] system 00:01: ioport range 0x4d0-0x4d1 has been reserved >> [ 1.364773] system 00:01: ioport range 0x220-0x225 has been reserved >> [ 1.371159] system 00:01: ioport range 0x290-0x294 has been reserved >> [ 1.377523] system 00:02: ioport range 0x4100-0x411f has been reserved >> [ 1.384089] system 00:02: ioport range 0x228-0x22f has been reserved >> [ 1.390470] system 00:02: ioport range 0x40b-0x40b has been reserved >> [ 1.396832] system 00:02: ioport range 0x4d6-0x4d6 has been reserved >> [ 1.403229] system 00:02: ioport range 0xc00-0xc01 has been reserved >> [ 1.409597] system 00:02: ioport range 0xc14-0xc14 has been reserved >> [ 1.415992] system 00:02: ioport range 0xc50-0xc52 has been reserved >> [ 1.422370] system 00:02: ioport range 0xc6c-0xc6d has been reserved >> [ 1.428735] system 00:02: ioport range 0xc6f-0xc6f has been reserved >> [ 1.435128] system 00:02: ioport range 0xcd0-0xcd1 has been reserved >> [ 1.441509] system 00:02: ioport range 0xcd2-0xcd3 has been reserved >> [ 1.447871] system 00:02: ioport range 0xcd4-0xcdf has been reserved >> [ 1.454266] system 00:02: ioport range 0x4000-0x40fe has been reserved >> [ 1.460818] system 00:02: ioport range 0x4210-0x4217 has been reserved >> [ 1.467355] system 00:02: ioport range 0xb00-0xb0f has been reserved >> [ 1.473748] system 00:02: ioport range 0xb10-0xb1f has been reserved >> [ 1.480128] system 00:02: ioport range 0xb20-0xb3f has been reserved >> [ 1.486493] system 00:0b: iomem range 0xe0000000-0xefffffff has been reserved >> [ 1.493667] system 00:0c: iomem range 0xafde0000-0xafdfffff could not be reserved >> [ 1.501182] system 00:0c: iomem range 0xffff0000-0xffffffff has been reserved >> [ 1.508330] system 00:0c: iomem range 0xafef0000-0xcfeeffff could not be reserved >> [ 1.515856] system 00:0c: iomem range 0xfec00000-0xfec00fff could not be reserved >> [ 1.523369] system 00:0c: iomem range 0xfee00000-0xfee00fff has been reserved >> [ 1.530534] system 00:0c: iomem range 0xfff80000-0xfffeffff has been reserved >> [ 1.542754] pci 0000:00:01.0: PCI bridge, secondary bus 0000:01 >> [ 1.548689] pci 0000:00:01.0: IO window: 0xe000-0xefff >> [ 1.554050] pci 0000:00:01.0: MEM window: 0xfde00000-0xfdffffff >> [ 1.560175] pci 0000:00:01.0: PREFETCH window: 0x000000d0000000-0x000000dfffffff >> [ 1.567754] pci 0000:00:0a.0: PCI bridge, secondary bus 0000:02 >> [ 1.573722] pci 0000:00:0a.0: IO window: 0xd000-0xdfff >> [ 1.579047] pci 0000:00:0a.0: MEM window: 0xfdd00000-0xfddfffff >> [ 1.585181] pci 0000:00:0a.0: PREFETCH window: 0x000000fda00000-0x000000fdafffff >> [ 1.592775] pci 0000:00:14.4: PCI bridge, secondary bus 0000:03 >> [ 1.598711] pci 0000:00:14.4: IO window: 0xc000-0xcfff >> [ 1.604067] pci 0000:00:14.4: MEM window: 0xfdc00000-0xfdcfffff >> [ 1.610193] pci 0000:00:14.4: PREFETCH window: 0xfdb00000-0xfdbfffff >> [ 1.616751] pci 0000:00:0a.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 >> [ 1.623549] NET: Registered protocol family 2 >> [ 1.628090] IP route cache hash table entries: 262144 (order: 9, 2097152 bytes) >> [ 1.636549] ------------[ cut here ]------------ >> [ 1.641209] WARNING: at mm/vmalloc.c:110 vmap_page_range_noflush+0x301/0x380() >> [ 1.648440] Hardware name: GA-MA790GP-UD4H >> [ 1.652582] Modules linked in: >> [ 1.655710] Pid: 1, comm: swapper Not tainted 2.6.32.10 #12 >> [ 1.661321] Call Trace: >> [ 1.663801] [<ffffffff8106602b>] warn_slowpath_common+0x7b/0xc0 >> [ 1.669819] [<ffffffff81066084>] warn_slowpath_null+0x14/0x20 >> [ 1.675698] [<ffffffff8111bb31>] vmap_page_range_noflush+0x301/0x380 >> [ 1.682164] [<ffffffff8111bbe2>] map_vm_area+0x32/0x50 >> [ 1.687402] [<ffffffff8111d010>] __vmalloc_area_node+0x100/0x190 >> [ 1.693535] [<ffffffff81898700>] ? alloc_large_system_hash+0x15e/0x222 >> [ 1.700172] [<ffffffff8111cf02>] __vmalloc_node+0xa2/0xb0 >> [ 1.705671] [<ffffffff81898700>] ? alloc_large_system_hash+0x15e/0x222 >> [ 1.712324] [<ffffffff818b4a72>] ? inet_init+0x0/0x209 >> [ 1.717562] [<ffffffff8111d282>] __vmalloc+0x22/0x30 >> [ 1.722653] [<ffffffff81898700>] alloc_large_system_hash+0x15e/0x222 >> [ 1.729916] [<ffffffff818b4a72>] ? inet_init+0x0/0x209 >> [ 1.735186] [<ffffffff818b4a72>] ? inet_init+0x0/0x209 >> [ 1.740438] [<ffffffff818b44b6>] tcp_init+0xa3/0x383 >> [ 1.745505] [<ffffffff818b4bbd>] inet_init+0x14b/0x209 >> [ 1.750772] [<ffffffff8100a04c>] do_one_initcall+0x3c/0x1a0 >> [ 1.756451] [<ffffffff8187972c>] kernel_init+0x15a/0x1b0 >> [ 1.761890] [<ffffffff810150ea>] child_rip+0xa/0x20 >> [ 1.766870] [<ffffffff818795d2>] ? kernel_init+0x0/0x1b0 >> [ 1.772307] [<ffffffff810150e0>] ? child_rip+0x0/0x20 >> [ 1.777461] ---[ end trace e93713a9d40cd06c ]--- >> [ 1.782160] general protection fault: 0000 [#1] SMP >> > This is the same error I''ve gotten. Now thought I can''t reproduce it (after > I slimmed down the .config to build less modules). > > Try ''nopat'' as a command line parameter. > > Also, you might want to update your kernel. The 2.6.32.12 is out > >Thanks. I tried ''nopat'' but that did not seem to change anything. I also tried ''git pull'' for xen/stable but it says ''Already up to date''. So where do I find the 2.6.32.12? -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2010-May-06 05:52 UTC
Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush
On Wed, May 05, 2010 at 11:18:52PM -0400, Gerry Reno wrote:> On 05/05/2010 01:54 PM, Konrad Rzeszutek Wilk wrote: >>> Finally, my serial port header cables showed up so I installed them and >>> now have some console output. >>> >>> Case 1: Xen 4.0.0-rc8 / pv_ops dom0 kernel 2.6.32.10 >>> >>> After playing around with the order of the consoles on the xen and >>> kernel lines I am able to get a login prompt but only after quite a long >>> time (4-5 mins). It seems like something is stealing processor cycles. >>> And the behavior is not consistent, on different boots I get different >>> errors at times. >>> >>> >>> Case 1: pv_ops domU kernel 2.6.32.10 (no xen dom0) >>> >>> The kernel shows a lot of errors and just hangs. >>> >>> >>> >>> Attached: console output for both cases plus menu.lst >>> >>> -Gerry >>> >>> >>> >>> >> >>> [ 1.616751] pci 0000:00:0a.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 >>> [ 1.623549] NET: Registered protocol family 2 >>> [ 1.628090] IP route cache hash table entries: 262144 (order: 9, 2097152 bytes) >>> [ 1.636549] ------------[ cut here ]------------ >>> [ 1.641209] WARNING: at mm/vmalloc.c:110 vmap_page_range_noflush+0x301/0x380() >>> [ 1.648440] Hardware name: GA-MA790GP-UD4H >>> [ 1.652582] Modules linked in: >>> [ 1.655710] Pid: 1, comm: swapper Not tainted 2.6.32.10 #12 >>> [ 1.661321] Call Trace: >>> [ 1.663801] [<ffffffff8106602b>] warn_slowpath_common+0x7b/0xc0 >>> [ 1.669819] [<ffffffff81066084>] warn_slowpath_null+0x14/0x20 >>> [ 1.675698] [<ffffffff8111bb31>] vmap_page_range_noflush+0x301/0x380 >>> [ 1.682164] [<ffffffff8111bbe2>] map_vm_area+0x32/0x50 >>> [ 1.687402] [<ffffffff8111d010>] __vmalloc_area_node+0x100/0x190 >>> [ 1.693535] [<ffffffff81898700>] ? alloc_large_system_hash+0x15e/0x222 >>> [ 1.700172] [<ffffffff8111cf02>] __vmalloc_node+0xa2/0xb0 >>> [ 1.705671] [<ffffffff81898700>] ? alloc_large_system_hash+0x15e/0x222 >>> [ 1.712324] [<ffffffff818b4a72>] ? inet_init+0x0/0x209 >>> [ 1.717562] [<ffffffff8111d282>] __vmalloc+0x22/0x30 >>> [ 1.722653] [<ffffffff81898700>] alloc_large_system_hash+0x15e/0x222 >>> [ 1.729916] [<ffffffff818b4a72>] ? inet_init+0x0/0x209 >>> [ 1.735186] [<ffffffff818b4a72>] ? inet_init+0x0/0x209 >>> [ 1.740438] [<ffffffff818b44b6>] tcp_init+0xa3/0x383 >>> [ 1.745505] [<ffffffff818b4bbd>] inet_init+0x14b/0x209 >>> [ 1.750772] [<ffffffff8100a04c>] do_one_initcall+0x3c/0x1a0 >>> [ 1.756451] [<ffffffff8187972c>] kernel_init+0x15a/0x1b0 >>> [ 1.761890] [<ffffffff810150ea>] child_rip+0xa/0x20 >>> [ 1.766870] [<ffffffff818795d2>] ? kernel_init+0x0/0x1b0 >>> [ 1.772307] [<ffffffff810150e0>] ? child_rip+0x0/0x20 >>> [ 1.777461] ---[ end trace e93713a9d40cd06c ]--- >>> [ 1.782160] general protection fault: 0000 [#1] SMP >>> >> This is the same error I''ve gotten. Now thought I can''t reproduce it (after >> I slimmed down the .config to build less modules). >> >> Try ''nopat'' as a command line parameter. >> >> Also, you might want to update your kernel. The 2.6.32.12 is out >> >> > Thanks. I tried ''nopat'' but that did not seem to change anything. > > I also tried ''git pull'' for xen/stable but it says ''Already up to date''. > So where do I find the 2.6.32.12? >You should be using xen/stable-2.6.32.x branch. changelog: http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=xen/stable-2.6.32.x -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2010-May-06 17:57 UTC
Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush
On 05/05/2010 10:52 PM, Pasi Kärkkäinen wrote:> You should be using xen/stable-2.6.32.x branch. >Meaning, do "git checkout xen/stable-2.6.32.x". And if you want to make it the default, add "XEN_LINUX_GIT_REMOTEBRANCH = xen/stable-2.6.32.x" to your Config.mk. J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-May-06 19:39 UTC
Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush
On 05/06/2010 01:57 PM, Jeremy Fitzhardinge wrote:> On 05/05/2010 10:52 PM, Pasi Kärkkäinen wrote: > >> You should be using xen/stable-2.6.32.x branch. >> >> > Meaning, do "git checkout xen/stable-2.6.32.x". And if you want to make > it the default, add "XEN_LINUX_GIT_REMOTEBRANCH = xen/stable-2.6.32.x" > to your Config.mk. > > J > >Here''s what I did on my platform (ubuntu lucid) which got 2.6.32.12 compiled and installed (not tested yet): sudo su - cd /usr/src git clone git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git linux-2.6-xen cd linux-2.6-xen git reset --hard git checkout -b xen/stable-2.6.32.x origin/xen/stable-2.6.32.x git pull cp PATHTOYOURCONFIG/.config . make oldconfig make menuconfig # if you need to change something make chmod g-s /usr/src -R make deb-pkg dpkg -i ../linux-image-2.6.32.12_2.6.32.12-2_amd64.deb # update deb version if you rebuild kernel depmod 2.6.32.12 update-initramfs -c -k 2.6.32.12 update-grub echo "xen-evtchn" >> /etc/modules -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-May-07 00:21 UTC
Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush
Ok, I tested with the new 2.6.32.12: (.config same) Case 1: Xen 4.0.0-rc8 / pv_ops dom0 kernel 2.6.32.12 Still pv_ops dom0 is not working properly. There are still call trace and other errors. The kernel does boot up but it takes again a long time to get the login prompt (about 3 mins). This is far longer than when I used 2.6.31.6 pv_ops dom0. Networking does not start properly (only see ''lo'' and ''virbr0''), so I have to restart it manually and then I see my bridge ''br0'' and ''eth0''. Can''t find device "br0" /etc/xen/scripts/network-bridge: line 240: "sigerr" command not found. And it is trying unsuccessfully to start some laptop feature like S99powernap (unknown job) and also S28-libvirt-bin fails (maybe network related?). Case 2: pv_ops domU kernel 2.6.32.12 (no xen dom0): Now the straight linux kernel (no xen dom0) boots right up and goes to login prompt in normal timeframe. Networking starts correctly. Things look pretty normal. Observation: I''m getting slightly different output on console and serial console. Some errors show on one but not the other. Shouldn''t these be identical? I''m attaching both serial console outputs. menu.lst is same as before (just .12 instead of .10) -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-May-07 02:22 UTC
Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush
On 05/06/2010 08:21 PM, Gerry Reno wrote:> Ok, I tested with the new 2.6.32.12: (.config same) > > Case 1: Xen 4.0.0-rc8 / pv_ops dom0 kernel 2.6.32.12 > > Still pv_ops dom0 is not working properly. > There are still call trace and other errors. The kernel does boot up > but it takes again a long time to get the login prompt (about 3 > mins). This is far longer than when I used 2.6.31.6 pv_ops dom0. > Networking does not start properly (only see ''lo'' and ''virbr0''), so I > have to restart it manually and then I see my bridge ''br0'' and ''eth0''. > Can''t find device "br0" > /etc/xen/scripts/network-bridge: line 240: "sigerr" command not found. > And it is trying unsuccessfully to start some laptop feature like > S99powernap (unknown job) and also S28-libvirt-bin fails (maybe > network related?). > > > Case 2: pv_ops domU kernel 2.6.32.12 (no xen dom0): > > Now the straight linux kernel (no xen dom0) boots right up and goes to > login prompt in normal timeframe. Networking starts correctly. > Things look pretty normal. > > > Observation: > I''m getting slightly different output on console and serial console. > Some errors show on one but not the other. Shouldn''t these be identical? > > > I''m attaching both serial console outputs. > > menu.lst is same as before (just .12 instead of .10) > > -Gerry > >And I''m attaching the syslog from Case 1 (pv_ops dom0). -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2010-May-07 06:05 UTC
Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush
On Thu, May 06, 2010 at 10:22:03PM -0400, Gerry Reno wrote:> On 05/06/2010 08:21 PM, Gerry Reno wrote: >> Ok, I tested with the new 2.6.32.12: (.config same) >> >> Case 1: Xen 4.0.0-rc8 / pv_ops dom0 kernel 2.6.32.12 >> >> Still pv_ops dom0 is not working properly. >> There are still call trace and other errors. The kernel does boot up >> but it takes again a long time to get the login prompt (about 3 mins). >> This is far longer than when I used 2.6.31.6 pv_ops dom0. Networking >> does not start properly (only see ''lo'' and ''virbr0''), so I have to >> restart it manually and then I see my bridge ''br0'' and ''eth0''. >> Can''t find device "br0" >> /etc/xen/scripts/network-bridge: line 240: "sigerr" command not found. >> And it is trying unsuccessfully to start some laptop feature like >> S99powernap (unknown job) and also S28-libvirt-bin fails (maybe >> network related?). >> >> >> Case 2: pv_ops domU kernel 2.6.32.12 (no xen dom0): >> >> Now the straight linux kernel (no xen dom0) boots right up and goes to >> login prompt in normal timeframe. Networking starts correctly. >> Things look pretty normal. >> >> >> Observation: >> I''m getting slightly different output on console and serial console. >> Some errors show on one but not the other. Shouldn''t these be >> identical? >> >> >> I''m attaching both serial console outputs. >> >> menu.lst is same as before (just .12 instead of .10) >> >> -Gerry >> >> > And I''m attaching the syslog from Case 1 (pv_ops dom0). >You should be posting two things: 1) xm dmesg 2) dmesg Aka the full boot log, from both Xen hypervisor and dom0 Linux kernel. -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2010-May-07 06:21 UTC
Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush
>> /etc/xen/scripts/network-bridge: line 240: "sigerr" command not found.apt-get install bridge-utils ( has been done ?) If yes, you could try remove br0 declaration from /etc/network/interfaces and edit properly /etc/xen/xend-config.sxp . Xen should bring up bridge with no pain after reboot. Just service xend restart might not help. I got this error this error as reaction on any mistake in Xen network config on Lucid. Boris. P.S. you could keep br0 declaration and commented out network bridging setup in /etc/xen/xend-config.sxp. It works as well. --- On Fri, 5/7/10, Pasi Kärkkäinen <pasik@iki.fi> wrote: From: Pasi Kärkkäinen <pasik@iki.fi> Subject: Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush To: "Gerry Reno" <greno@verizon.net> Cc: xen-devel@lists.xensource.com, "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com> Date: Friday, May 7, 2010, 2:05 AM On Thu, May 06, 2010 at 10:22:03PM -0400, Gerry Reno wrote:> On 05/06/2010 08:21 PM, Gerry Reno wrote: >> Ok, I tested with the new 2.6.32.12: (.config same) >> >> Case 1: Xen 4.0.0-rc8 / pv_ops dom0 kernel 2.6.32.12 >> >> Still pv_ops dom0 is not working properly. >> There are still call trace and other errors. The kernel does boot up >> but it takes again a long time to get the login prompt (about 3 mins). >> This is far longer than when I used 2.6.31.6 pv_ops dom0. Networking >> does not start properly (only see ''lo'' and ''virbr0''), so I have to >> restart it manually and then I see my bridge ''br0'' and ''eth0''. >> Can''t find device "br0" >> /etc/xen/scripts/network-bridge: line 240: "sigerr" command not found. >> And it is trying unsuccessfully to start some laptop feature like >> S99powernap (unknown job) and also S28-libvirt-bin fails (maybe >> network related?). >> >> >> Case 2: pv_ops domU kernel 2.6.32.12 (no xen dom0): >> >> Now the straight linux kernel (no xen dom0) boots right up and goes to >> login prompt in normal timeframe. Networking starts correctly. >> Things look pretty normal. >> >> >> Observation: >> I''m getting slightly different output on console and serial console. >> Some errors show on one but not the other. Shouldn''t these be >> identical? >> >> >> I''m attaching both serial console outputs. >> >> menu.lst is same as before (just .12 instead of .10) >> >> -Gerry >> >> > And I''m attaching the syslog from Case 1 (pv_ops dom0). >You should be posting two things: 1) xm dmesg 2) dmesg Aka the full boot log, from both Xen hypervisor and dom0 Linux kernel. -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-May-07 16:44 UTC
Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush
On 05/07/2010 02:21 AM, Boris Derzhavets wrote:> > >> /etc/xen/scripts/network-bridge: line 240: "sigerr" command not found. > > apt-get install bridge-utils ( has been done ?) > If yes, you could try remove br0 declaration from /etc/network/interfaces > and edit properly /etc/xen/xend-config.sxp . Xen should bring up bridge > with no pain after reboot. Just service xend restart might not help. > I got this error this error as reaction on any mistake in Xen network > config > on Lucid. > > Boris. > P.S. you could keep br0 declaration and commented out network bridging > setup > in /etc/xen/xend-config.sxp. It works as well. > > > > --- On *Fri, 5/7/10, Pasi Kärkkäinen /<pasik@iki.fi>/* wrote: > > > From: Pasi Kärkkäinen <pasik@iki.fi> > Subject: Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 > vmap_page_range_noflush > To: "Gerry Reno" <greno@verizon.net> > Cc: xen-devel@lists.xensource.com, "Konrad Rzeszutek Wilk" > <konrad.wilk@oracle.com> > Date: Friday, May 7, 2010, 2:05 AM > > On Thu, May 06, 2010 at 10:22:03PM -0400, Gerry Reno wrote: > > On 05/06/2010 08:21 PM, Gerry Reno wrote: > >> Ok, I tested with the new 2.6.32.12: (.config same) > >> > >> Case 1: Xen 4.0.0-rc8 / pv_ops dom0 kernel 2.6.32.12 > >> > >> Still pv_ops dom0 is not working properly. > >> There are still call trace and other errors. The kernel does > boot up > >> but it takes again a long time to get the login prompt (about 3 > mins). > >> This is far longer than when I used 2.6.31.6 pv_ops dom0. > Networking > >> does not start properly (only see ''lo'' and ''virbr0''), so I have to > >> restart it manually and then I see my bridge ''br0'' and ''eth0''. > >> Can''t find device "br0" > >> /etc/xen/scripts/network-bridge: line 240: "sigerr" command not > found. > >> And it is trying unsuccessfully to start some laptop feature like > >> S99powernap (unknown job) and also S28-libvirt-bin fails (maybe > >> network related?). > >> > >> > >> Case 2: pv_ops domU kernel 2.6.32.12 (no xen dom0): > >> > >> Now the straight linux kernel (no xen dom0) boots right up and > goes to > >> login prompt in normal timeframe. Networking starts correctly. > >> Things look pretty normal. > >> > >> > >> Observation: > >> I''m getting slightly different output on console and serial > console. > >> Some errors show on one but not the other. Shouldn''t these be > >> identical? > >> > >> > >> I''m attaching both serial console outputs. > >> > >> menu.lst is same as before (just .12 instead of .10) > >> > >> -Gerry > >> > >> > > And I''m attaching the syslog from Case 1 (pv_ops dom0). > > > > You should be posting two things: > > 1) xm dmesg > 2) dmesg > > Aka the full boot log, from both Xen hypervisor and dom0 Linux kernel. > > -- Pasi > >Pasi, I am attaching ''xm dmesg'' and ''dmesg''. Boris, bridge-utils is installed and latest. I will try some of these other things you suggested. -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-May-07 21:53 UTC
Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush
On 05/07/2010 12:44 PM, Gerry Reno wrote:> On 05/07/2010 02:21 AM, Boris Derzhavets wrote: >> >> >> /etc/xen/scripts/network-bridge: line 240: "sigerr" command not found. >> >> apt-get install bridge-utils ( has been done ?) >> If yes, you could try remove br0 declaration from /etc/network/interfaces >> and edit properly /etc/xen/xend-config.sxp . Xen should bring up bridge >> with no pain after reboot. Just service xend restart might not help. >> I got this error this error as reaction on any mistake in Xen network >> config >> on Lucid. >> >> Boris. >> P.S. you could keep br0 declaration and commented out network >> bridging setup >> in /etc/xen/xend-config.sxp. It works as well. >> >> >> >> --- On *Fri, 5/7/10, Pasi Kärkkäinen /<pasik@iki.fi>/* wrote: >> >> >> From: Pasi Kärkkäinen <pasik@iki.fi> >> Subject: Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 >> vmap_page_range_noflush >> To: "Gerry Reno" <greno@verizon.net> >> Cc: xen-devel@lists.xensource.com, "Konrad Rzeszutek Wilk" >> <konrad.wilk@oracle.com> >> Date: Friday, May 7, 2010, 2:05 AM >> >> On Thu, May 06, 2010 at 10:22:03PM -0400, Gerry Reno wrote: >> > On 05/06/2010 08:21 PM, Gerry Reno wrote: >> >> Ok, I tested with the new 2.6.32.12: (.config same) >> >> >> >> Case 1: Xen 4.0.0-rc8 / pv_ops dom0 kernel 2.6.32.12 >> >> >> >> Still pv_ops dom0 is not working properly. >> >> There are still call trace and other errors. The kernel does >> boot up >> >> but it takes again a long time to get the login prompt (about >> 3 mins). >> >> This is far longer than when I used 2.6.31.6 pv_ops dom0. >> Networking >> >> does not start properly (only see ''lo'' and ''virbr0''), so I >> have to >> >> restart it manually and then I see my bridge ''br0'' and ''eth0''. >> >> Can''t find device "br0" >> >> /etc/xen/scripts/network-bridge: line 240: "sigerr" command >> not found. >> >> And it is trying unsuccessfully to start some laptop feature like >> >> S99powernap (unknown job) and also S28-libvirt-bin fails (maybe >> >> network related?). >> >> >> >> >> >> Case 2: pv_ops domU kernel 2.6.32.12 (no xen dom0): >> >> >> >> Now the straight linux kernel (no xen dom0) boots right up and >> goes to >> >> login prompt in normal timeframe. Networking starts correctly. >> >> Things look pretty normal. >> >> >> >> >> >> Observation: >> >> I''m getting slightly different output on console and serial >> console. >> >> Some errors show on one but not the other. Shouldn''t these be >> >> identical? >> >> >> >> >> >> I''m attaching both serial console outputs. >> >> >> >> menu.lst is same as before (just .12 instead of .10) >> >> >> >> -Gerry >> >> >> >> >> > And I''m attaching the syslog from Case 1 (pv_ops dom0). >> > >> >> You should be posting two things: >> >> 1) xm dmesg >> 2) dmesg >> >> Aka the full boot log, from both Xen hypervisor and dom0 Linux >> kernel. >> >> -- Pasi >> >> > Pasi, I am attaching ''xm dmesg'' and ''dmesg''. > > Boris, bridge-utils is installed and latest. I will try some of these > other things you suggested. > > -GerryOk, I tried to adjust bridge parameters and found that I can finally get pv_ops dom0 to boot in normal timeframe if I comment out all bridge related statements in /etc/xen/xend-config.sxp. Before with 2.6.31.6 I had (network-script network-bridge) and also tried (network-script ''network-bridge bridge=br0'') but these do not work with 2.6.32.12. However, there are still errors in the pv_ops dom0 2.6.32.12 console output so I''m attaching the output so someone could see if they are serious or if there are workarounds to improve things. I''m seeing things like ''unable to locate IOAPIC for xxx'', call trace from enlighten.c, ''d0 domain attempted wrmsr'', ''Detected 1226681.732 MHz processor.''(a 1.2 TeraHz processor??? - the processor is actually a 3.1 GHz processor), ''No compatible ACPI _PSS objects found.''. Plus, why do I see slightly different outputs on the consoles? Some errors only show on one of the consoles but not the other. -Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Boris Derzhavets
2010-May-08 07:20 UTC
Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush
> ''No compatible ACPI _PSS objects found.''ACPI for 2.6.32.12 is written different from *31* . I don''t know exactly what except acpi_processor has been changed by Yu Ke. ACPI stuff is his responsibility.> unable to locate IOAPIC for xxx'', call trace fromenlighten.c, ''d0 domain attempted> wrmsr'',IOAPIC i believe was also reworked by Xiantao Zang for 2.6.32.X. It works OK on the recent Intel Boards. Address issues directly. Boris. --- On Fri, 5/7/10, Gerry Reno <greno@verizon.net> wrote: From: Gerry Reno <greno@verizon.net> Subject: Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush To: xen-devel@lists.xensource.com Date: Friday, May 7, 2010, 5:53 PM On 05/07/2010 12:44 PM, Gerry Reno wrote: On 05/07/2010 02:21 AM, Boris Derzhavets wrote:>> /etc/xen/scripts/network-bridge: line 240: "sigerr" commandnot found. apt-get install bridge-utils ( has been done ?) If yes, you could try remove br0 declaration from /etc/network/interfaces and edit properly /etc/xen/xend-config.sxp . Xen should bring up bridge with no pain after reboot. Just service xend restart might not help. I got this error this error as reaction on any mistake in Xen network config on Lucid. Boris. P.S. you could keep br0 declaration and commented out network bridging setup in /etc/xen/xend-config.sxp. It works as well. --- On Fri, 5/7/10, Pasi Kärkkäinen <pasik@iki.fi> wrote: From: Pasi Kärkkäinen <pasik@iki.fi> Subject: Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush To: "Gerry Reno" <greno@verizon.net> Cc: xen-devel@lists.xensource.com, "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com> Date: Friday, May 7, 2010, 2:05 AM On Thu, May 06, 2010 at 10:22:03PM -0400, Gerry Reno wrote:> On 05/06/2010 08:21 PM, Gerry Reno wrote:>> Ok, I tested with the new 2.6.32.12: (.config same)>>>> Case 1: Xen 4.0.0-rc8 / pv_ops dom0 kernel 2.6.32.12>>>> Still pv_ops dom0 is not working properly.>> There are still call trace and other errors. The kernel doesboot up>> but it takes again a long time to get the login prompt (about3 mins).>> This is far longer than when I used 2.6.31.6 pv_ops dom0.Networking>> does not start properly (only see ''lo'' and ''virbr0''), so Ihave to>> restart it manually and then I see my bridge ''br0'' and ''eth0''.>> Can''t find device "br0">> /etc/xen/scripts/network-bridge: line 240: "sigerr" commandnot found.>> And it is trying unsuccessfully to start some laptop featurelike>> S99powernap (unknown job) and also S28-libvirt-bin fails(maybe>> network related?).>>>>>> Case 2: pv_ops domU kernel 2.6.32.12 (no xen dom0):>>>> Now the straight linux kernel (no xen dom0) boots right up andgoes to>> login prompt in normal timeframe. Networking startscorrectly.>> Things look pretty normal.>>>>>> Observation:>> I''m getting slightly different output on console and serialconsole.>> Some errors show on one but not the other. Shouldn''t these be>> identical?>>>>>> I''m attaching both serial console outputs.>>>> menu.lst is same as before (just .12 instead of .10)>>>> -Gerry>>>>> And I''m attaching the syslog from Case 1 (pv_ops dom0).>You should be posting two things: 1) xm dmesg 2) dmesg Aka the full boot log, from both Xen hypervisor and dom0 Linux kernel. -- Pasi Pasi, I am attaching ''xm dmesg'' and ''dmesg''. Boris, bridge-utils is installed and latest. I will try some of these other things you suggested. -Gerry Ok, I tried to adjust bridge parameters and found that I can finally get pv_ops dom0 to boot in normal timeframe if I comment out all bridge related statements in /etc/xen/xend-config.sxp. Before with 2.6.31.6 I had (network-script network-bridge) and also tried (network-script ''network-bridge bridge=br0'') but these do not work with 2.6.32.12. However, there are still errors in the pv_ops dom0 2.6.32.12 console output so I''m attaching the output so someone could see if they are serious or if there are workarounds to improve things. I''m seeing things like ''unable to locate IOAPIC for xxx'', call trace from enlighten.c, ''d0 domain attempted wrmsr'', ''Detected 1226681.732 MHz processor.''(a 1.2 TeraHz processor??? - the processor is actually a 3.1 GHz processor), ''No compatible ACPI _PSS objects found.''. Plus, why do I see slightly different outputs on the consoles? Some errors only show on one of the consoles but not the other. -Gerry -----Inline Attachment Follows----- _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2010-May-10 14:10 UTC
Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush
> Ok, I tried to adjust bridge parameters and found that I can finally get > pv_ops dom0 to boot in normal timeframe if I comment out all bridge > related statements in /etc/xen/xend-config.sxp. Before with 2.6.31.6 I > had (network-script network-bridge) and also tried (network-script > ''network-bridge bridge=br0'') but these do not work with 2.6.32.12.I had this problem when I forgot to have ''CONFIG_BRIDGE'' enabled in my .config, and also CONFIG_TAP (but I think that was only used during guest startup) but I don''t think that is your problem. It could be related to this: "init: eucalyptus-network (eth0) main process (1156) killed by TERM signal" which might have mangled the eth0? Why is it being killed?> > However, there are still errors in the pv_ops dom0 2.6.32.12 console > output so I''m attaching the output so someone could see if they are > serious or if there are workarounds to improve things. I''m seeing > things like ''unable to locate IOAPIC for xxx'', call trace fromDon''t worry about that. These are used to setup the GSI and there is a second code path that does that.> enlighten.c, ''d0 domain attempted wrmsr'', ''Detected 1226681.732 MHz > processor.''(a 1.2 TeraHz processor??? - the processor is actually a 3.1 > GHz processor), ''No compatible ACPI _PSS objects found.''.Interesting. My AMD prototype board shows the same data (or sometimes even higher number)- completly bogus.> > Plus, why do I see slightly different outputs on the consoles? Some > errors only show on one of the consoles but not the other.That is b/c the Xen console (all prefixed with XEN) shouldn''t by default be in the Linux domain, unless requested. .. snip..> (XEN) Command line: dummy=dummy dom0_mem=1024M vga=text-80x50 loglvl=all guest_loglvl=all sync_console console_to_rin1^''g'' or unless you use console_to_ring at which point all of the output should be synced together. Except that you have ''1'' at the end instead of ''g''. .. snip..> GR: now login prompt shows up immediately:Hurrayy!> > Ubuntu lucid (development branch) grp-01-23-02 hvc0 > > grp-01-23-02 login:_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-May-10 16:03 UTC
Re: [Xen-devel] AMD Phenom II 940: mm/vmalloc.c:110 vmap_page_range_noflush
On 05/10/2010 10:10 AM, Konrad Rzeszutek Wilk wrote:>> Ok, I tried to adjust bridge parameters and found that I can finally get >> pv_ops dom0 to boot in normal timeframe if I comment out all bridge >> related statements in /etc/xen/xend-config.sxp. Before with 2.6.31.6 I >> had (network-script network-bridge) and also tried (network-script >> ''network-bridge bridge=br0'') but these do not work with 2.6.32.12. >> > I had this problem when I forgot to have ''CONFIG_BRIDGE'' enabled in my > .config, and also CONFIG_TAP (but I think that was only used during > guest startup) but I don''t think that is your problem. It could be related to > this: > > "init: eucalyptus-network (eth0) main process (1156) killed by TERM signal" > > which might have mangled the eth0? Why is it being killed? >I''m going to investigate this but I suspect it dies because eth0 isn''t there. The euca network works fine after I restart networking.> >> However, there are still errors in the pv_ops dom0 2.6.32.12 console >> output so I''m attaching the output so someone could see if they are >> serious or if there are workarounds to improve things. I''m seeing >> things like ''unable to locate IOAPIC for xxx'', call trace from >> > Don''t worry about that. These are used to setup the GSI and there is a > second code path that does that. >Ok. But then why bother writing these scary messages that just confuse things?> >> enlighten.c, ''d0 domain attempted wrmsr'', ''Detected 1226681.732 MHz >> processor.''(a 1.2 TeraHz processor??? - the processor is actually a 3.1 >> GHz processor), ''No compatible ACPI _PSS objects found.''. >> > Interesting. My AMD prototype board shows the same data (or sometimes > even higher number)- completly bogus. >I''m wondering if this bothers delay loop timings, etc. ???>> Plus, why do I see slightly different outputs on the consoles? Some >> errors only show on one of the consoles but not the other. >> > That is b/c the Xen console (all prefixed with XEN) shouldn''t by default > be in the Linux domain, unless requested. > .. snip.. > >> (XEN) Command line: dummy=dummy dom0_mem=1024M vga=text-80x50 loglvl=all guest_loglvl=all sync_console console_to_rin1 >> > ^''g'' > > or unless you use console_to_ring at which point all of the output > should be synced together. Except that you have ''1'' at the end instead > of ''g''. >The ''1'' is an artifact due to the command line actually being truncated. It''s actually the last character on the line.> .. snip.. > >> GR: now login prompt shows up immediately: >> > Hurrayy! >Yeah, no kidding! :-) Thanks for the help and looking at this. -Gerry>> Ubuntu lucid (development branch) grp-01-23-02 hvc0 >> >> grp-01-23-02 login: >> > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2010-May-10 16:17 UTC
[Xen-devel] AMD Phenom II 940: Upgrade to 2.6.32.12 fixes it and upgrades CPU from 3.1Ghz to 1.2Thz!
On Mon, May 10, 2010 at 12:03:09PM -0400, Gerry Reno wrote:> On 05/10/2010 10:10 AM, Konrad Rzeszutek Wilk wrote: >>> Ok, I tried to adjust bridge parameters and found that I can finally get >>> pv_ops dom0 to boot in normal timeframe if I comment out all bridge >>> related statements in /etc/xen/xend-config.sxp. Before with 2.6.31.6 I >>> had (network-script network-bridge) and also tried (network-script >>> ''network-bridge bridge=br0'') but these do not work with 2.6.32.12. >>> >> I had this problem when I forgot to have ''CONFIG_BRIDGE'' enabled in my >> .config, and also CONFIG_TAP (but I think that was only used during >> guest startup) but I don''t think that is your problem. It could be related to >> this: >> >> "init: eucalyptus-network (eth0) main process (1156) killed by TERM signal" >> >> which might have mangled the eth0? Why is it being killed? >> > > I''m going to investigate this but I suspect it dies because eth0 isn''t > there. The euca network works fine after I restart networking.Uh, why isn''t eth0 there? The kernel log looks to have ''eth0'' setup. Did it get renamed?> > >> >>> However, there are still errors in the pv_ops dom0 2.6.32.12 console >>> output so I''m attaching the output so someone could see if they are >>> serious or if there are workarounds to improve things. I''m seeing >>> things like ''unable to locate IOAPIC for xxx'', call trace from >>> >> Don''t worry about that. These are used to setup the GSI and there is a >> second code path that does that. >> > Ok. But then why bother writing these scary messages that just confuse > things?Well, you know.. job security and such :-) But in all seriousness - I was thinking about doing something about those pesky messages, but haven''t yet come up with a good way of doing it.> > >> >>> enlighten.c, ''d0 domain attempted wrmsr'', ''Detected 1226681.732 MHz >>> processor.''(a 1.2 TeraHz processor??? - the processor is actually a 3.1Maybe you should look in a lead case. You know at that speeds your CPU might be producing X-rays that could be harmful to you.>>> GHz processor), ''No compatible ACPI _PSS objects found.''. >>> >> Interesting. My AMD prototype board shows the same data (or sometimes >> even higher number)- completly bogus. >> > I''m wondering if this bothers delay loop timings, etc. ???Dan, thoughts?> > >>> Plus, why do I see slightly different outputs on the consoles? Some >>> errors only show on one of the consoles but not the other. >>> >> That is b/c the Xen console (all prefixed with XEN) shouldn''t by default >> be in the Linux domain, unless requested. >> .. snip.. >> >>> (XEN) Command line: dummy=dummy dom0_mem=1024M vga=text-80x50 loglvl=all guest_loglvl=all sync_console console_to_rin1 >>> >> ^''g'' >> >> or unless you use console_to_ring at which point all of the output >> should be synced together. Except that you have ''1'' at the end instead >> of ''g''. >> > The ''1'' is an artifact due to the command line actually being truncated. > It''s actually the last character on the line.Ah, OK.> > > >> .. snip.. >> >>> GR: now login prompt shows up immediately: >>> >> Hurrayy! >> > > Yeah, no kidding! :-) > > Thanks for the help and looking at this.Of course. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Dan Magenheimer
2010-May-10 16:40 UTC
[Xen-devel] RE: AMD Phenom II 940: Upgrade to 2.6.32.12 fixes it and upgrades CPU from 3.1Ghz to 1.2Thz!
> >>> enlighten.c, ''d0 domain attempted wrmsr'', ''Detected 1226681.732 MHz > >>> processor.''(a 1.2 TeraHz processor??? - the processor is actually a > 3.1 > > I''m wondering if this bothers delay loop timings, etc. ??? > > Dan, thoughts?This info is obtained from Xen via the shared_info struct, so I''d bet the shared_info struct is getting trashed. Or, for awhile, Jeremy had some code that made it possible for pvclock to use multiple shared_info structs to detect TSC skew. I think that got pulled for 4.0, but not sure I remember why (or the symptoms)... and I''m not sure what Xen bits you are testing with.> -----Original Message----- > From: Konrad Wilk > Sent: Monday, May 10, 2010 10:17 AM > To: Gerry Reno; Dan Magenheimer > Cc: xen-devel@lists.xensource.com > Subject: AMD Phenom II 940: Upgrade to 2.6.32.12 fixes it and upgrades > CPU from 3.1Ghz to 1.2Thz! > > On Mon, May 10, 2010 at 12:03:09PM -0400, Gerry Reno wrote: > > On 05/10/2010 10:10 AM, Konrad Rzeszutek Wilk wrote: > >>> Ok, I tried to adjust bridge parameters and found that I can > finally get > >>> pv_ops dom0 to boot in normal timeframe if I comment out all bridge > >>> related statements in /etc/xen/xend-config.sxp. Before with > 2.6.31.6 I > >>> had (network-script network-bridge) and also tried (network-script > >>> ''network-bridge bridge=br0'') but these do not work with 2.6.32.12. > >>> > >> I had this problem when I forgot to have ''CONFIG_BRIDGE'' enabled in > my > >> .config, and also CONFIG_TAP (but I think that was only used during > >> guest startup) but I don''t think that is your problem. It could be > related to > >> this: > >> > >> "init: eucalyptus-network (eth0) main process (1156) killed by TERM > signal" > >> > >> which might have mangled the eth0? Why is it being killed? > >> > > > > I''m going to investigate this but I suspect it dies because eth0 > isn''t > > there. The euca network works fine after I restart networking. > > Uh, why isn''t eth0 there? The kernel log looks to have ''eth0'' setup. > Did > it get renamed? > > > > > >> > >>> However, there are still errors in the pv_ops dom0 2.6.32.12 > console > >>> output so I''m attaching the output so someone could see if they are > >>> serious or if there are workarounds to improve things. I''m seeing > >>> things like ''unable to locate IOAPIC for xxx'', call trace from > >>> > >> Don''t worry about that. These are used to setup the GSI and there is > a > >> second code path that does that. > >> > > Ok. But then why bother writing these scary messages that just > confuse > > things? > > Well, you know.. job security and such :-) > > But in all seriousness - I was thinking about doing something about > those pesky messages, but haven''t yet come up with a good way of doing > it. > > > > > > >> > >>> enlighten.c, ''d0 domain attempted wrmsr'', ''Detected 1226681.732 MHz > >>> processor.''(a 1.2 TeraHz processor??? - the processor is actually a > 3.1 > > Maybe you should look in a lead case. You know at that speeds your > CPU might be producing X-rays that could be harmful to you. > > >>> GHz processor), ''No compatible ACPI _PSS objects found.''. > >>> > >> Interesting. My AMD prototype board shows the same data (or > sometimes > >> even higher number)- completly bogus. > >> > > I''m wondering if this bothers delay loop timings, etc. ??? > > Dan, thoughts? > > > > > > >>> Plus, why do I see slightly different outputs on the consoles? > Some > >>> errors only show on one of the consoles but not the other. > >>> > >> That is b/c the Xen console (all prefixed with XEN) shouldn''t by > default > >> be in the Linux domain, unless requested. > >> .. snip.. > >> > >>> (XEN) Command line: dummy=dummy dom0_mem=1024M vga=text-80x50 > loglvl=all guest_loglvl=all sync_console console_to_rin1 > >>> > >> > ^''g'' > >> > >> or unless you use console_to_ring at which point all of the output > >> should be synced together. Except that you have ''1'' at the end > instead > >> of ''g''. > >> > > The ''1'' is an artifact due to the command line actually being > truncated. > > It''s actually the last character on the line. > > Ah, OK. > > > > > > > >> .. snip.. > >> > >>> GR: now login prompt shows up immediately: > >>> > >> Hurrayy! > >> > > > > Yeah, no kidding! :-) > > > > Thanks for the help and looking at this. > > Of course._______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Gerry Reno
2010-May-10 17:40 UTC
Re: [Xen-devel] RE: AMD Phenom II 940: Upgrade to 2.6.32.12 fixes it and upgrades CPU from 3.1Ghz to 1.2Thz!
"...and I''m not sure what Xen bits you are testing with." I''m using Xen 4.0.0-rc8. Kernel is 2.6.32.12. -Gerry On 05/10/2010 12:40 PM, Dan Magenheimer wrote:>>>>> enlighten.c, ''d0 domain attempted wrmsr'', ''Detected 1226681.732 MHz >>>>> processor.''(a 1.2 TeraHz processor??? - the processor is actually a >>>>> >> 3.1 >> >>> I''m wondering if this bothers delay loop timings, etc. ??? >>> >> Dan, thoughts? >> > This info is obtained from Xen via the shared_info struct, so > I''d bet the shared_info struct is getting trashed. > > Or, for awhile, Jeremy had some code that made it possible > for pvclock to use multiple shared_info structs to detect > TSC skew. I think that got pulled for 4.0, but not sure > I remember why (or the symptoms)... and I''m not sure what > Xen bits you are testing with. > > >> -----Original Message----- >> From: Konrad Wilk >> Sent: Monday, May 10, 2010 10:17 AM >> To: Gerry Reno; Dan Magenheimer >> Cc: xen-devel@lists.xensource.com >> Subject: AMD Phenom II 940: Upgrade to 2.6.32.12 fixes it and upgrades >> CPU from 3.1Ghz to 1.2Thz! >> >> On Mon, May 10, 2010 at 12:03:09PM -0400, Gerry Reno wrote: >> >>> On 05/10/2010 10:10 AM, Konrad Rzeszutek Wilk wrote: >>> >>>>> Ok, I tried to adjust bridge parameters and found that I can >>>>> >> finally get >> >>>>> pv_ops dom0 to boot in normal timeframe if I comment out all bridge >>>>> related statements in /etc/xen/xend-config.sxp. Before with >>>>> >> 2.6.31.6 I >> >>>>> had (network-script network-bridge) and also tried (network-script >>>>> ''network-bridge bridge=br0'') but these do not work with 2.6.32.12. >>>>> >>>>> >>>> I had this problem when I forgot to have ''CONFIG_BRIDGE'' enabled in >>>> >> my >> >>>> .config, and also CONFIG_TAP (but I think that was only used during >>>> guest startup) but I don''t think that is your problem. It could be >>>> >> related to >> >>>> this: >>>> >>>> "init: eucalyptus-network (eth0) main process (1156) killed by TERM >>>> >> signal" >> >>>> which might have mangled the eth0? Why is it being killed? >>>> >>>> >>> I''m going to investigate this but I suspect it dies because eth0 >>> >> isn''t >> >>> there. The euca network works fine after I restart networking. >>> >> Uh, why isn''t eth0 there? The kernel log looks to have ''eth0'' setup. >> Did >> it get renamed? >> >>> >>> >>>> >>>>> However, there are still errors in the pv_ops dom0 2.6.32.12 >>>>> >> console >> >>>>> output so I''m attaching the output so someone could see if they are >>>>> serious or if there are workarounds to improve things. I''m seeing >>>>> things like ''unable to locate IOAPIC for xxx'', call trace from >>>>> >>>>> >>>> Don''t worry about that. These are used to setup the GSI and there is >>>> >> a >> >>>> second code path that does that. >>>> >>>> >>> Ok. But then why bother writing these scary messages that just >>> >> confuse >> >>> things? >>> >> Well, you know.. job security and such :-) >> >> But in all seriousness - I was thinking about doing something about >> those pesky messages, but haven''t yet come up with a good way of doing >> it. >> >> >>> >>> >>>> >>>>> enlighten.c, ''d0 domain attempted wrmsr'', ''Detected 1226681.732 MHz >>>>> processor.''(a 1.2 TeraHz processor??? - the processor is actually a >>>>> >> 3.1 >> >> Maybe you should look in a lead case. You know at that speeds your >> CPU might be producing X-rays that could be harmful to you. >> >> >>>>> GHz processor), ''No compatible ACPI _PSS objects found.''. >>>>> >>>>> >>>> Interesting. My AMD prototype board shows the same data (or >>>> >> sometimes >> >>>> even higher number)- completly bogus. >>>> >>>> >>> I''m wondering if this bothers delay loop timings, etc. ??? >>> >> Dan, thoughts? >> >> >>> >>> >>>>> Plus, why do I see slightly different outputs on the consoles? >>>>> >> Some >> >>>>> errors only show on one of the consoles but not the other. >>>>> >>>>> >>>> That is b/c the Xen console (all prefixed with XEN) shouldn''t by >>>> >> default >> >>>> be in the Linux domain, unless requested. >>>> .. snip.. >>>> >>>> >>>>> (XEN) Command line: dummy=dummy dom0_mem=1024M vga=text-80x50 >>>>> >> loglvl=all guest_loglvl=all sync_console console_to_rin1 >> >>>>> >>>> >> ^''g'' >> >>>> or unless you use console_to_ring at which point all of the output >>>> should be synced together. Except that you have ''1'' at the end >>>> >> instead >> >>>> of ''g''. >>>> >>>> >>> The ''1'' is an artifact due to the command line actually being >>> >> truncated. >> >>> It''s actually the last character on the line. >>> >> Ah, OK. >> >>> >>> >>> >>>> .. snip.. >>>> >>>> >>>>> GR: now login prompt shows up immediately: >>>>> >>>>> >>>> Hurrayy! >>>> >>>> >>> Yeah, no kidding! :-) >>> >>> Thanks for the help and looking at this. >>> >> Of course. >> > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Jeremy Fitzhardinge
2010-May-10 17:56 UTC
Re: [Xen-devel] RE: AMD Phenom II 940: Upgrade to 2.6.32.12 fixes it and upgrades CPU from 3.1Ghz to 1.2Thz!
On 05/10/2010 09:40 AM, Dan Magenheimer wrote:>>>>> enlighten.c, ''d0 domain attempted wrmsr'', ''Detected 1226681.732 MHz >>>>> processor.''(a 1.2 TeraHz processor??? - the processor is actually a >>>>> >> 3.1 >> >>> I''m wondering if this bothers delay loop timings, etc. ??? >>> >> Dan, thoughts? >> > This info is obtained from Xen via the shared_info struct, so > I''d bet the shared_info struct is getting trashed. > > Or, for awhile, Jeremy had some code that made it possible > for pvclock to use multiple shared_info structs to detect > TSC skew.I had a patch for multiple pvclock structures so that they could be exported to userspace, but I screwed up the Xen side so that it was trashing memory on context switch. But the use of pvclock in usermode is fairly iffy anyway, since there are concerns about how to attain the monotonicity guarantees required by clock_gettime, etc. So at the moment, neither Xen nor the .32+ kernels have support for that. J _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel