[Bug 329616] Re: Multiple instances of xfdesktop started simultaneously

2009-05-11 Thread Christian Siefkes
I had the same problem, after updating to Jaunty my system became
practically unusable. I just removed 69 files from the ~/.cache/sessions
directory.

-- 
Multiple instances of xfdesktop started simultaneously
https://bugs.launchpad.net/bugs/329616
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 272669] Re: [INTREPID] 965GM gives a wrong screen resolution on laptop used with an external display

2008-11-07 Thread Christian Siefkes
I have the same problem after updating to Xubuntu Intrepid.

My laptop is a Thinkpad 61s with an Intel 965GM chipset. Older versions
of Xubuntu had no problem handling the external display correctly, but
after updating to Intrepid, X always starts using the resolution of the
internal display (1024x768), even if the laptop lid is closed.

Thanks to the workaround proposed above, I'm at least able to switch to
the correct resolution after login:

xrandr --output VGA --mode 1680x1050

Bug this bug is still very annoying, an it's a real killer for innocent
people updating their Ubuntu that aren't experienced enough to find this
bug report and apply the workaround.

Please raise the importance of this bug to "critial". It's a real
showstopper for laptops using a 965GM chipset!

-- 
[INTREPID] 965GM gives a wrong screen resolution on laptop used with an 
external display
https://bugs.launchpad.net/bugs/272669
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 717919] Re: ACPI + kworker high interrupts.

2012-02-08 Thread Christian Siefkes
I sometimes have the same problem with my Thinkpad X61s, running Ubuntu
Natty (2.6.38-13-generic #54-Ubuntu SMP i386 GNU/Linux). I finally found
out that the problem occurs if two conditions are met:

1. There is no LAN connection (no LAN cable is plugged in or the
LAN/router has no working Internet connection).

2. The laptop runs on mains power, not just on battery.

If both conditions are met at startup, the kworkers run amok, taking all
CPU power they can get. Since I discovered these conditions, I was able
to avoid the problem by starting the laptop from battery power when I
have no LAN. I can plug in the power cable later without problems, but
it must not be plugged in at startup or the kworkers will go crazy.

When they did, I once run "sudo perf record -ag sleep 10" and "sudo perf
report", which essentially showed the following::

53.80%  kworker/0:4  [kernel.kallsyms]  [k] delay_tsc
|
— delay_tsc
__const_udelay
e1000_check_phy_82574
__e1000e_read_phy_reg_igp
e1000e_write_phy_reg_m88
e1000e_phy_has_link_generic
e1000_configure_k1_ich8lan
e1000e_has_link
e1000e_up
process_one_work
worker_thread
kthread
kernel_thread_helper

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/717919

Title:
  ACPI + kworker high interrupts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717919/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 537396] Re: events/0 spikes CPU every 3 seconds since upgrade to 2.6.31-20

2010-08-25 Thread Christian Siefkes
Since today I'm affected too. I use Xubuntu Lucid/32-bit on a Lenovo
X61s. "ifconfig eth0 down" fixed the problem for the time being; I
didn't yet try the "remove battery" trick.

Re comment #32: I don't have Windows on my computer, that's not the
issue.

I don't understand why the bug has been marked invalid.

-- 
events/0 spikes CPU every 3 seconds since upgrade to 2.6.31-20
https://bugs.launchpad.net/bugs/537396
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs