From: Linus Torvalds <torvalds@osdl.org>
To: Matt Mackall <mpm@selenic.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test3-mm3 - cp -a kills machine
Date: Thu, 21 Aug 2003 22:59:46 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0308212259000.3258-100000@home.osdl.org> (raw)
In-Reply-To: <20030822015658.GD3958@waste.org>
On Thu, 21 Aug 2003, Matt Mackall wrote:
> > No console message either. Repeated after taking out local APIC
> > support, same thing.
>
> Similar repeatable problems with periodic fsck on ext3 root. Appears
> not to be ext3 or loop, perhaps something IDE-related in Linus' bk
> tree added between mm2 and mm3.
The more you can track this down, the easier it will be for us. Willing to
triangulate a bit? For example, just start testing the suspicious parts of
the patch?
Linus
next prev parent reply other threads:[~2003-08-22 5:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 22:08 2.6.0-test3-mm3 - cp -a kills machine Matt Mackall
2003-08-22 1:49 ` Zwane Mwaikambo
2003-08-22 14:58 ` Matt Mackall
2003-08-22 1:56 ` Matt Mackall
2003-08-22 5:59 ` Linus Torvalds [this message]
2003-08-23 17:50 ` Matt Mackall
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=Pine.LNX.4.44.0308212259000.3258-100000@home.osdl.org \
--to=torvalds@osdl.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
/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;
as well as URLs for NNTP newsgroup(s).