Re: Bizarre oops after suspend to RAM (was: Re: [ACPI] Resume from Suspend to RAM)

[Pavel Machek]

Hi!

> > > I've no idea how to debug a reboot, but if the system hangs it's possible to 
> > > add "lcall $0xffff,$0" early in the wakeup assembler code. If the system 
> > > reboots immediatly then, the kernels wakeup code was reached and the kernel 
> > > hangs later during resume.
> > 
> > Ok, I've just tried that. The system still just freezes.
> 
> Whoops. May have been a bit too hasty there. I'm not sure why that
> doesn't reset it, but we've now got the following (really rather odd)
> serial output. Does anyone have any idea what might be triggering this?
> Shell builtins work fine, but anything else seems to explode very
> messily. Memory corruption of some description?
> 
> ^MRestarting tasks... done
> ^Mroot@(none):/# ^M
> root@(none):/# ls -la ^M
> Unable to handle kernel NULL pointer dereference at virtual address
> > > 00000024

NULL pointer dereference in filp_open; whats that strange about it?
Use printks to debug this one, nothing mysterious.
								Pavel

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/