From: hugang@soulinfo.com
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@zip.com.au>
Subject: Re: Applications segfault on evo n620c with 2.6.10
Date: Fri, 28 Jan 2005 10:36:37 +0800 [thread overview]
Message-ID: <20050128023636.GA3919@hugang.soulinfo.com> (raw)
In-Reply-To: <20050127184334.GA1368@elf.ucw.cz>
On Thu, Jan 27, 2005 at 07:43:34PM +0100, Pavel Machek wrote:
> Hi!
>
> It happened for 3rd in a week now...
>
> When problem happens, processes start to segfault, usually right
> during startup. Programs that were loaded prior to problem usualy
> works, and can be restarted. I also seen sendmail exec failing with
> "no such file or directory" when it clearly was there. Reboot corrects
> things, and filesystem (ext3) is not damaged.
>
> Unfortunately I do not know how to reproduce it. I tried
> parallel-building kernels for few hours and that worked okay. Swsusp
> is not involved (but usb, bluetooth, acpi and sound may be).
>
> Does anyone else see something similar?
I got the same thing in my computer.
Maybe this can reproduce it.
1: add this in boot loader
"init=/bin/sh"
2: after system boot, then active swap space, then do suspend.
3: after system resume, the sh will crash like.
that can 100% reproduce it my in X86, X86_64, PPC32.
The Software suspend2 has not that problem.
--
Hu Gang .-.
/v\
// \\
Linux User /( )\ [204016]
GPG Key ID ^^-^^ http://soulinfo.com/~hugang/hugang.asc
next prev parent reply other threads:[~2005-01-28 2:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 18:43 Applications segfault on evo n620c with 2.6.10 Pavel Machek
2005-01-27 22:57 ` Nigel Cunningham
2005-01-27 23:01 ` Pavel Machek
2005-01-27 23:09 ` Nigel Cunningham
2005-01-28 2:36 ` hugang [this message]
2005-01-28 10:11 ` Pierre Chifflier
2005-01-28 13:04 ` Pavel Machek
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=20050128023636.GA3919@hugang.soulinfo.com \
--to=hugang@soulinfo.com \
--cc=akpm@zip.com.au \
--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 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.