I have the same problem with karmic.
--
wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer)
https://bugs.launchpad.net/bugs/373245
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hello, this bug also affects me.
I'm running Jaunty with kernel 2.6.30-5candela on an Acer Aspire One.
According to xorg.log i'm using EXA.
If you need me to try anything I'm willing to do it.
Jim
--
wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer)
I did some testing with UXA and EXA (Not XAA) during jaunty with it's
kernels and .30 and it was still present. If it's in intel driver issue
then it's present in both EXA and UXA. UXA is currently the only
supported option with 2.8 afaik.
Andrew
--
wakeups kernel core :
Is everyone who is seeing this issue using an Intel graphics device and
using UXA?
I'm using Jaunty, with a 2.6.30 kernel (from the kernelteam PPA) and X
and Intel drivers from the xorg-updates PPA. (xserver-xorg-video-
intel=2.7.1). I also appear to see this issue (many interrupts) as
described
Thanks Samat, I would like to try this, but please could you clarify how to
enable XAA support? I've tried using
Option AccelMethod xaa
in my xorg.conf, but it seems to make no difference - the logs still show:
(II) UXA(0): Driver registered support for the following operations:
(II)
Sorry, just seen that XAA and EXA have been removed from Intel's 2.80
driver. From the release notes:
The driver now depends on X server 1.6 or later,
and eliminates several obsolete code paths, (XAA and EXA removed in
favor of UXA, DRI1 support eliminated).
I guess it really depends on how important battery life of notebooks is
for this release. I would anticipate that with the push on net books and
laptops it would be reasonably important.
The battery life has been slowly getting better since Hardy but it still
does make a significant difference.
I think part of the problem here is it seems to be a regression. I know;
for me at-least, when i was running Jaunty on my netbook i was seeing
6-7hr battery life. After upgrading to Karmic (with this bug present)
I'm seeing 4.5-5hr battery. Ideally I think we should be on-par with; or
better than,
I don't think i have ever gotten anywhere close to that especially
with Jaunty. 2.6.30 was probably the best kernel for the X200.
On Thu, Aug 27, 2009 at 11:50 PM, Jeff Utterjeffut...@sadclown.net wrote:
I think part of the problem here is it seems to be a regression. I know;
for me at-least,
Important for karmic. I guess this bug should be given high priority.
--
wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer)
https://bugs.launchpad.net/bugs/373245
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Still there on 2.6.31-6 Karmic. This bug cuts my netbook battery in
half.
--
wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer)
https://bugs.launchpad.net/bugs/373245
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
On 2.6.30.1, in powertop I get e.g.
30.0% (261.0) kernel core : hrtimer_start_range_ns (tick_sched_timer)
--
wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer)
https://bugs.launchpad.net/bugs/373245
You received this bug notification because you are a member of Ubuntu
Bugs,
This is still present in 2.6.31-33 in Karmic
--
wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer)
https://bugs.launchpad.net/bugs/373245
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Is there any thoughts / progress on this ? Do the developers need more
information ? If so how can we help ?
Willing to help in any way possible.
--
wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer)
https://bugs.launchpad.net/bugs/373245
You received this bug notification
Hello,
i am seeing the same behaviour, hrtimer_start_range_ns causes more than
2000 wakups:
87.4% (2002.0) kernel core : hrtimer_start_range_ns (tick_sched_timer)
7.6% (174.2) interrupt : ahci
1.3% ( 30.2) interrupt : iwlagn
1.2% ( 27.2) interrupt : acpi
0.7%
That specific commit was merged in 2.6.30-rc4 and so should be in karmic
kernels.
--
wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer)
https://bugs.launchpad.net/bugs/373245
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is not a bug in the linux-meta package, moving to the linux
package.
** Package changed: linux-meta (Ubuntu) = linux (Ubuntu)
--
wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer)
https://bugs.launchpad.net/bugs/373245
You received this bug notification because you are a
Yep, I talked to Matthew and it should definitely be in 2.6.30-rc7 in
karmic which is the kernel that I tested with. So either it's not the
issue which was addressed with that patch or the patch has not
completely resolved the issue.
--
wakeups kernel core : hrtimer_start_range_ns
Sorry my mistake , it's not the kernel that I filed the report with,
however it _is_ still present in 2.6.30-rc7.
--
wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer)
https://bugs.launchpad.net/bugs/373245
You received this bug notification because you are a member of Ubuntu
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=67405439bca28c4dbecd3fefd97fbdb282a302d9
--
wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer)
https://bugs.launchpad.net/bugs/373245
You received this bug notification because you are a member of Ubuntu
I did see this and was under the impression this was merged by Linus in
2.6.30-rc7. Is this not the case ? Should I try to apply this patch
manually ?
Many thanks
Andrew
--
wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer)
https://bugs.launchpad.net/bugs/373245
You received this
Bug #380303 may or may not be also related.
--
wakeups kernel core : hrtimer_start_range_ns (tick_sched_timer)
https://bugs.launchpad.net/bugs/373245
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
22 matches
Mail list logo
