Date: Thu, 20 Jun 2013 20:20:14 +0200 From: Bengt Ahlgren <bengta@sics.se> To: Konstantin Belousov <kostikbel@gmail.com> Cc: freebsd-acpi@freebsd.org Subject: Re: AMT console Message-ID: <uh7a9mkabkx.fsf@P142.sics.se> In-Reply-To: <20130620062901.GI91021@kib.kiev.ua> (Konstantin Belousov's message of "Thu, 20 Jun 2013 09:29:01 %2B0300") References: <20130613134922.M8280@martymac.org> <201306131016.57098.jhb@freebsd.org> <uh7fvwd4uac.fsf_-_@P142.sics.se> <20130620061619.GH91021@kib.kiev.ua> <20130620062901.GI91021@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Konstantin Belousov <kostikbel@gmail.com> writes: > On Thu, Jun 20, 2013 at 09:16:19AM +0300, Konstantin Belousov wrote: >> On Thu, Jun 20, 2013 at 12:20:27AM +0200, Bengt Ahlgren wrote: >> > John Baldwin <jhb@freebsd.org> writes: >> > >> > > On Thursday, June 13, 2013 10:00:21 am Ganael LAPLANCHE wrote: >> > >> Hi, >> > >> >> > >> As you may know, suspend/resume has been broken on Lenovo x220 for a >> > >> long time now, see : >> > >> >> > >> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/174504 >> > >> >> > >> I have been able to do a suspend(S3)/resume operation in text mode (it >> > >> works, but console stays dark at resume, I had to connect through ssh ; >> > >> also, resume hangs if X is started with i915kms.ko loaded) and collect >> > >> the following verbose logs : >> > > >> > > Interesting, I connected a serial console via AMT but wasn't able to get >> > > any output during resume. Is this with a stock kernel? >> > >> > Does the console via AMT otherwise work for you? >> > >> > I'm trying to set up AMT as the console on a TP X201. I got the serial >> > over LAN working using amtterm from another machine - verified with cu >> > on the tty (ttyu2) that typing on both ends shows up at the other end >> > before trying console redirection. The device is: >> > >> > uart2: <Non-standard ns8250 class UART with FIFOs> port >> > 0x1808-0x180f mem 0xf2524000-0xf2524fff irq 17 at device 22.3 on >> > pci0 >> > >> > uart2@pci0:0:22:3: class=0x070002 card=0x216217aa chip=0x3b678086 >> > rev=0x06 hdr=0x00 >> > vendor = 'Intel Corporation' >> > device = '5 Series/3400 Series Chipset KT Controller' >> > class = simple comms >> > subclass = UART >> > bar [10] = type I/O Port, range 32, base 0x1808, size 8, enabled >> > bar [14] = type Memory, range 32, base 0xf2524000, size 4096, enabled >> > cap 01[c8] = powerspec 3 supports D0 D3 current D0 >> > cap 05[d0] = MSI supports 1 message, 64 bit >> > >> > I've set: >> > >> > hint.uart.2.flags="0x10" >> > console="comconsole" >> > >> > in /boot/loader.conf, but the loader just hangs after printing: >> > >> > Loading /boot/defaults/loader.conf >> > >> > Any advice? Is uart2 unusable as a console? It does not say "flags >> > 0x10" in the device probe - does that mean it won't work? >> >> You should use >> comconsole_pcidev=0:0:22:3 > Oops, > comconsole_pcidev=0:22:3 No difference, I'm afraid. The port does not show up here either: # sysctl kern.console kern.console: ttyv0,dcons,/dcons,ttyv0,ucom, Forgot to tell, but this is a 9.1-REL-p3/amd64 system running GENERIC. (I wanted to set up the console for KMS shutdown and resume debugging.) Bengt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?uh7a9mkabkx.fsf>