On Wed, May 26, 2010 at 1:45 AM, Beat Gaetzi <[email protected]> wrote: > On 05/26/10 08:27, Brandon Gooch wrote: >> On Fri, Apr 30, 2010 at 1:05 PM, Jung-uk Kim <[email protected]> wrote: >>> On Thursday 29 April 2010 09:02 pm, Michael Butler wrote: >>>> On 04/29/10 19:23, Jung-uk Kim wrote: >>>>> I read the source again and I found it is not "patched" by the >>>>> emulator itself. It's done from usual _CRS method. Please try >>>>> the attached patch instead. >>>> >>>> Now I get .. >>>> >>>> kBuild: iasl DevicesR3 - >>>> /usr/home/imb/svn/virtualbox-ose/work/VirtualBox-3.2.0_OSE/src/VBox >>>> /Devices/PC/vbox-cpuhotplug.dsl >>>> /usr/home/imb/svn/virtualbox-ose/work/VirtualBox-3.2.0_OSE/out/free >>>> bsd.x86/release/obj/DevicesR3/vboxssdt-cpuhotplug.hex.pre 14: >>>> Device (SCK0) { Name (_HID, "ACPI0004") Name (_UID, "SCKCPU0") >>>> Processor (CPU0, 0x00, 0x0, 0x0 ) { Name (_HID, "ACPI0007") Name >>>> (_UID, "SCK0-CPU0") Name (_PXM, 0x00) Method(_MAT, 0) { IF >>>> (CPCK(0x00)) { Name (APIC, Buffer (8) {0x00, 0x08, 0x00, 0x00, >>>> 0x01}) Return(APIC) } Else { Return (0x00) } } Method(_STA) { IF >>>> (CPCK(0x00)) { Return (0xF) } Else { Return (0x0) } } Method(_EJ0, >>>> 1) { Store(0x00, \_SB.CPUL) Return } } } >>>> >>>> Error 4080 - >>>> >>>> >>>> >>>> >>>> Invalid object type for reserved >>>> name ^ (found INTEGER, requires Buffer) >>>> >>>> .. where the "Return(0x00)" as the alternate result to >>>> "Result(APIC)" is causing an issue, >>> >>> Sigh... A new file, a new bug. :-( >>> >>> Try the attached patch. >> >> It seems this patch has been committed to the 'virtualbox-ose-devel' >> port, but your previous patch (attached to an earlier message in this >> thread) did not. Will you submit the original patch to the >> freebsd-vbox crew as well? > > I forgot to commit this patch to the virtualbox-ose-devel port as our > main focus is on the 3.2.0 port at the moment with already includes this > patch. I will commit the patch in a few minutes to the -devel port. > I see... Well, as it stands, both of my laptops, one running CURRENT, the other running 8.1-PRERELEASE, panic when loading the vboxdrv module right now (on 3.2.1 at least), so I'm looking to rollback to 3.1.8 -- or test 3.2.0 :)
Will you announce to the list when we VirtualBox users should begin testing 3.2.0? Or did I already miss that? > > Thanks for the reminder! > Beat > Thank you! -Brandon _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "[email protected]"
