From: Thierry Reding <thierry.reding@avionic-design.de>
To: Alan Cox <alan@linux.intel.com>
Cc: Ian Abbott <abbotti@mev.co.uk>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Ian Abbott <ian.abbott@mev.co.uk>,
lkml <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: Oops after merge of tty-next
Date: Fri, 27 Jul 2012 09:16:34 +0200 [thread overview]
Message-ID: <20120727071634.GA29885@avionic-0098.mockup.avionic-design.de> (raw)
In-Reply-To: <20120724230527.2135198e@bob.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]
On Tue, Jul 24, 2012 at 11:05:27PM +0100, Alan Cox wrote:
> On Mon, 23 Jul 2012 15:51:03 +0100
> Ian Abbott <abbotti@mev.co.uk> wrote:
>
> > On 2012-07-21 23:41, Alan Cox wrote:
> > > On Fri, 20 Jul 2012 23:07:06 +0100
> > > Ian Abbott <abbotti@mev.co.uk> wrote:
> > >
> > >> I'm getting an Oops in the linux-next tree today after the merge
> > >> of the remote-tracking branch 'tty/tty-next'. I bisected it down
> > >> to commit 36b3c070d2346c890d690d71f6eab02f8c511137 in
> > >> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git :
>
> Ok Greg you can you leave that one in -next but not push it for 3.6.
>
> I need to go over this in some detail and figure out the remaining
> race, and worse yet how to fix it without the mess of existing locks
> turning it into something nasty.
>
> I think I understand what is needed but I don't want to be doing it as
> a mad panic for 3.6. On the bright side I think it explains the other
> tty lock splitting mysteries.
I've also been able to reproduce this, or at least a very similar issue,
on ARM (Tegra). The system boots into the initrd, which works as usual,
but it hangs when executing the switch_root that starts systemd within
the final root filesystem. With the above-mentioned commit reverted, the
system successfully boots to the login prompt.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-07-27 7:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 22:07 Oops after merge of tty-next Ian Abbott
2012-07-21 22:41 ` Alan Cox
2012-07-23 14:51 ` Ian Abbott
2012-07-24 9:58 ` Alan Cox
2012-07-24 22:05 ` Alan Cox
2012-07-27 7:16 ` Thierry Reding [this message]
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=20120727071634.GA29885@avionic-0098.mockup.avionic-design.de \
--to=thierry.reding@avionic-design.de \
--cc=abbotti@mev.co.uk \
--cc=alan@linux.intel.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=ian.abbott@mev.co.uk \
--cc=linux-kernel@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