From: Andrew Buehler <abuehler.kernel@gmail.com>
To: Kernel development list <linux-kernel@vger.kernel.org>
Subject: Thanks and congratulations for improved support
Date: Thu, 18 Aug 2011 23:54:16 -0400 [thread overview]
Message-ID: <4E4DDE68.6060308@gmail.com> (raw)
When I first got my current laptop and installed Linux on it - somewhere
between one and two years ago - there were a number of less than ideal
behaviors, which seem in hindsight to have potentially been
kernel-related. Wireless connections would bounce up and down at random
intervals (sometimes as little as a few seconds apart), suspending even
to RAM would take 15-45 seconds freezing processes and then another
10-15 suspending consoles, and connecting or unplugging a USB device
during the process of suspending would abort the suspend - this last,
apparently, because a new process was triggered which would not freeze.
I found workarounds for the wireless problems, got used to the suspend
slowness, and took an "if it hurts to do that, don't do that" approach
to the USB disconnect-while-suspending problem - and I kept going,
upgrading my kernel and various other software on a fairly regular
basis. After a while, I noticed that the time needed to suspend had gone
down; another while later, I noticed that my "stand on one leg and
whistle 'I Am My Own Grandpa' backwards" wireless workaround script
wasn't necessary anymore.
By now, suspending to RAM takes five seconds or less most of the time -
and just this past evening (coincidentally enough, not long after having
rebooted into kernel 3.0.0), I accidentally unplugged a USB mouse while
suspending, and was pleasantly surprised to find that the suspend did
not abort but completed without problems. As of this moment, as far as I
know, all of the various problems I've had with this laptop under Linux
are gone.
So I just wanted to take a moment to say: thank you for the fixes,
congratulations on the improvements, and keep up the good work!
--
Andrew J. Buehler
reply other threads:[~2011-08-19 3:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E4DDE68.6060308@gmail.com \
--to=abuehler.kernel@gmail.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox