From: "Stefan Dösinger" <stefandoesinger@gmx.at>
To: acpi-devel@lists.sourceforge.net
Cc: Matthew Garrett <mjg59@srcf.ucam.org>, linux-kernel@vger.kernel.org
Subject: Re: Bizarre oops after suspend to RAM (was: Re: [ACPI] Resume from Suspend to RAM)
Date: Mon, 6 Jun 2005 15:31:40 +0000 [thread overview]
Message-ID: <200506061531.41132.stefandoesinger@gmx.at> (raw)
In-Reply-To: <1118056003.6648.148.camel@tyrosine>
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
next prev parent reply other threads:[~2005-06-06 13:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200506051456.44810.hugelmopf@web.de>
[not found] ` <1117978635.6648.136.camel@tyrosine>
[not found] ` <200506051732.08854.stefandoesinger@gmx.at>
[not found] ` <1118053578.6648.142.camel@tyrosine>
2005-06-06 11:06 ` Matthew Garrett
2005-06-06 14:45 ` Pavel Machek
2005-06-06 14:54 ` Matthew Garrett
2005-06-06 15:09 ` Pavel Machek
2005-06-07 14:14 ` Martin Michlmayr
2005-06-06 15:31 ` Stefan Dösinger [this message]
2005-06-07 6:23 ` S3 test tool (was : Re: Bizarre oops after suspend to RAM (was: Re: [ACPI] Resume from Suspend to RAM)) Shaohua Li
2005-06-07 12:07 ` Martin Michlmayr
2005-06-14 7:25 ` dagit
2005-06-14 8:47 ` Matthew Garrett
2005-06-14 16:24 ` dagit
2005-06-17 13:16 ` Matthew Garrett
2005-06-14 9:06 ` Pavel Machek
2005-06-14 15:51 ` dagit
2005-06-14 21:37 ` Pavel Machek
2005-06-14 22:01 ` dagit
2005-06-14 22:09 ` Pavel Machek
2005-06-14 22:18 ` dagit
2005-06-14 23:11 ` Pavel Machek
2005-06-15 0:41 ` dagit
2005-06-15 0:50 ` dagit
2005-06-15 18:41 ` Pavel Machek
[not found] <4cnEB-7Y5-13@gated-at.bofh.it>
[not found] ` <4cnEB-7Y5-19@gated-at.bofh.it>
[not found] ` <4cnEB-7Y5-11@gated-at.bofh.it>
[not found] ` <4cpZW-1yL-13@gated-at.bofh.it>
2005-06-07 1:06 ` Bizarre oops after suspend to RAM (was: Re: [ACPI] Resume from Suspend to RAM) Bodo Eggert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200506061531.41132.stefandoesinger@gmx.at \
--to=stefandoesinger@gmx.at \
--cc=acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®