public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Tvrtko A. Ursulin" <tvrtko@ursulin.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Pavel Machek <pavel@ucw.cz>,
	linux-pm@lists.linux-foundation.org,
	kernel list <linux-kernel@vger.kernel.org>,
	Tobias Diedrich <ranma+kernel@tdiedrich.de>,
	Ayaz Abdulla <aabdulla@nvidia.com>
Subject: Re: Resume after hibernation regression in 2.6.29
Date: Thu, 26 Mar 2009 22:01:03 +0000	[thread overview]
Message-ID: <200903262201.03931.tvrtko@ursulin.net> (raw)
In-Reply-To: <200903262235.29576.rjw@sisk.pl>

On Thursday 26 March 2009 21:35:29 Rafael J. Wysocki wrote:
> On Thursday 26 March 2009, Pavel Machek wrote:
> > On Thu 2009-03-26 20:55:23, Tvrtko A. Ursulin wrote:
> > > On Thursday 26 March 2009 20:18:40 Pavel Machek wrote:
> > > > On Thu 2009-03-26 19:20:32, Tvrtko A. Ursulin wrote:
> > > > > Hi guys,
> > > > > I have been running custom compiled 2.6.28.7 in OpenSUSE 11.1 and
> > > > > using hiberation/resume daily as configured by the distro.
> > > > > Yesterday I upgraded to 2.6.29 (make oldconfig from 2.6.28.7,
> > > > > attached) and after resume networking (at least) does not work.
> > > > > Reboot at this point takes very long because of timeouts on CIFS
> > > > > and whatelse.
> > > > >
> > > > > Below is how /var/log/messagess looks for one cycle
> > > > > (hibernate-resume-reboot) and I am also attaching kernel config and
> > > > > /var/log/pm-suspend.log.
> > > > >
> > > > > You will probably notice evil nvidia.ko in there but don't panic,
> > > > > it all happens without it as well. Tested from runlevel 3 and by
> > > > > running pm-hibernate. After resume from that NIC LEDs were off. I
> > > > > tried /etc/init.d/network restart but that hung so I ^C and tried
> > > > > rmmod forcedeth && modprobe forcedeth && ifup eth0 and after some
> > > > > time network went live again. Haven't had time to test further
> > > > > though, so this is all pretty rough.
> > > >
> > > > Ok, can you try to rmmod forcedeth before hibernation, then insmod it
> > > > after resume?
> > >
> > > Sure, after insmod and /etc/init.d/network start following resume
> > > network was fine. Guess I could kludge that sequence into pm scripts
> > > somehow but would rather avoid that since it slows down the cycle and
> > > would make scripts non-stock.
> >
> > Ok, I guess you need to talk to forcedeth maintainers then... sounds
> > like a forcedeth problem to me.
>
> I have a box with forcedeth somewhere here, I should be able to check that
> in the next few days.

Not a lot activity in forcedeth.c from 2.6.28 to 2.6.29 so I will CC two guys 
who commited changes in that period. Ayaz, Tobias, forcedeth does not seem to 
come up after hibernation well for me. Actual hardware is:

00:0f.0 Ethernet controller: nVidia Corporation MCP73 Ethernet (rev a2)

Anything more I can do just shout!

Tvrtko




  reply	other threads:[~2009-03-26 22:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200903261920.32173.tvrtko@ursulin.net>
2009-03-26 20:18 ` Resume after hibernation regression in 2.6.29 Pavel Machek
2009-03-26 20:55   ` Tvrtko A. Ursulin
2009-03-26 21:14     ` Pavel Machek
2009-03-26 21:35       ` Rafael J. Wysocki
2009-03-26 22:01         ` Tvrtko A. Ursulin [this message]
2009-03-26 22:38           ` Pavel Machek
2009-03-26 23:04             ` Tvrtko A. Ursulin
2009-03-26 23:08               ` Rafael J. Wysocki
2009-03-27  8:01                 ` Tvrtko A. Ursulin
2009-03-27 11:55                   ` Rafael J. Wysocki
2009-03-27 20:09                     ` [Regression in 2.6.29] forcedeth doesn't work after resume from hibernation (was: Re: Resume after hibernation regression in 2.6.29) Rafael J. Wysocki
2009-03-29  8:03                       ` Tvrtko A. Ursulin
2009-04-03 10:23                         ` Tvrtko Ursulin
2009-04-03 15:24                       ` Ed Swierk
2009-04-03 17:41                         ` Ed Swierk
2009-04-03 20:26                           ` Rafael J. Wysocki
2009-04-04 13:04                           ` Tvrtko A. Ursulin
2009-04-04 13:07                             ` Rafael J. Wysocki
2009-03-27  8:39           ` Resume after hibernation regression in 2.6.29 Tobias Diedrich
     [not found] <ck4dD-3ce-35@gated-at.bofh.it>
     [not found] ` <ck4dD-3ce-33@gated-at.bofh.it>
     [not found]   ` <ck504-4x8-13@gated-at.bofh.it>
2009-03-27  4:35     ` Robby Workman

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=200903262201.03931.tvrtko@ursulin.net \
    --to=tvrtko@ursulin.net \
    --cc=aabdulla@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=pavel@ucw.cz \
    --cc=ranma+kernel@tdiedrich.de \
    --cc=rjw@sisk.pl \
    /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