lkml.org 
[lkml]   [2005]   [Jun]   [6]   [last100]   RSS Feed
Views: [more markup]  [less markup]  [headers]  [forward] 
 
Messages in this thread
/
FromStefan Dösinger <>
SubjectRe: Bizarre oops after suspend to RAM (was: Re: [ACPI] Resume from Suspend to RAM)
DateMon, 6 Jun 2005 15:31:40 +0000
Am Montag, 6. Juni 2005 11:06 schrieb Matthew Garrett:
> 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?

<snip>
So it does reach the kernel, right? I don't know if I remembered that call 
correctly, but "lcall $0xffff,$0" should call the real mode BIOS reset 
code...
Anyone else who can correct me here?
Perhaps the disk driver is going mad? Has anyone tried to boot a kernel 
without any disk drivers with a minimal root system on an initrd?

Cheers,
Stefan
-
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/

\
 
 \ /
  Last update: 2005-06-06 13:37    [from the cache]
©2003-2008