From: Andrew Morton <akpm@linux-foundation.org>
To: fragabr@gmail.com
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 15:21:35 -0700 [thread overview]
Message-ID: <20080420152135.d2c45887.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-10487-10286@http.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
> On Sun, 20 Apr 2008 00:06:07 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=10487
>
> Summary: NIC (forcedeth) doesn't work with suspend (S3)
> Product: Power Management
> Version: 2.5
> KernelVersion: 2.6.25
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: high
> Priority: P1
> Component: Hibernation/Suspend
> AssignedTo: power-management_other@kernel-bugs.osdl.org
> ReportedBy: fragabr@gmail.com
>
>
> Latest working kernel version: 2.6.25
No, that's not right. Please tell us the latest version of the kernel
which worked OK.
> Earliest failing kernel version: all
> Distribution: Linux from scratch
> Hardware Environment: Athlon64 x2 (x86-64), Asus M2N-E
> Software Environment:
> Problem Description:
>
> When I use s2ram to suspend to ram, everything works, except the network
> (forcedeth) that doesn't come back from suspend. So I have to reboot the
> machine.
>
> Steps to reproduce:
>
> 1) s2ram
>
> 2) then wake up from suspend
>
> 3) network isn't working anymore
>
>
next parent reply other threads:[~2008-04-20 22:21 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 ` Andrew Morton [this message]
2008-04-20 23:16 ` [Bugme-new] [Bug 10487] New: NIC (forcedeth) doesn't work with suspend (S3) Dâniel Fraga
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=20080420152135.d2c45887.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aabdulla@nvidia.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=fragabr@gmail.com \
--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.