From: insecure <insecure@mail.od.ua>
To: Andi Kleen <ak@suse.de>, <bvds@bvds.geneva.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: segfault error on x86_64
Date: Sat, 4 Oct 2003 17:13:55 +0300 [thread overview]
Message-ID: <200310041713.55050.insecure@mail.od.ua> (raw)
In-Reply-To: <p73y8w2yboa.fsf@oldwotan.suse.de>
On Friday 03 October 2003 11:20, Andi Kleen wrote:
> <bvds@bvds.geneva.edu> writes:
> > I have kernel 2.4.22 compiled with gcc 3.3 running on a
> > dual AMD Opteron (in 64 bit mode).
> > There is an error message that occurs about twice a day at random times:
> >
> > Sep 30 23:45:00 gideon kernel: bumps[12960]: segfault at 0000002a95611000
> > rip 0000000000402150 rsp 0000007fbffff1a8 error 6 Oct 1 10:26:57 gideon
> > kernel: bumps[13510]: segfault at 0000002a95611000 rip 0000000000402150
> > rsp 0000007fbffff1a8 error 6
> >
> > As far as I can tell, there is no other effect than this message.
> > (the system keeps running OK).
> >
> > What is "bumps" ?
>
> Some random program on your system. The x86-64 kernel logs all unhandled
> segfaults by default. It is unlikely to be a kernel problem.
Whoa. Do you mean it can be told to not do this?
This is very good, because it can now be generalized to all arches
without people objecting 'its legitimate to use unhandled SEGVs,
I do not want this logged' - they can turn it off in /proc.
Of course some folks will object anyway ;););)
--
vda
next prev parent reply other threads:[~2003-10-04 14:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031002215345.A1D33E24D6@bvds.geneva.edu.suse.lists.linux.kernel>
2003-10-03 8:20 ` segfault error on x86_64 Andi Kleen
2003-10-03 8:44 ` Mitchell Blank Jr
2003-10-03 10:04 ` bvds
2003-10-04 14:13 ` insecure [this message]
2003-10-02 21:53 bvds
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=200310041713.55050.insecure@mail.od.ua \
--to=insecure@mail.od.ua \
--cc=ak@suse.de \
--cc=bvds@bvds.geneva.edu \
--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