On Fri, Sep 07, 2007 at 08:49:49AM -0400, Godmar Back wrote:
> For completeness, and to help people googling for this particular
> error, I'd like to briefly report the outcome of my investigation. I'm
> happy to report (if a bit embarrassed) that operator error was to
> blame. That piece of code I
For completeness, and to help people googling for this particular
error, I'd like to briefly report the outcome of my investigation. I'm
happy to report (if a bit embarrassed) that operator error was to
blame. That piece of code I had added was in fact executed, and it led
to a deadlock when UML lo
Still on the subject of UML hanging after VFS: mount, related to my
earlier email (*), I've been trying to dig deeper into what causes the
hang. When UML hangs, I observe the main thread idling, and 3 threads
being blocked in either io_getevents, read, or poll. The thread stuck
in read, in particul
guest kernel
on RHEL5 with 2.6.18 (host).
Scott.
-Original Message-
From: Godmar Back [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 05, 2007 10:18 AM
To: Mills, Scott (CAR:2V62)
Cc: user-mode-linux-user@lists.sourceforge.net
Subject: Re: [uml-user] hang after VFS: Mounted root (
Scott,
2.6.22.5 appears to already contain this patch. FWIW, here is the
startup output:
Checking that ptrace can change system call numbers...OK
Checking syscall emulation patch for ptrace...OK
Checking advanced syscall emulation patch for ptrace...OK
Checking for tmpfs mount on /dev/shm...OK
Ch
ck
Sent: Wednesday, September 05, 2007 9:13 AM
To: user-mode-linux-user@lists.sourceforge.net
Subject: Re: [uml-user] hang after VFS: Mounted root (ext3 filesystem)
readonly.
I'm not intending to swamp this list, but I'd like to share some
additional information about this hanging issue
I'm not intending to swamp this list, but I'd like to share some
additional information about this hanging issue. At the time when UML
hangs, there are four threads running in it.
Below, I'm providing their stack traces as shown by gdb:
#0 0x081963eb in __nanosleep_nocancel () at include/net/soc
Some additional information about this issue.
http://user-mode-linux.sourceforge.net/new/problems.html#vdso says to
disable CONFIG_COMPAT_VDSO on the host. According to Ingo Molnar
himself, disabling CONFIG_COMPAT_VDSO (http://lwn.net/Articles/184734/
) means that VDSO is not always at the usual 0
