All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dâniel Fraga" <fragabr@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: bugme-daemon@bugzilla.kernel.org, netdev@vger.kernel.org,
	Ayaz Abdulla <aabdulla@nvidia.com>
Subject: Re: [Bugme-new] [Bug 10487] New: NIC (forcedeth) doesn't work with suspend (S3)
Date: Sun, 20 Apr 2008 20:16:18 -0300	[thread overview]
Message-ID: <20080420201618.0c9c10a0@tux> (raw)
In-Reply-To: <20080420152135.d2c45887.akpm@linux-foundation.org>

On Sun, 20 Apr 2008 15:21:35 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:

> No, that's not right.  Please tell us the latest version of the kernel
> which worked OK.

	No versions worked. Since I acquired this motherboard (Asus
M2N-E), I couldn't suspend because of the NIC.

	Is there any test I can do to help you figure it out what's
happening? Thanks.

-- 

      reply	other threads:[~2008-04-20 23:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-10487-10286@http.bugzilla.kernel.org/>
2008-04-20 22:21 ` [Bugme-new] [Bug 10487] New: NIC (forcedeth) doesn't work with suspend (S3) Andrew Morton
2008-04-20 23:16   ` Dâniel Fraga [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=20080420201618.0c9c10a0@tux \
    --to=fragabr@gmail.com \
    --cc=aabdulla@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.