https://bugzilla.novell.com/show_bug.cgi?id=623393 https://bugzilla.novell.com/show_bug.cgi?id=623393#c29 --- Comment #29 from Thomas Renninger <trenn@novell.com> 2011-01-21 13:05:38 UTC --- Function acpi_init_one_device does not exist, there only is acpi_ns_init_one_device in drivers/acpi/acpica/nsinit.c If you would have attached a real diff, I could have find out where you placed the code from comment #28... Anyway, if it's really this, something might go wrong when the _STA or _INI function of the affected device is called... If it's really this function you could also place a debug print at the beginning like at the end: ACPI_EXCEPTION((AE_INFO, status, "during %s._INI" "execution",scope_name)); then we would know which device exactly is no. 35. This should be enough already. If not, you can also run with: acpi.debug_layer=0xFFFFFFFF acpi.debug_level=0x20F log_bug_len=16M boot parameters and should get quite some additional output. But as said, knowing about the device might be enough. You can then try to do: acpidump >acpidump acpixtract acpidump acpiexec DSDT.dat in acpiexec shell, find the _STA and _INI method path of the bad device via: methods and then execute them: execute ..._INI execute ..._STA I expect this will work, it's more likely that a HW access inside of these cause the hang and acpiexec in userspace cannot access HW. But possibly you already get a warning/error. -- 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.