Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 12 Jul 2013 18:01:59 +0900
From:      "Lundberg, Johannes" <johannes@brilliantservice.co.jp>
To:        Kevin Oberman <rkoberman@gmail.com>
Cc:        "freebsd-x11@freebsd.org" <freebsd-x11@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: FreeBSD-head hang when shutdown by ACPI with Intel GPU and new Xorg and SandyBridge
Message-ID:  <CAASDrVm3eNYMvpJ-bCGve9Yq3ZgzNNYP5cD-0zFjrBTKfM6D-g@mail.gmail.com>
In-Reply-To: <CAN6yY1vZmHAGy=R-MyP71bh-H4npvfRKSUPNrBnh3-2GHurs3Q@mail.gmail.com>
References:  <1601171.hWXcdG7J9D@notebook.alkar.net> <CAN6yY1vZmHAGy=R-MyP71bh-H4npvfRKSUPNrBnh3-2GHurs3Q@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
> As the KMS code does not switch the display mode back, once X with KMS
starts, you can't get a console back.

Is there any solution for this in the works?

Johannes Lundberg
BRILLIANTSERVICE CO., LTD. <http://www.brilliantservice.co.jp>;


On Wed, May 22, 2013 at 5:44 AM, Kevin Oberman <rkoberman@gmail.com> wrote:

> On Tue, May 21, 2013 at 12:50 PM, Artyom Mirgorodskiy <
> artyom.mirgorodsky@gmail.com> wrote:
>
> > Hi
> > More than a month I can not shutdown FreeBSD on my laptop correctly when
> > running Xorg with Intel GPU. However reboot work correctly. Shutdown work
> > fine if I choose Vesa driver in xorg.conf. So I can run with intel, then
> > edit xorg.conf, kill Xorg server and shutdown correctly. If I shut down
> > immediately after loading Xorg - everything is fine too.
> > Without the text console is difficult to provide any information :( Why
> > would still not recover mode when kill Xorg?
> >
> > PS
> > I try to disable RC6 states -without any changes.
> > FreeBSD shutdown correctly before January.
> >
>
> I am seeing similar issues on my Sandybridge running Xorg with KMS, but I
> see it on 9-Stable.
>
> The main difference between shutdown and reboot is that shutdown goes
> through the rc.d files and issues a 'stop' for each. reboot simply kills
> running processes, first by sending SIGTERM and then sending SIGKILL to
> those that still live. So something is failing to die and that "something"
> is probably X. The system still responds to ICMP ECHOREQUEST (i.e. ping),
> but I can't fire up an ssh session.
>
> As the KMS code does not switch the display mode back, once X with KMS
> starts, you can't get a console back.
>
> Since the system is deadlocked in this state, I suspect something bad is
> happening in the KMS code that leaves the system hung.
>
> I may try to run a firewire console. Never tried it, but it should work.
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAASDrVm3eNYMvpJ-bCGve9Yq3ZgzNNYP5cD-0zFjrBTKfM6D-g>