From: davidsen@tmr.com (Bill Davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: Random SIGSEGVs and 2.6.0-test10
Date: 2 Dec 2003 03:10:42 GMT [thread overview]
Message-ID: <bqgvri$8mh$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 3FC559AB.7000806@sh0n.net
In article <3FC559AB.7000806@sh0n.net>, Shawn Starr <spstarr@sh0n.net> wrote:
>It's funny you mention random userland SIGSEGV's.
>
>I don't know if this some of the fallout wrt CONFIG_PREEMPT being
>enabled or not but using vmware and running my ncurses mp3 player seems
>to trigger an oddity:
>
>Apon using vmware, it may sometimes crap out with a internal bug # and
>in doing so, sometimes my mp3 player will segfault for no reason. This
>randomly happens. I do have preempt enabled. Even more odd is the fact
>that even if I have only say 4500K left out of 576MB, there is 0 swap
>usage. The kernel malloc fails if there is no physical memory? If I have
>a huge swap file/disk wouldn't it malloc some of that virtual memory?
>There is no OOM kill either happening since there's no log of that from
>the kernel saying it did an OOM kill.
>
>I would certainly like to debug any weird oddities. My systems seem to
>be good test grounds for such things :-)
1 - You can play with swappiness which should get swap used
2 - I doubt that's the problem
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
prev parent reply other threads:[~2003-12-02 3:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 1:55 Random SIGSEGVs and 2.6.0-test10 Shawn Starr
2003-12-02 3:10 ` Bill Davidsen [this message]
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='bqgvri$8mh$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox