From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: acpi-devel@lists.sourceforge.net, 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:54:29 +0100 [thread overview]
Message-ID: <20050606145429.GA18396@srcf.ucam.org> (raw)
In-Reply-To: <20050606144501.GB2243@elf.ucw.cz>
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
next prev parent reply other threads:[~2005-06-06 14:54 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 ` Bizarre oops after suspend to RAM (was: Re: [ACPI] Resume from Suspend to RAM) Matthew Garrett
2005-06-06 14:45 ` Pavel Machek
2005-06-06 14:54 ` Matthew Garrett [this message]
2005-06-06 15:09 ` Pavel Machek
2005-06-07 14:14 ` Martin Michlmayr
2005-06-06 15:31 ` Stefan Dösinger
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=20050606145429.GA18396@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=acpi-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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