From: Leonid Kalmankin <lvk@mashcenter.ru>
To: linux-kernel@vger.kernel.org
Subject: segfault and multiple traps on x86_64
Date: Tue, 14 Sep 2004 01:31:17 +0400 [thread overview]
Message-ID: <20040914013117.3bda812d.lvk@mashcenter.ru> (raw)
Greetings!
In dmesg I see stuff like:
rpmbuild[3842] trap int3 rip:402d9e rsp:7fbfffb540 error:0
rpmbuild[3842] trap int3 rip:4026d1 rsp:7fbfffb538 error:0
sh[3843] trap int3 rip:415f39 rsp:7fbffff8c8 error:0
sh[3843]: segfault at 0000000000000000 rip 0000000000000000 rsp 0000007fbffff8b8 error 14
rpmbuild[3842] trap int3 rip:402dea rsp:7fbfffb540 error:0
rpmbuild[3842] trap int3 rip:4025d1 rsp:7fbfffb538 error:0
rpmbuild[3842] trap int3 rip:402ced rsp:7fbfffb540 error:0
rpmbuild[3842] trap int3 rip:4027c1 rsp:7fbffff688 error:0
segfault is scarry.
Are these traps harmless or do they mean some serious software/hardware problem?
The system is:
Fedora Core 2 x86_64, last updates, vanilla 2.6.8.1, dual AMD Opteron, 4G RAM
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 5
model name : AMD Opteron(tm) Processor 246
stepping : 10
cpu MHz : 1992.318
cache size : 1024 KB
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow
bogomips : 3915.77
TLB size : 1088 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp
[skipping 2nd processor info]
SY,
LVK
next reply other threads:[~2004-09-13 21:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 21:31 Leonid Kalmankin [this message]
2004-09-14 7:43 ` Alexander Nyberg
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=20040914013117.3bda812d.lvk@mashcenter.ru \
--to=lvk@mashcenter.ru \
--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®