Unable to handle null pointer dereference (acpi_ps_has_completed_scope)

And here's the attachment.

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information.

Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available here: <http://wiki.ubuntu.com/DebuggingKernelProblems> Thanks!

Here's the additional info.

# uname -a
Linux bakbeest 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux

lspci -vvnn is attached.

Oh, and the relevant dmesg info should be contained in the syslog excerpt. I have nothing else from that crash anymore, I'm sorry. :-(

Thanks for the info. FYI, only the first crash is relevant most times, since the second is usually caused by the first one.

Seems to be a genuine bug. Please try to reproduce against latest kernel (2.6.20-8).

OK, I'll make a proper backup and then start using suspend again. I'll get back to you once I'm sure that it either works or doesn't work. :-)

I've started using suspend again, this time using 2.6.20-9-generic. I haven't seen *this* bug again in the last 20 suspends. However, of these 20 suspends, I had at least five resume failures, and in some of these, the logs were lost. (Notably, I had a crash five minutes *after* resume, and the last message in the logs was... log rotation. :-) ) I'm dropping the suspend again, it's simply not reliable enough for me at the moment. You can close this particular bug as far as I'm concerned.

Thanks. Marking rejected for now.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.