From: Al Viro <viro@ZenIV.linux.org.uk>
To: Michel Lespinasse <walken@google.com>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Hugh Dickins <hughd@google.com>
Subject: Re: Issues with "x86, um: switch to generic fork/vfork/clone" commit
Date: Sat, 10 Nov 2012 05:33:34 +0000 [thread overview]
Message-ID: <20121110053334.GO2616@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CANN689GetguA+1bqKXC=Cq0SLcLqaqLsn5XGBZYVbWeBogX+zA@mail.gmail.com>
On Fri, Nov 09, 2012 at 08:57:58PM -0800, Michel Lespinasse wrote:
> On Fri, Nov 9, 2012 at 8:51 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> > On Fri, Nov 09, 2012 at 08:36:53PM -0800, Michel Lespinasse wrote:
> >> Hi,
> >>
> >> I'm having an issue booting current linux-next kernels on my test
> >> machines. Userspace crashes when it's supposed to pivot to the rootfs.
> >> With the loglevel=8 kernel parameter, the last messages I see are:
> >>
> >> Checking root filesystem in pivot_root init.
> >> [ 6.252717] usb 2-1: link qh256-0001/ffff880853ec9ab8 start 1 [1/0 us]
> >> [ 6.259419] hub 2-1:1.0: state 7 ports 8 chg 0000 evt 0000
> >> [ 6.292302] traps: hotplug[1633] general protection ip:f767c06b
> >> sp:ffbb2d1c error:0 in libc-2.3.6.so[f7652000+126000]
> >>
> >> I ran a bisection and it turns out that
> >> e52d03a3775841cc68d0ea9d86f2f09b603c41e6 (x86, um: switch to generic
> >> fork/vfork/clone) is the commit breaking my setup. When reverting
> >> that, I am able to boot linux-next (or mmotm, which is what I was
> >> trying to do in the first place) without issues.
> >>
> >> Sorry for not having a more complete root cause at the moment - I'm
> >> lacking some context as to what the change is trying to do.
> >
> > Hmm... 32bit native, presumably?
>
> This is running on a x86_64 system; I believe the userspace binaries
> should be 64-bit as well.
Curious... After the second look at that sucker, it seems that you have
32bit hotplug(8) in there, and yes, it's clearly a 64bit kernel... Could
you check which binary it is and whether it's really 32bit or not?
next prev parent reply other threads:[~2012-11-10 5:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 4:36 Issues with "x86, um: switch to generic fork/vfork/clone" commit Michel Lespinasse
2012-11-10 4:51 ` Al Viro
2012-11-10 4:57 ` Michel Lespinasse
2012-11-10 5:33 ` Al Viro [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2013-01-14 9:42 Nicolas Dichtel
2013-01-19 6:38 ` Al Viro
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 9:00 ` Nicolas Dichtel
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=20121110053334.GO2616@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=walken@google.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