public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Dave Airlie <airlied@gmail.com>
Cc: Dave Airlie <airlied@linux.ie>, linux-kernel@vger.kernel.org
Subject: S3 resume and PNP (was: Re: S3 resume and serial console..)
Date: Sun, 31 Jul 2005 08:08:59 +0100	[thread overview]
Message-ID: <20050731080859.A5580@flint.arm.linux.org.uk> (raw)
In-Reply-To: <21d7e99705073017295ed29c64@mail.gmail.com>; from airlied@gmail.com on Sun, Jul 31, 2005 at 10:29:58AM +1000

On Sun, Jul 31, 2005 at 10:29:58AM +1000, Dave Airlie wrote:
> latest Linus git tree, and it just does the usual entering suspend and
> then when I resume I get crap out of the serial port, nothing at all
> intelliigble...
> 
> Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
> ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> 
> And as I said its an i865 based motherboard from Intel... nothing
> special on it, do you need to know the super-io chip, i.e. I 'll have
> to open the case to find out...

The above two messages tells me you're probably using plug'n'play.
Unfortunately, for some unknown reason, the Linux plug'n'play
subsystem does not support suspend/resume.  This is not a serial
problem.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2005-07-31  7:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-30  2:03 S3 resume and serial console Dave Airlie
2005-07-30  7:55 ` Russell King
2005-07-31  0:29   ` Dave Airlie
2005-07-31  7:08     ` Russell King [this message]
2005-07-31  7:44       ` S3 resume and PNP (was: Re: S3 resume and serial console..) Dave Airlie
2005-07-31  8:02         ` Dave Airlie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050731080859.A5580@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=airlied@gmail.com \
    --cc=airlied@linux.ie \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox