From: "Ioan Ionita" <opslynx@gmail.com>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>, ak@suse.de
Subject: x86-64 2.6.22-rc2 random segfaults
Date: Thu, 24 May 2007 14:42:07 -0400 [thread overview]
Message-ID: <df47b87a0705241142gce9bdbbkaa3b25be21ba04c0@mail.gmail.com> (raw)
Hello,
Since upgrading from 2.6.21 to 2.6.22-rc2, I started seeing some
segfaults in dmesg.
2.6.22-rc1-git2 even locked up on me at one point.
I'm using SLUB. I haven't yet found a way to easily reproduce the
problem.. Once I do, I'll try a git bisect
gam_server[4269]: segfault at 0000000000000018 rip 00002b46a9f88ab7
rsp 00007fff00d80020 error 4
gam_server[6003]: segfault at 0000000000000017 rip 00002accf4c50ab7
rsp 00007fffb60b74b0 error 4
gam_server[6395]: segfault at 0000000000000000 rip 00002b9f55885239
rsp 00007fff55754f30 error 4
gam_server[9414]: segfault at 000000000000001b rip 00002ab4a51b0ab7
rsp 00007fff05b59f60 error 4
gam_server[10412]: segfault at 000000000000001c rip 00002b7d42556ab7
rsp 00007fff687b14e0 error 4
gam_server[10427]: segfault at 0000000000000017 rip 00002ac59efe6ab7
rsp 00007fff0bd24130 error 4
gam_server[10433]: segfault at 0000000000000017 rip 00002b66058e9ab7
rsp 00007fffa5420710 error 4
gam_server[10451]: segfault at 0000000000000017 rip 00002b4220764ab7
rsp 00007fff8a5a3890 error 4
gam_server[10461]: segfault at 000000000000001d rip 00002ae292751ab7
rsp 00007fff185b69b0 error 4
gam_server[10485]: segfault at 000000000000001b rip 00002b525be5dab7
rsp 00007fff4eeab150 error 4
gam_server[10491]: segfault at 000000000000001a rip 00002aff730c7ab7
rsp 00007fff37c42eb0 error 4
root@ops-desktop:~# uname -a
Linux ops-desktop 2.6.22-rc2-git4 #1 SMP PREEMPT Wed May 23 22:35:02
EDT 2007 x86_64 GNU/Linux
next reply other threads:[~2007-05-24 18:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 18:42 Ioan Ionita [this message]
2007-05-24 21:15 ` Andi Kleen
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=df47b87a0705241142gce9bdbbkaa3b25be21ba04c0@mail.gmail.com \
--to=opslynx@gmail.com \
--cc=ak@suse.de \
--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
all inboxes | Powered by JetHome®