From: Adrian Bunk <bunk@stusta.de>
To: "Ismail Dönmez" <ismail@pardus.org.tr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Ooops with suspend to RAM
Date: Wed, 14 Mar 2007 12:50:47 +0100 [thread overview]
Message-ID: <20070314115047.GC18731@stusta.de> (raw)
In-Reply-To: <200703140642.28390.ismail@pardus.org.tr>
On Wed, Mar 14, 2007 at 06:42:28AM +0200, Ismail Dönmez wrote:
> Hi all,
>
> With latest GIT tree I am getting the following oops when I try to suspend to
> RAM:
>...
Is this an old problem, or what was the last kernel that worked for you?
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-03-14 11:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 4:42 Ooops with suspend to RAM Ismail Dönmez
2007-03-14 11:14 ` oops in __nodemgr_remove_host_dev (was Re: Ooops with suspend to RAM) Stefan Richter
2007-03-14 11:45 ` oops in __nodemgr_remove_host_dev Stefan Richter
2007-03-14 16:58 ` oops in __nodemgr_remove_host_dev (was Re: Ooops with suspend to RAM) Ismail Dönmez
2007-03-14 18:25 ` Stefan Richter
2007-03-14 22:51 ` Ismail Dönmez
2007-03-15 0:08 ` Stefan Richter
2007-03-15 0:14 ` Stefan Richter
2007-03-15 0:45 ` Ismail Dönmez
2007-03-15 0:49 ` Ismail Dönmez
2007-03-16 19:46 ` Stefan Richter
2007-03-20 21:43 ` [PATCH 2.6.21-rc4] ieee1394: fix oops on "modprobe -r ohci1394" after network class_device conversion Stefan Richter
2007-03-20 22:26 ` Ismail Dönmez
2007-03-21 18:11 ` Stefan Richter
2007-03-20 23:34 ` Greg KH
2007-03-21 0:16 ` Stefan Richter
2007-05-13 11:43 ` Stefan Richter
2007-05-20 20:21 ` Stefan Richter
2007-03-14 11:50 ` Adrian Bunk [this message]
2007-03-14 16:59 ` Ooops with suspend to RAM Ismail Dönmez
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=20070314115047.GC18731@stusta.de \
--to=bunk@stusta.de \
--cc=ismail@pardus.org.tr \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.