public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Nicolas Dichtel <nicolas.dichtel@6wind.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Issues with "x86, um: switch to generic fork/vfork/clone" commit
Date: Sat, 19 Jan 2013 06:38:08 +0000	[thread overview]
Message-ID: <20130119063808.GN4939@ZenIV.linux.org.uk> (raw)
In-Reply-To: <50F3D2F2.3080200@6wind.com>

On Mon, Jan 14, 2013 at 10:42:10AM +0100, Nicolas Dichtel wrote:
> Hi,
> 
> I'm running a virtual host (kvm/qemu x86 32 bits 16 CPUs, debian
> wheezy) over a x86 64bits target.
> The virtual host has problem during the boot with recent kernels
> (sometimes, daemons crash, but not always, and not always the same
> daemon). Here is an example:
> [    2.150274] input: ImExPS/2 Generic Explorer Mouse as
> /devices/platform/i8042/serio1/input/input3
> udevd[468]: timeout: killing 'firmware.agent' [587]
> 
> udevd[468]: 'firmware.agent' [587] terminated by signal 9 (Killed)
> 
> done.
> 
> [snip]
> 
> [   64.313636] kbd[2563]: segfault at 9fe ip 000009fe sp b758293c
> error 4 in dash[8048000+18000]
> 
> After bisecting, the following commit seems responsible:
> 1d4b4b2994b5fc208963c0b795291f8c1f18becf (x86, um: switch to generic
> fork/vfork/clone)

Er...  Bisect of the guest kernel, I take it?  Could you check if building
the guest !SMP affects anything?

  reply	other threads:[~2013-01-19  6:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14  9:42 Issues with "x86, um: switch to generic fork/vfork/clone" commit Nicolas Dichtel
2013-01-19  6:38 ` Al Viro [this message]
2013-01-20  3:12   ` Al Viro
2013-01-20 20:53     ` Linus Torvalds
2013-01-20 21:28       ` Al Viro
2013-01-21  1:22       ` Al Viro
2013-01-21  1:40         ` Linus Torvalds
2013-01-21  2:30           ` Al Viro
2013-01-21  2:39             ` Linus Torvalds
2013-01-21  6:02               ` Al Viro
2013-01-21 22:55             ` [RFC] making HAVE_SYSCALL_WRAPPERS universal (Re: Issues with "x86, um: switch to generic fork/vfork/clone" commit) Al Viro
2013-01-22 12:47               ` James Hogan
2013-01-22 14:23                 ` Al Viro
2013-01-22 13:16               ` Arnd Bergmann
2013-01-22 15:33               ` Arnd Bergmann
2013-01-21  9:00     ` Issues with "x86, um: switch to generic fork/vfork/clone" commit Nicolas Dichtel
  -- strict thread matches above, loose matches on Subject: below --
2012-11-10  4:36 Michel Lespinasse
2012-11-10  4:51 ` Al Viro
2012-11-10  4:57   ` Michel Lespinasse
2012-11-10  5:33     ` Al Viro
2012-11-10  5:47       ` Michel Lespinasse
2012-11-10  7:33         ` Al Viro
2012-11-10  8:08           ` Michel Lespinasse
2012-11-10 18:59           ` Al Viro

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=20130119063808.GN4939@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    /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