Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

FreeBSD-head hang when shutdown by ACPI with Intel GPU and new Xorg and SandyBridge

3 views
Skip to first unread message

Artyom Mirgorodskiy

unread,
May 21, 2013, 3:51:15 PM5/21/13
to freebsd...@freebsd.org, freeb...@freebsd.org
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.

--
Artyom Mirgorodskiy
dmesg

Kevin Oberman

unread,
May 21, 2013, 4:44:30 PM5/21/13
to Artyom Mirgorodskiy, freeb...@freebsd.org, FreeBSD Current
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...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"

Lundberg, Johannes

unread,
Jul 12, 2013, 5:02:27 AM7/12/13
to Kevin Oberman, Artyom Mirgorodskiy, freeb...@freebsd.org, FreeBSD Current
> 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>

Lars Engels

unread,
Jul 12, 2013, 12:06:06 PM7/12/13
to David Chisnall, Kevin Oberman, freeb...@freebsd.org, FreeBSD Current, Lundberg, Johannes, Artyom Mirgorodskiy
On Fri, Jul 12, 2013 at 11:26:06AM +0100, David Chisnall wrote:
> On 12 Jul 2013, at 10:01, "Lundberg, Johannes" <joha...@brilliantservice.co.jp> wrote:
>
> >> 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?
>
> Yes. ray@ is currently being funded by the FreeBSD Foundation to
> improve Newcons compatibility with KMS. The Newcons framework is
> designed to improve layering in the console. The machine-dependent
> part simply provides a framebuffer interface, the machine-independent
> part provides the terminal emulator (this also means things like
> unicode in the console will work, as will higher-resolution consoles).
> It's currently used on a few non-x86 platforms, but it wasn't a
> priority for x86 because the PC BIOS text console mostly works and
> people who want a better terminal can just run X. It's now become a
> priority because of the KMS integration with X.org. Once this work is
> completed, we will switch to a new X.org by default and will use the
> KMS interface within the kernel for selecting the video mode.

Is there a rough ETA for this great improvement?

Aleksandr Rybalko

unread,
Jul 13, 2013, 4:12:42 PM7/13/13
to Lars Engels, Kevin Oberman, freeb...@freebsd.org, FreeBSD Current, David Chisnall
I hope first things to test will be available on begin of the August.
But it is just hope yet :)

Thanks.
--
Aleksandr Rybalko <r...@freebsd.org>
0 new messages