From: Maurice Volaski <mvolaski@aecom.yu.edu>
To: linux-kernel@vger.kernel.org
Cc: colding@omesc.com, bert.hubert@netherlabs.nl
Subject: Re: Segfaults in mkdir under high load. Software or hardware?
Date: Sat, 17 Sep 2005 20:20:40 -0400 [thread overview]
Message-ID: <a0623096fbf5261b770eb@[129.98.90.227]> (raw)
In-Reply-To: <mailman.3.1123153201.10574.linux-kernel-daily-digest@lists.us.dell.com>
> > I am experiencing segfaults in mkdir, and mkdir alone, under high load.
>
>I've seen errors like these happen, and they were kernel bugs.
>
>> [ 0.000000] Bootdata ok (command line is root=/dev/sda4
>>vga=0x31B video=vesafb:mtrr,ywrap)
> > [ 0.000000] Linux version 2.6.12-gentoo-r6 (root@omc-2) (gcc
>version 3.4.3 20041125 (Gentoo 3.4.3-r1, ssp-3.4.3-0, pie-8.7.7)) #6
>SMP Mon Jul 25 13:50:58 CEST 2005
>
>If you reproduce with an unpatched kernel and an unpatched compiler, you are
>much more likely to get attention. Your problem might also just go away.
I have been seeing a similar thing:
./current:Sep 17 18:00:01 [kernel] mkdir[7696]: segfault at
0000000000000000 rip 000000000040184d rsp 00007fffff826350 error 4
I'm using the plain 2.6.13 (from gentoo vanilla sources), though it
was compiled with
gcc version 3.4.4 (Gentoo 3.4.4-r1, ssp-3.4.4-1.0, pie-8.7.8)
--
Maurice Volaski, mvolaski@aecom.yu.edu
Computing Support, Rose F. Kennedy Center
Albert Einstein College of Medicine of Yeshiva University
next parent reply other threads:[~2005-09-18 0:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3.1123153201.10574.linux-kernel-daily-digest@lists.us.dell.com>
2005-09-18 0:20 ` Maurice Volaski [this message]
2005-09-18 7:34 ` Andrew Walrond
2005-09-18 8:49 ` bert hubert
[not found] <mailman.3.1127041200.14075.linux-kernel-daily-digest@lists.us.dell.com>
2005-09-19 1:03 ` Maurice Volaski
2005-09-19 19:27 ` Bongani Hlope
2005-08-03 12:14 Jules Colding
2005-08-03 12:57 ` bert hubert
2005-08-03 13:12 ` Steven Rostedt
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='a0623096fbf5261b770eb@[129.98.90.227]' \
--to=mvolaski@aecom.yu.edu \
--cc=bert.hubert@netherlabs.nl \
--cc=colding@omesc.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
all inboxes | Powered by JetHome®