Bug 111877
| Summary: | rawhide 2.6 kernel unresponsive | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Raw Hide | Reporter: | Behdad Esfahbod <behdad> |
| Component: | kernel | Assignee: | Dave Jones <davej> |
| Status: | CLOSED RAWHIDE | QA Contact: | Brian Brock <bbrock> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 1.0 | CC: | mingo, pfrields |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 2.6.1-1.43 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-01-18 09:11:26 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
I see it fixed in 2.6.1-1.43. Closing. |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031114 Epiphany/1.0.4 Description of problem: Tested with this kernel, with vanilla test11, and vanilla test11 with preemption enabled; all three give the same results to my simple test: Open up a gnome terminal. Maximize it. Do some ls, blah, ... to fill the screen with characters. Now start selecting some text and while holding down the mouse button, start moving the pointer in a circlur path. Now fasten your movement and see how unresponsive is the selection following the pointer. Even my geyes do not respond (follow the pointer) while I'm moving the cursor a bit fast. Do the same with 2.4 kernel and you feel no latency. Version-Release number of selected component (if applicable): kernel-2.6.0-0.test11.1.9 How reproducible: Always Steps to Reproduce: 1. Read description above. 2. 3. Actual Results: unresponsive Expected Results: no delay should be felt. Additional info: I do not remember such a problem back around 2.6.0-test5 or so, but I may be wrong. BTW, I hope this is solved upstream, otherwise it's an stopper IMO.