From: "Riccardo" <andrighetto.riccardo@gmail.com>
To: kvm@vger.kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: Gentoo guest with smp: emerge freeze while recompile world
Date: Fri, 21 May 2010 18:47:05 +0200 [thread overview]
Message-ID: <20100521164533.M78490@gmail.com> (raw)
In-Reply-To: <201005211135.36592.iggy@theiggy.com>
---------- Original Message -----------
From: Brian Jackson <iggy@theiggy.com>
To: "Riccardo" <andrighetto.riccardo@gmail.com>
Cc: kvm@vger.kernel.org
Sent: Fri, 21 May 2010 11:35:36 -0500
Subject: Re: Gentoo guest with smp: emerge freeze while recompile world
> On Friday, May 21, 2010 10:46:10 am Riccardo wrote:
> > ---------- Original Message -----------
> > From: Avi Kivity <avi@redhat.com>
> > To: Riccardo <andrighetto.riccardo@gmail.com>
> > Cc: kvm@vger.kernel.org
> > Sent: Fri, 21 May 2010 18:21:20 +0300
> > Subject: Re: Gentoo guest with smp: emerge freeze while recompile world
> >
> > > On 05/21/2010 04:16 PM, Riccardo wrote:
> > > > ...
> > > >
> > > >> There are almost impossible to debug.
> > > >>
> > > >> Try copying vmlinux out of your guest and attach with gdb when it
> > > >> hangs. Then issue the command
> > > >>
> > > >> (gdb) thread apply all backtrace
> > > >>
> > > >> to see what the guest is doing.
> > > >
> > > > panic.
> > > > ------- End of Original Message -------
> > > >
> > > > Hi,
> > > > I compile gentoo-sources-2.6.31-r10 and with this kernel "emerge -e
> > > > world" complete without errors!
> > >
> > > Interesing. Can you so a git bisect to see where it stops working?
> >
> > Ehm sorry I don't understand the request have you a link?
> >
> > > > I always use the same .config
> > > >
> > > > After I try gentoo-sources-2.6.34 and vanilla-sources-2.6.34 but the
> > > > problem remain, the compile freeze and I see this in ps -elf:
> > > >
> > > > 5 S root 1013 1 0 76 -4 - 3125 poll_s 13:00 ?
> > > > 00:00:00 /sbin/udevd --daemon
> > > > 1 S root 2669 1 0 80 0 - 7523 wait 13:00 ?
> > > > 00:00:00 supervising syslog-ng
> > > > 5 S root 2670 2669 0 80 0 - 7556 poll_s 13:00 ?
> > > > 00:00:00 /usr/sbin/syslog-ng
> > > > 1 S root 3258 1 0 80 0 - 9505 poll_s 13:00 ?
> > > > 00:00:00 /usr/sbin/sshd
> > > > 1 S root 3378 1 0 80 0 - 4115 hrtime 13:00 ?
> > > > 00:00:00 /usr/sbin/cron
> > > > 0 S root 3446 1 0 80 0 - 1493 n_tty_ 13:00 tty2
> > > > 00:00:00 /sbin/agetty 38400 tty2 linux
> > > > 0 S root 3447 1 0 80 0 - 1493 n_tty_ 13:00 tty3
> > > > 00:00:00 /sbin/agetty 38400 tty3 linux
> > > > 0 S root 3448 1 0 80 0 - 1493 n_tty_ 13:00 tty4
> > > > 00:00:00 /sbin/agetty 38400 tty4 linux
> > > > 0 S root 3449 1 0 80 0 - 1493 n_tty_ 13:00 tty5
> > > > 00:00:00 /sbin/agetty 38400 tty5 linux
> > > > 0 S root 3450 1 0 80 0 - 1493 n_tty_ 13:00 tty6
> > > > 00:00:00 /sbin/agetty 38400 tty6 linux
> > > > 5 S root 3457 1 0 80 0 - 5959 poll_s 13:00 ?
> > > > 00:00:00 SCREEN -S sb1
> > > > 4 S root 3458 3457 0 80 0 - 4454 wait 13:00 pts/0
> > > > 00:00:00 -/bin/bash
> > > > 4 S root 3462 3458 0 75 -5 - 45171 poll_s 13:00 pts/0
> > > > 00:00:34 /usr/bin/python2.6 /usr/bin/emerge -e world
> > > > 4 S root 3613 1 0 80 0 - 14014 wait 13:01 tty1
> > > > 00:00:00 /bin/login --
> > > > 4 S root 3953 3613 0 80 0 - 4429 n_tty_ 13:01 tty1
> >
> > 00:00:00 -bash
> >
> > > > 0 S root 6614 3462 0 75 -5 - 972 wait 14:26 pts/0
> > > > 00:00:00 [dev-util/pkgconfig-0.23] sandbox
> > > > "/usr/lib64/portage/bin/ebuild.sh" compile 4 S root 6615 6614
> > > > 0 75 -5 - 6362 wait 14:26 pts/0 00:00:00 /bin/bash
> > > > /usr/lib64/portage/bin/ebuild.sh compile
> > > > 5 S root 6646 6615 0 75 -5 - 6745 wait 14:26 pts/0
> > > > 00:00:00 /bin/bash /usr/lib64/portage/bin/ebuild.sh compile
> > > > 4 S root 13235 6646 0 75 -5 - 3651 wait 14:27 pts/0
> > > > 00:00:00 make -j8
> > > > 4 S root 13238 13235 0 75 -5 - 3652 wait 14:27 pts/0
> > > > 00:00:00 make all-recursive
> > > > 4 S root 13239 13238 0 75 -5 - 5956 wait 14:27 pts/0
> > > > 00:00:00 /bin/sh -c set fnord $MAKEFLAGS; amf=$2; \?dot_seen=no;
> > > > \?target=`echo all-recursive | sed s/-recursive//`; \?list=
> > > > 5 S root 13243 13239 0 75 -5 - 5956 wait 14:27 pts/0
> > > > 00:00:00 /bin/sh -c set fnord $MAKEFLAGS; amf=$2; \?dot_seen=no;
> > > > \?target=`echo all-recursive | sed s/-recursive//`; \?list=
> > > > 4 S root 13244 13243 0 75 -5 - 3686 wait 14:27 pts/0
> > > > 00:00:00 make all
> > > > 4 S root 13358 13244 0 75 -5 - 3684 wait 14:27 pts/0
> > > > 00:00:00 make all-recursive
> > > > 4 S root 13359 13358 0 75 -5 - 5956 wait 14:27 pts/0
> > > > 00:00:00 /bin/sh -c set fnord $MAKEFLAGS; amf=$2; \?dot_seen=no;
> > > > \?target=`echo all-recursive | sed s/-recursive//`; \?list=
> > > > 5 S root 16546 13359 0 75 -5 - 5956 wait 14:28 pts/0
> > > > 00:00:00 /bin/sh -c set fnord $MAKEFLAGS; amf=$2; \?dot_seen=no;
> > > > \?target=`echo all-recursive | sed s/-recursive//`; \?list=
> > > > 4 S root 16547 16546 0 75 -5 - 3652 wait 14:28 pts/0
> > > > 00:00:00 make all
> > > > 4 S root 16548 16547 0 75 -5 - 3652 n_tty_ 14:28 pts/0
> > > > 00:00:00 make all-am
> > > > 4 S root 16599 3258 0 80 0 - 17937 poll_s 15:07 ?
> > > > 00:00:00 sshd: root@pts/2
> > > > 4 S root 16602 16599 0 80 0 - 4429 wait 15:07 pts/2
> > > > 00:00:00
> >
> > -bash
> >
> > > > 4 R root 16611 16602 0 80 0 - 3698 - 15:08 pts/2
> > > > 00:00:00
> >
> > ps -elf
> >
> > > > 1 S root 31506 2 0 80 0 - 0 bdi_wr 14:25 ?
> > > > 00:00:00 [flush-253:0]
> > > >
> > > > All in wait?
> > >
> > > Maybe a block driver problem? Are you using virtio?
> >
> > Yes, I always used virtio.
> > In the server the kernel is sys-kernel/gentoo-sources-2.6.33
> > and in dmesg I see this new lines about clock?:
> > [ 885.500098] CE: hpet increasing min_delta_ns to 15000 nsec
> > [ 1354.020020] CE: hpet increasing min_delta_ns to 22500 nsec
> > [ 2657.777387] hrtimer: interrupt took 7542 ns
> > [ 7148.533547] CE: hpet increasing min_delta_ns to 33750 nsec
>
> If you are using kvm-clock, maybe try disabling that.
>
$ cat /sys/devices/system/clocksource/clocksource0/current_clocksource
hpet
This is from server, not from VM (that have freeze).
> >
> > > > After this test I reboot in 2.6.31-r10 and I complete emerge -e world
> >
> > succefully.
> >
> > > > The problem show always with all kernels>=2.6.32
> > > > I have setup something wrong in kernel? I post the .config in the
> > > > previous
> >
> > email.
> >
> > > It should work for all .configs.
> >
> > Thanks for your checks.
> >
> > ------- End of Original Message -------
> > Now I have leave the VM freeze.
> > If you can debug I can send you the data for connect to the VM.
> >
> > Riccardo
> > --
> > To unsubscribe from this list: send the line "unsubscribe kvm" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
------- End of Original Message -------
next prev parent reply other threads:[~2010-05-21 16:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 8:33 Gentoo guest with smp: emerge freeze while recompile world Riccardo
2010-05-19 16:25 ` Avi Kivity
2010-05-19 17:49 ` Alexander Graf
2010-05-21 14:11 ` Riccardo
[not found] ` <20100521130924.M32603@gmail.com>
2010-05-21 15:21 ` Avi Kivity
2010-05-21 15:46 ` Riccardo
2010-05-21 16:35 ` Brian Jackson
2010-05-21 16:47 ` Riccardo [this message]
2010-05-23 11:38 ` Avi Kivity
2010-05-23 12:12 ` Riccardo
2010-05-23 13:30 ` Avi Kivity
2010-05-23 21:15 ` Riccardo
2010-05-25 9:09 ` Avi Kivity
2010-05-22 14:32 ` Riccardo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100521164533.M78490@gmail.com \
--to=andrighetto.riccardo@gmail.com \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox