From: emisca <emisca.ml@gmail.com>
To: "Stefan Seyfried" <seife@suse.de>
Cc: "Pavel Machek" <pavel@ucw.cz>,
suspend2-users@lists.suspend2.net,
suspend-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [Suspend-devel] asus p5ld2 se, serial port gone after suspend and i8042 problems (solved, pnpacpi=off needed)
Date: Fri, 12 Jan 2007 12:11:49 +0100 [thread overview]
Message-ID: <414cba4e0701120311t39d90e10y472f251f8e357643@mail.gmail.com> (raw)
In-Reply-To: <20070111195812.GF11903@suse.de>
But using pnpacpi=no, I disable the acpi code.. the "normal" pnp code,
what does on suspend? Does it simply do nothing? In the dmesg I don't
see anything related to pnp device reinit.
I tried suspend to ram on this motherboard. A strange thing happens..
the system goes to suspend and then suddenly resumes. Why?
How I can check if it's enabled a wake up device? There are no related
settings on the bios, only wake on lan (disabled). I think I must
debug interrupts...
2007/1/11, Stefan Seyfried <seife@suse.de>:
> On Thu, Jan 11, 2007 at 02:14:42PM +0100, emisca wrote:
> > Yes, I have to look at pnpacpi code... but does the dsdt matters for this
> > problem?
> > Surely, it is a bios bug (as usually.....). I will look at pnpacpi code.
>
> Not necessarily. IIRC, somebody (Rusty?) said that serial consoles have had
> problems with suspend for a long time and just sometimes work "by accident".
> ISTR that they do not really save and restore the line settings etc.
>
> So it does not need to be the BIOS, it can also be a plain broken driver.
>
> --
> Stefan Seyfried
> QA / R&D Team Mobile Devices | "Any ideas, John?"
> SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
>
prev parent reply other threads:[~2007-01-12 11:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <414cba4e0701101409w4be38105vae7d185f4c2967bd@mail.gmail.com>
2007-01-11 11:42 ` Pavel Machek
2007-01-11 13:17 ` emisca
[not found] ` <414cba4e0701110514t2fbd0659g905aa2fb06b9a261@mail.gmail.com>
2007-01-11 19:58 ` Stefan Seyfried
2007-01-12 11:11 ` emisca [this message]
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=414cba4e0701120311t39d90e10y472f251f8e357643@mail.gmail.com \
--to=emisca.ml@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=seife@suse.de \
--cc=suspend-devel@lists.sourceforge.net \
--cc=suspend2-users@lists.suspend2.net \
/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
all inboxes | Powered by JetHome®