What version of virtualbox are you using? I'm curious now, I have version 3.1.0 for reference. Also, what do you mean by stuttering/pausing? Is there a reference for these kernel bugs?
Just curious...want to know what to expect if this starts happening / how to tell. Thanks. On Wed, Dec 9, 2009 at 1:54 AM, Zatara214 <[email protected]> wrote: > I'm fairly certain that the vbox issues I'm having are also an effect of > the new kernel. Never had these issues with 2.6.28. I'll probably > switch back if the generic kernel doesn't turn out to be anything good. > Apparently there was a new bug introduced in 2.6.31 that required the > real-time kernel to be installed or vbox wouldn't work as it should > (which I experienced before, but I was hoping it was fixed). I'm > surprised you haven't had this issue, as well. Guest pausing/stuttering > every 15 or so seconds. > > -- > ac adapter is not detected > https://bugs.launchpad.net/bugs/412499 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “linux” package in Ubuntu: Triaged > > Bug description: > The latest version of jaunty generates errors when trying to load the acpi > ac adapter state on boot. The resultant behavior is that the system is > unaware of the ac adapter state (nothing gets populated in > /proc/acpi/ac_adapter or its equivalent sys directory). The error can be > seen via 'dmesg | grep ACPI' after booting: > > [ 1.679140] ACPI Error (psargs-0358): [\_PR_.CPU0._PSS] Namespace lookup > fail > ure, AE_NOT_FOUND > [ 1.679167] ACPI Error (psparse-0524): Method parse/execution failed > [\_SB_.A > C__.ADJP] (Node ffff88013f81a660), AE_NOT_FOUND > [ 1.679215] ACPI Error (psparse-0524): Method parse/execution failed > [\_SB_.A > C__._PSR] (Node ffff88013f81a620), AE_NOT_FOUND > [ 1.679264] ACPI Exception (ac-0135): AE_NOT_FOUND, Error reading AC > Adapter state [20080926] > [ 1.769339] ACPI: Battery Slot [BAT0] (battery present) > > This is most problematic on the kubuntu distribution, as it relies on this > information to determine the ac adapter state for powerdevil. On gnome there > is some sort of fall back and the correct state is determined (possibly by > interpreting /proc/acpi/battery/*)? After investigating this further, I > recompiled the stock ubuntu kernel from source with acpi_ac as a module > instead of into the kernel and the ac adapter state is detected correctly. > ACPI no longer generates errors and outputs the following: > > [ 1.824127] ACPI: CPU1 (power states: C1[C1] C2[C2] C3[C3]) > [ 1.824141] processor ACPI_CPU:01: registered as cooling_device1 > [ 1.824143] ACPI: Processor [CPU1] (supports 8 throttling states) > [ 1.858123] ACPI: Thermal Zone [TZ0] (57 C) > [ 12.273114] ACPI: Video Device [PEGP] (multi-head: yes rom: no post: > no) > [ 12.302021] ACPI: AC Adapter [AC] (on-line) > > Is this the correct method to solve this problem? I've checked this > solution against several other distributions that report the ac adapter > state correctly (namely ArchLinux and openSUSE) and from what I can tell > this is the solution that is used in each case. > > lsb_release -rd > -- > Description: Ubuntu 9.04 > Release: 9.04 > > uname -a > -- > Linux kronos 2.6.28-14-generic #47 SMP Wed Aug 12 07:37:17 EDT 2009 x86_64 > GNU/Linux > > apt-cache policy linux-image-2.6.28-14-generic > -- > linux-image-2.6.28-14-generic: > Installed: 2.6.28-14.47 > Candidate: 2.6.28-14.47 > Version table: > 2.6.28-14.47 0 > 500 http://us.archive.ubuntu.com jaunty-updates/main Packages > 500 http://security.ubuntu.com jaunty-security/main Packages > *** 2.6.28-14.47 0 > 100 /var/lib/dpkg/status > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/412499/+subscribe > -- ac adapter is not detected https://bugs.launchpad.net/bugs/412499 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
