Thomas Hellstrom wrote:
> Hi, Daniel,
>
> It appears you and Thierry are guilty to this:
>
> d56f57ac969c7818986a0c78025740399e49f3a9
Looks like Jongman Heo did also report this issue [1][2].
> Could you please revert the vmwgfx-specific parts of that commit before
> 4.5 GA?
>
> Thanks,
> Thom
On Mon, Mar 07, 2016 at 02:51:10PM +0100, Thomas Hellstrom wrote:
> Hi, Daniel,
>
> It appears you and Thierry are guilty to this:
>
> d56f57ac969c7818986a0c78025740399e49f3a9
>
> Could you please revert the vmwgfx-specific parts of that commit before
> 4.5 GA?
Indeed, that hunk looks completel
get+0x11f/0x200
> [ 15.384249] [] ? __fget+0x5/0x200
> [ 15.385760] [] SyS_ioctl+0x79/0x90
> [ 15.387296] [] entry_SYSCALL_64_fastpath+0x12/0x76
> [ 15.389246] Code: Bad RIP value.
> [ 15.390375] RIP [< (null)>] (null)
> [ 15.391992] RSP
RSP
[ 15.393081] CR2:
[ 15.394174] ---[ end trace f9f3f138ca13da13 ]---
On 02/29/2016 10:38 PM, Sebastian Herbszt wrote:
> Hello,
>
> I get a boot hang with vmwgfx on 4.5-rc6 (4.5.0-rc6-1.gb239884-default from
> openSUSE). This happens on VMware Player 5.0.2.
> Same V
Hello,
I get a boot hang with vmwgfx on 4.5-rc6 (4.5.0-rc6-1.gb239884-default from
openSUSE). This happens on VMware Player 5.0.2.
Same VM works fine with kernel 4.4 but on 4.5-rc6 it hangs with
[drm] Initialized vmwgfx 2.9.0 20150810 for :00:0f.0 on minor 0
I am able to boot the system
