On 2013/03/05 14:13, Andriy Gapon wrote: > on 03/03/2013 20:26 kron said the following: >> #5 0xffffffff806abc53 in calltrap () at exception.S:228 >> #6 0xffffffff802bc850 in AcpiOsAcquireObject (Cache=0xfffffe00093a14a0) >> at /usr/src/sys/contrib/dev/acpica/utilities/utcache.c:310 >> #7 0xffffffff802bf481 in AcpiUtCreateInternalObjectDbg ( >> ModuleName=0xffffffff8071c1a6 "dsutils", LineNumber=703, >> ComponentId=64,. >> Type=1) at /usr/src/sys/contrib/dev/acpica/utilities/utobject.c:437 > > Did this panic happen even with hw.acpi.osname="Linux" or did you revert that > to > reproduce the panic?
Yes, it was with hw.acpi.osname="Linux". It seems to be useless so I've just removed it. > > In either case, could you please try the following patch (it is against recent > stable/9) ? > http://people.freebsd.org/~avg/OsdSynch-9.diff Applied. BTW, the crashes use to be signalized beforehand - there can be more than 1 hour between the first kernel error messages ("ACPI Error: No object attached") and a crash. Is there anything useful I can milk from the soon-to-be-dead system if I get a chance? BR Oli _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to "[email protected]"
