Messages in this thread | | | Date | Mon, 6 Jun 2005 15:54:29 +0100 | From | Matthew Garrett <> | Subject | Re: Bizarre oops after suspend to RAM (was: Re: [ACPI] Resume from Suspend to RAM) |
| |
On Mon, Jun 06, 2005 at 04:45:01PM +0200, Pavel Machek wrote:
> NULL pointer dereference in filp_open; whats that strange about it? > Use printks to debug this one, nothing mysterious.
I can't see any way that a null pointer could get to filp_open without something already being very wrong - the kernel worked fine before suspend. Unfortunately, that's the one occasion that we've got the machine (an HP nc4000) to resume. Since then, it simply freezes before hitting "Back to C" despite having had no kernel or configuration changes. The behaviour is very non-deterministic, which makes me wonder about something in the suspend or resume process damaging state.
-- Matthew Garrett | mjg59@srcf.ucam.org - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |