From: Pavel Machek <pavel@ucw.cz>
To: Thomas Fjellstrom <tfjellstrom@shaw.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Possible Suspend to Ram bug?
Date: Wed, 15 Jul 2009 02:04:17 +0200 [thread overview]
Message-ID: <20090715000417.GB1552@ucw.cz> (raw)
In-Reply-To: <200907150545.14867.tfjellstrom@shaw.ca>
On Wed 2009-07-15 05:45:14, Thomas Fjellstrom wrote:
> On Wed July 15 2009, Jiri Kosina wrote:
> > On Wed, 15 Jul 2009, Thomas Fjellstrom wrote:
> > > I'll try with debian's 2.6.30 first. But there's a small issue with
> > > that, .30 and .31 seem to have some performance regressions according to
> > > sites like phoronix.
> >
> > You know, there are lies, then horrible lies, then benchmarks, and
> > benchmarks done wrong.
> >
> > Just do your own measurements under your particular workload, and if you
> > see any performance regression, just report it.
>
> The benchmarks they run are pretty much what I'd do to test, so I'd more than
> likely get the same results, and waste a bunch of time.
So rather you expect us to waste a bunch of time?
> 2.6.30 did seem to fix the ssd error. but the first time I suspended, my r8169
> decided to flip out. I had to rmmod and modprobe it to get the network back
> up.
>
> [ 867.780034] ------------[ cut here ]------------
> [ 867.780165] WARNING: at
> /home/blank/debian/kernel/tmp/linux-2.6-2.6.30/debian/build/source_amd64_none/net/sched/sch_generic.c:226
> dev_watchdog+0xc7/0x164()
> [ 867.780373] Hardware name: GA-MA790FXT-UD5P
> [ 867.780488] NETDEV WATCHDOG: eth1 (r8169): transmit timed out
> [ 867.780610] Modules linked in: nvidia(P) powernow_k8 cpufreq_conservative
> cpufreq_stats cpufreq_userspace cpufreq_powersave nfsd exportfs nfs lockd
> fscache nfs_acl auth_rpcgss sunrpc it87 hwmon_vid adt7473 firewire_sbp2 loop
> snd_hda$
> [ 867.785472] Pid: 0, comm: swapper Tainted: P
....and some more.
> At this point I was getting repeated "link up" messages and even though
> ifconfig said the network was up, there was no actual connectivity. as
> mentioned only rmmod+modprobe of r8169 fixed the problem. It doesn't seem to
> happen often though.
Reproduce it without taints, then youu can report a regression in network...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-07-15 15:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 10:58 Thomas Fjellstrom
2009-07-14 10:17 ` Thomas Fjellstrom
2009-07-14 15:53 ` Jiri Kosina
2009-07-15 9:59 ` Thomas Fjellstrom
2009-07-15 11:31 ` Jiri Kosina
2009-07-15 11:45 ` Thomas Fjellstrom
2009-07-15 0:04 ` Pavel Machek [this message]
2009-07-16 22:53 ` Thomas Fjellstrom
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=20090715000417.GB1552@ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=tfjellstrom@shaw.ca \
/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®