Is this issue intel specific only? I am seeing it on Nvidia open source
driver (nouveau). Does the same code apply there as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1272338
Title:
Xorg
For me, this bug happened after I updated the BIOS on my Samsung Series
7 17.3 laptop. I had bought it last year and never updated the BIOS. I
went from P02 to P06 I think.
People who got their laptops with latest BIOS obviously had the bug all
along.
This is a classic case of Samsung screwing
Please leave the bug number for new bug here. TB has not been usable for
me for more than a week now, and I have been using alternatives. Someone
at TB development has messed up change management really badly!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Why was the change that introduced this issue not rolled back? Why not
make 16.0.3 release? How do we know we haven't gotten plethora of new
bugs with TB17?
Are you folks trying to kill off Thunderbird as an email client? This is
a widespread breakage and its killing servers with redundant
Does this patch apply clean to 16.0.2? Its disappointing that such a
critical fix hasn't been pushed to stable release yet...:(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1074260
Title:
Almost the same thing happens on my Dell Latitude E6510 using vanilla-
sources 2.6.38-rc4. Surprisingly, the regression was introduced with rc4
because I had rc3 earlier and resume from suspend worked, sort of (the
screen stayed dim, so I had to hit Fn-Auto (left arrow) to get the
screen to show
The sleep patch on top of rc7 solved it for me (I finally see my boot,
VTs are available, external monitor works, suspend/resume works(tried
few cycles)). I had spent so many hour fighting the external monitor
issue prior to hitting this bug, its not even funny. Thanks henk!
--
[arrandale]
This because of CONFIG_SCHED_DEBUG and CONFIG_SCHEDSTATS. Get rid of
these and wakeups shown in [kernel scheduler] Load balancing tick go
away. I just ran into by accident and compared my config with previous
version where I wasn't seeing this.
This was basically triggered by CONFIG_LATENCYTOP
Is this really a corner case bug or is it just the hardware?
I have had this happen to me with 3 different drives and the drives are
brand new and they work fine otherwise.
I have checked the cabling and I have the locked SATAII cables. All the
drives are SATAII and nothing in the system is
