https://bugzilla.novell.com/show_bug.cgi?id=350017
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=350017#c20
--- Comment #20 from Thomas Renninger
It will be more appropriate to fix this bug by BIOS update. Yes, but I think, and that is the reason why I am still searching, that this bug exposed an ugly invalid (pointer) node bug.
For debugging on another machine, I changed: Name (_PSL, Package (0x01) { \_PR.C000 \_PR.C001 }) to e.g.: Name (_PSL, Package (0x01) { \_PR.K000 \_PR.K001 }) The first reference node was again an invalid pointer, the second was NULL (as it should be I expect) and "Invalid passive trip point" was shown -> No kernel oops, etc.. Using only invalid reference only the invalid pointer/node is there and the code runs into the oops. This if/else path came in with the above stated patch (if code runs through here it also shows the "Ignoring unresolved reference in package", maybe this is the right place to fix this?): * We didn't find the target and we are populating elements * of a package - ignore if slack enabled. Some ASL code * contains dangling invalid references in packages and * expects that no exception will be issued. Leave the * element as a null element. It cannot be used, but it * can be overwritten by subsequent ASL code - this is * typically the case. But instead of leaving the element to be NULL as stated, it seems it is an invalid (uninitialized?) pointer. But I had some problems with this internal to external conversions and couldn't find the right object to clear with NULL and I had to reboot for each test... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.