From: pk <peterk2@coolmail.se>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Extraordinarily laggy UI, keyboard, udev weirdness, KDE 4.5
Date: Sat, 14 Aug 2010 14:53:40 +0200 [thread overview]
Message-ID: <4C6691D4.2030402@coolmail.se> (raw)
In-Reply-To: <AANLkTi=Dq9yFYqa-pZ=aU9-tAyiiad3CwxEtNE+7U4=b@mail.gmail.com>
On 2010-08-14 10:36, Paul Hartman wrote:
> I downgraded to kernel 2.6.34.3 and everything runs smoothly again. No
> more hangs or sluggishness. It would seem that something in 2.6.35
> series kernels does not like my computer, or something in my computer
> does not like 2.6.35 series kernels.
Not sure if this is related (esp. since you have an nvidia card using
proprietary drivers) but it may provide some insights to your problem:
https://bugzilla.kernel.org/show_bug.cgi?id=16265
Best regards
Peter K
next prev parent reply other threads:[~2010-08-14 13:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 16:24 [gentoo-user] Extraordinarily laggy UI, keyboard, udev weirdness, KDE 4.5 Paul Hartman
2010-08-12 16:30 ` Thomas Yao
2010-08-12 16:44 ` [gentoo-user] " Nikos Chantziaras
2010-08-12 17:12 ` Paul Hartman
2010-08-13 4:33 ` Paul Hartman
2010-08-14 8:36 ` Paul Hartman
2010-08-14 12:53 ` pk [this message]
2010-09-23 22:52 ` Paul Hartman
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=4C6691D4.2030402@coolmail.se \
--to=peterk2@coolmail.se \
--cc=gentoo-user@lists.gentoo.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