Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 20 Jun 2013 21:26:23 +0300
From:      Konstantin Belousov <kostikbel@gmail.com>
To:        Bengt Ahlgren <bengta@sics.se>
Cc:        freebsd-acpi@freebsd.org
Subject:   Re: AMT console
Message-ID:  <20130620182623.GL91021@kib.kiev.ua>
In-Reply-To: <uh7a9mkabkx.fsf@P142.sics.se>
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> <uh7a9mkabkx.fsf@P142.sics.se>

next in thread | previous in thread | raw e-mail | index | archive | help

--YNUuthOiC1RHZCCs
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Jun 20, 2013 at 08:20:14PM +0200, Bengt Ahlgren wrote:
> Konstantin Belousov <kostikbel@gmail.com> writes:
>=20
> > 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:
> >> >=20
> >> > > On Thursday, June 13, 2013 10:00:21 am Ganael LAPLANCHE wrote:
> >> > >> Hi,
> >> > >>=20
> >> > >> As you may know, suspend/resume has been broken on Lenovo x220 fo=
r a
> >> > >> long time now, see :
> >> > >>=20
> >> > >> http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/174504
> >> > >>=20
> >> > >> I have been able to do a suspend(S3)/resume operation in text mod=
e (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 co=
llect
> >> > >> 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?
> >> >=20
> >> > Does the console via AMT otherwise work for you?
> >> >=20
> >> > I'm trying to set up AMT as the console on a TP X201.  I got the ser=
ial
> >> > 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:
> >> >=20
> >> > uart2: <Non-standard ns8250 class UART with FIFOs> port
> >> > 0x1808-0x180f mem 0xf2524000-0xf2524fff irq 17 at device 22.3 on
> >> > pci0
> >> >=20
> >> > uart2@pci0:0:22:3: class=3D0x070002 card=3D0x216217aa chip=3D0x3b678=
086
> >> > rev=3D0x06 hdr=3D0x00
> >> >     vendor     =3D 'Intel Corporation'
> >> >     device     =3D '5 Series/3400 Series Chipset KT Controller'
> >> >     class      =3D simple comms
> >> >     subclass   =3D UART
> >> >     bar   [10] =3D type I/O Port, range 32, base 0x1808, size  8, en=
abled
> >> >     bar   [14] =3D type Memory, range 32, base 0xf2524000, size 4096=
, enabled
> >> >     cap 01[c8] =3D powerspec 3  supports D0 D3  current D0
> >> >     cap 05[d0] =3D MSI supports 1 message, 64 bit=20
> >> >=20
> >> > I've set:
> >> >=20
> >> > hint.uart.2.flags=3D"0x10"
> >> > console=3D"comconsole"
> >> >=20
> >> > in /boot/loader.conf, but the loader just hangs after printing:
> >> >=20
> >> > Loading /boot/defaults/loader.conf
> >> >=20
> >> > 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?
> >>=20
> >> You should use
> >> comconsole_pcidev=3D0:0:22:3
> > Oops,
> > comconsole_pcidev=3D0:22:3
>=20
> No difference, I'm afraid.  The port does not show up here either:
>=20
> # sysctl kern.console
> kern.console: ttyv0,dcons,/dcons,ttyv0,ucom,
Obviously, you did not specified console=3Dcomconsole ?

>=20
> Forgot to tell, but this is a 9.1-REL-p3/amd64 system running GENERIC.
>=20
> (I wanted to set up the console for KMS shutdown and resume debugging.)



--YNUuthOiC1RHZCCs
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (FreeBSD)

iQIcBAEBAgAGBQJRw0lOAAoJEJDCuSvBvK1B+lIP/3cKgZOBy5m0zFCG2FKdJtb7
w7TSu2aCnEUiqrnQlgtCP+W0DGBfzw3Ej3Q8/M07BPhJspB6As7JoNerM4LPx7YW
8Nq2okTQpumHiYvR+SZNyZTZzbrK8H9Jv6Y/fPB7d1XrHP82t7MX5IRLRxld3lHa
4j2BHPI1DQYc/dfnZQpJ5CTfd/lx/tX728m8vE1+i6ccZfvLuHcbKluold1zMNLJ
TA73cAP5xFw8DxgIzQp8REi4g93zj99M9DvVD6PqSTELmEigqIhAheVMuwKpAWZS
Be6uVtHEg7uXcOjKR2sWp3DlidemQJDJy1gTCNE4FxjM6ptSbDIRoPIJWaY/TBDX
AQxO+/Lq/v4uo0vwbH4YfYHyhx1oiS/Fx/5jDMVdlwPJ+W0of37y0NRW/f1l25zs
WHgZ5X3/HqwCc7x/Oooh0OXDI5CxrJDFFb09ujQzaVtvT8n/9NSE4vdvrJyj3hlO
oo3lQ2bHwpemHzsqX3MPp3+PEs1ZI8YciIvLu8FTqb7PL7qaIDprevefz9OzMWdk
fvXOTmmGEr6MuI8XfDbW3m0C/RzIXBWTzn5s3kDi16460622o6tlLC+Ks9Q9wm60
K1panIr+a2cPFJmpXlFaAUI1Yp0e5BgVRWj3+32qo8RZJZFrnxEyGydJX4BVAhmY
LfhOjmm8o8HMSCwV6MmG
=EZ62
-----END PGP SIGNATURE-----

--YNUuthOiC1RHZCCs--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130620182623.GL91021>