public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rafal Skoczylas <nils@secprog.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.test11 bug
Date: Mon, 8 Dec 2003 23:28:42 +0100	[thread overview]
Message-ID: <20031208222842.GA27131@secprog.org> (raw)
In-Reply-To: <10xdJ-28r-21@gated-at.bofh.it>

On 2003-12-08 17:20 Linus Torvalds wrote:
> On Mon, 8 Dec 2003, Linus Torvalds wrote:
>> They all look to be (except for the odd last "bad page state" one, which
>> is likely just a result of some _other_ earlier corruption) due to the
>> high bit being cleared. And it's consistent across reboots too, so it's
>> not just some corruption that stayed around in memory.

I have already stuffed kernel source with debugging printk's, etc.,
so hopefully we could more precisely say where the problem is. Anyway
it will probably take quite a long to determine because (as I previously
said in our "private" e-mail exchange) it takes long hours to crash.
(eg. today mlnetd was killed twice but no system crash yet)
Now, I am starting mlnet in a 'while [ 1 ]; do mlnet; done;' loop just
in case it gets killed and let's see what will happen during the night.

>> And every time it's "mlnetd" - which may just be a coincidence (possibly
>> brought on by that being the most commonly run thing on your box), but it
>> certainly looks like it could also be an indication of the source of the
>> corruption.

Well, most of the time I use only X11+ctwm+aterm+vim+gcc (and sometimes
mozilla or xpdf) so the fact is that mlnetd is the best candidate for
such things since it is the only one on my box which uses resources so
intensively (a few hundrets open sockets constantly being opened and
closed, ram usage ~10% of 512MB, cpu usage ~20% of D1200, etc.).

>> I'll have to think about this, but quite frankly I'm also hoping to see
>> more of a pattern about what this is all about. Can you keep your oopses
>> up somewhere? Maybe opening a bug on bugme.osdl.org? Even though I don't
>> use bugme personally, it's good to keep the record around when we don't
>> immediately see the reason for something..

Sure, I will keep all the oopses. For now I'm gonna collect them on
my webpage in http://secprog.org/who/rs/linux/ (I will report when there
is something new so there is no need to poll() ;>). And then if you are
interested in registering them in bugme, will do it.

Btw. Linus, there is no need CC'ing messages to my e-mail. I will follow
this thread on lkml.

nils.
-- 
"Blessed is the man, who having nothing to say, abstains from giving wordy
evidence of the fact."  -- http://secprog.org/who/rs/quote.php?id=1

       reply	other threads:[~2003-12-08 22:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <10kzo-7mZ-11@gated-at.bofh.it>
     [not found] ` <10m88-2wd-1@gated-at.bofh.it>
     [not found]   ` <10xdJ-28r-23@gated-at.bofh.it>
     [not found]     ` <10xdJ-28r-25@gated-at.bofh.it>
     [not found]       ` <10xdJ-28r-21@gated-at.bofh.it>
2003-12-08 22:28         ` Rafal Skoczylas [this message]
2003-12-08  3:46 2.6.test11 bug Rafal Skoczylas
2003-12-08  4:17 ` William Lee Irwin III
2003-12-08  5:17 ` Linus Torvalds
2003-12-08  9:02   ` Xavier Bestel
     [not found]   ` <20031208161742.GB9087@secprog.org>
     [not found]     ` <Pine.LNX.4.58.0312080848560.13236@home.osdl.org>
2003-12-08 17:12       ` Linus Torvalds
     [not found]         ` <20031209194827.GA22265@secprog.org>
     [not found]           ` <Pine.LNX.4.58.0312091221440.21456@home.osdl.org>
2003-12-09 22:31             ` Rafal Skoczylas
2003-12-09 23:26               ` Linus Torvalds
  -- strict thread matches above, loose matches on Subject: below --
2003-12-08  2:24 Gordon Cormack
2003-12-08  2:37 ` Linus Torvalds

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=20031208222842.GA27131@secprog.org \
    --to=nils@secprog.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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