From: Nigel Cunningham <ncunningham@clear.net.nz>
To: alexander.riesen@synopsys.COM
Cc: Milton Miller <miltonm@bga.com>,
Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>,
Zwane Mwaikambo <zwane@linuxpower.ca>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
mikpe@csd.uu.se
Subject: Re: 2.5.69+bk: oops in apmd after waking up from suspend mode
Date: Wed, 21 May 2003 08:10:00 +1200 [thread overview]
Message-ID: <1053461400.2055.7.camel@laptop-linux> (raw)
In-Reply-To: <20030520171759.GR32559@Synopsys.COM>
This isn't the first time crashes have been seen suspending when hardly
any memory has been used. With the 2.4 swsusp project, we've seen
crashes appear when trying to suspend with init=/bin/bash that don't
appear when more memory has been used. Perhaps there's a common issue
here.
Regards,
Nigel
On Wed, 2003-05-21 at 05:17, Alex Riesen wrote:
> It is harder to trigger, but possible.
> I booted with init=/bin/bash. Than I started this
> find / -type f -fprint /dev/stderr -print | xargs cat > /dev/null
> and began going in suspend mode and back.
>
> At some point it broke with oops above.
>
> -alex
--
Nigel Cunningham
495 St Georges Road South, Hastings 4201, New Zealand
Be diligent to present yourself approved to God as a workman who does
not need to be ashamed, handling accurately the word of truth.
-- 2 Timothy 2:14, NASB.
next prev parent reply other threads:[~2003-05-20 20:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 12:16 2.5.69+bk: oops in apmd after waking up from suspend mode mikpe
2003-05-19 12:31 ` Alex Riesen
2003-05-19 14:41 ` Alex Riesen
2003-05-19 15:13 ` Alex Riesen
2003-05-20 10:39 ` Carl-Daniel Hailfinger
2003-05-20 10:48 ` Alex Riesen
2003-05-20 16:34 ` Milton Miller
2003-05-20 17:00 ` Alex Riesen
2003-05-20 17:17 ` Alex Riesen
2003-05-20 20:10 ` Nigel Cunningham [this message]
2003-05-20 22:01 ` Zwane Mwaikambo
2003-05-19 21:57 ` Zwane Mwaikambo
-- strict thread matches above, loose matches on Subject: below --
2003-05-14 9:48 Alex Riesen
2003-05-14 13:04 ` mikpe
2003-05-14 13:46 ` Alex Riesen
2003-05-14 14:03 ` mikpe
2003-05-14 14:11 ` Alex Riesen
2003-05-14 14:37 ` mikpe
2003-05-14 14:45 ` Alex Riesen
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=1053461400.2055.7.camel@laptop-linux \
--to=ncunningham@clear.net.nz \
--cc=alexander.riesen@synopsys.COM \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--cc=miltonm@bga.com \
--cc=zwane@linuxpower.ca \
/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