All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Hellstrom <thellstrom@vmware.com>
To: Steve French <smfrench@gmail.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>, <balbi@ti.com>,
	LKML <linux-kernel@vger.kernel.org>, <ravindrakumar@vmware.com>,
	<akataria@vmware.com>
Subject: Re: current mainline doesn't boot on VWware platform
Date: Mon, 27 Oct 2014 09:30:31 +0100	[thread overview]
Message-ID: <544E02A7.6080005@vmware.com> (raw)
In-Reply-To: <20141024161354.GB19933@dtor-ws>

Hi!

Thanks for forwarding. There is a bug on redhat bugzilla

https://bugzilla.redhat.com/show_bug.cgi?id=1155825

that might be related, but from what I can tell, the possible deadlock
reported there is only hypothetical.

/Thomas


On 10/24/2014 06:13 PM, Dmitry Torokhov wrote:
> Hi Steve,
>
> On Sat, Oct 18, 2014 at 09:02:15PM -0500, Steve French wrote:
>> Interesting to see that Fedora has similar problems with current
>> kernel (I pulled mainline again a few hours ago).
>>
>> Fedora 20 x86_64 in vmware boots to logon prompt but no mouse, no
>> keyboard, system hung.  Ctl-alt-f1 doesn't do anything.  Even with
>> verbose on kernel boot line, the extra debug messages have all been
>> cleared by the time the hang occurs so nothing useful displayed.
>>
>> To be as safe as possible I used their default .config
>> /boot/config-3.16.6-200.fc20.x86_64 to do a clean build of mainline.
>> Once again, 3.16 and 3.17 work but not current mainline.
> Let's add a few VMware people. I am pretty sure they'd be interested in
> why it does not work.
>
> Guys, could you please route as appropriate.
>
> Thanks.
>
>> On Sat, Oct 18, 2014 at 4:52 PM, Steve French <smfrench@gmail.com> wrote:
>>> Same thing happened after pulling newly updated mainline kernel
>>> changes a few minutes ago.
>>>
>>> Black screen on boot just when you would expect x to be starting.
>>> Hung. Ctl-alt-F1 doesn't do anything.
>>>
>>> arch is x86_64.
>>>
>>> 3.17.1 works.  When I get time I will see if I can figure out more
>>> useful info but this looks like a pretty boring setup:
>>>
>>> sfrench@ubuntu:~$ glxinfo | grep -i "vendor"
>>> server glx vendor string: SGI
>>> client glx vendor string: Mesa Project and SGI
>>> OpenGL vendor string: VMware, Inc.
>>> sfrench@ubuntu:~$ grep LoadModule /var/log/Xorg.0.log
>>> [    18.271] (II) LoadModule: "glx"
>>> [    18.288] (II) LoadModule: "vmware"
>>> [    18.352] (II) LoadModule: "modesetting"
>>> [    18.355] (II) LoadModule: "fbdev"
>>> [    18.360] (II) LoadModule: "vesa"
>>> [    18.369] (II) LoadModule: "fbdevhw"
>>> [    18.372] (II) LoadModule: "fb"
>>> [    18.379] (II) LoadModule: "dri2"
>>> [    18.479] (II) LoadModule: "evdev"
>>> [    18.484] (II) LoadModule: "vmmouse"
>>>
>>> On Fri, Oct 17, 2014 at 6:52 PM, Steve French <smfrench@gmail.com> wrote:
>>>> This is vmware guest
>>>>
>>>> sfrench@ubuntu:~/xfstests$ cat /proc/cpuinfo
>>>> processor    : 0
>>>> vendor_id    : GenuineIntel
>>>> cpu family    : 6
>>>> model        : 70
>>>> model name    : Intel(R) Core(TM) i7-4750HQ CPU @ 2.00GHz
>>>>
>>>> (and using 64 bit kernel build) ...
>>>>
>>>> I don't have the Ubuntu config for their mainline kernel test builds
>>>> any more (deleted the kernel since it didn't work) but they post their
>>>> .config diffs at
>>>> https://urldefense.proofpoint.com/v1/url?u=http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=l5Ago9ekmVFZ3c4M6eauqrJWGwjf6fTb%2BP3CxbBFkVM%3D%0A&m=wp7Vk7bzPRuHbjuXgvt6xD%2F5rYqFnHiHkWIbhmFC%2FM8%3D%0A&s=4e9068baa1dd8756d9843bd41f3568505198d273fe6d15fa2cf666c844f601cf
>>>>
>>>> I could not get to a console so assumed it died in kernel as x was
>>>> coming up.  I will have to reinstall current mainline to see if I can
>>>> hook up a serial console (I had maximum kernel boot verbose in the
>>>> grub.cfg but nothing interesting before the black screen)
>>>>
>>>> On Fri, Oct 17, 2014 at 6:44 PM, Felipe Balbi <balbi@ti.com> wrote:
>>>>> 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
>>>>
>>>>
>>>> --
>>>> Thanks,
>>>>
>>>> Steve
>>>
>>>
>>> --
>>> Thanks,
>>>
>>> Steve
>>
>>
>> -- 
>> Thanks,
>>
>> Steve
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  https://urldefense.proofpoint.com/v1/url?u=http://vger.kernel.org/majordomo-info.html&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=l5Ago9ekmVFZ3c4M6eauqrJWGwjf6fTb%2BP3CxbBFkVM%3D%0A&m=wp7Vk7bzPRuHbjuXgvt6xD%2F5rYqFnHiHkWIbhmFC%2FM8%3D%0A&s=21dbd5ec2e156ce4853d5ce9152289dc4475e1ea039790635ea0cd635312c820
>> Please read the FAQ at  https://urldefense.proofpoint.com/v1/url?u=http://www.tux.org/lkml/&k=oIvRg1%2BdGAgOoM1BIlLLqw%3D%3D%0A&r=l5Ago9ekmVFZ3c4M6eauqrJWGwjf6fTb%2BP3CxbBFkVM%3D%0A&m=wp7Vk7bzPRuHbjuXgvt6xD%2F5rYqFnHiHkWIbhmFC%2FM8%3D%0A&s=154e0c0abab99c1124e5b456fa05bf421d973a3bd69a2e71a3aec89085bf2765


  parent reply	other threads:[~2014-10-27  8:30 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
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 [this message]
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=544E02A7.6080005@vmware.com \
    --to=thellstrom@vmware.com \
    --cc=akataria@vmware.com \
    --cc=balbi@ti.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ravindrakumar@vmware.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.