public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Steve French <smfrench@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: current mainline doesn't boot
Date: Fri, 17 Oct 2014 18:44:45 -0500	[thread overview]
Message-ID: <20141017234445.GA28891@saruman> (raw)
In-Reply-To: <CAH2r5mvBOJHLbRXHMt50E97_1E2Q8F_=PH9=u6N3yuuqSQVmDg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 737 bytes --]

Hi,

On Fri, Oct 17, 2014 at 05:44:02PM -0500, Steve French wrote:
> Anyone know a workaround for the problem booting current mainline?
> 3.17 works fine for me, but recent mainline since 3.17 goes to a black
> screen near the end of boot as X is about to start.
> 
> I also tried the Ubuntu build of the day (which also is based on
> current mainline but with the Ubuntu config just in case it was some
> driver issue) which fails the same way.

you need to provide more information, here are a few queries which might
help:

1. which architecture ?
2. Can you get a serial console to get some dmesg output ?
3. after screen is black, can you ctrl + alt + F1 and get a console ?
4. where's you .config ?

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-10-17 23:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17 22:44 current mainline doesn't boot Steve French
2014-10-17 23:44 ` Felipe Balbi [this message]
2014-10-17 23:52   ` Steve French
2014-10-18 21:52     ` Steve French
2014-10-19  2:02       ` Steve French
2014-10-24 16:13         ` current mainline doesn't boot on VWware platform Dmitry Torokhov
2014-10-24 17:34           ` Ravindra Kumar
2014-10-27  8:30           ` Thomas Hellstrom
2014-10-19  6:17     ` current mainline doesn't boot Mike Galbraith

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=20141017234445.GA28891@saruman \
    --to=balbi@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smfrench@gmail.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