From: Andrea Arcangeli <andrea@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Ion Badulescu <ionut@cs.columbia.edu>, linux-kernel@vger.kernel.org
Subject: Re: 2.2.19 locks up on SMP
Date: Mon, 30 Apr 2001 20:15:47 +0200 [thread overview]
Message-ID: <20010430201547.G19620@athlon.random> (raw)
In-Reply-To: <Pine.LNX.4.33.0104281402090.2487-100000@age.cs.columbia.edu> <E14uHtt-0008KA-00@the-village.bc.nu>
In-Reply-To: <E14uHtt-0008KA-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Mon, Apr 30, 2001 at 06:55:54PM +0100
On Mon, Apr 30, 2001 at 06:55:54PM +0100, Alan Cox wrote:
> A couple. It looks lik the VM changes may have upset something (based on
> reports saying it began at that point). Can you see if 2.2.19pre stuff is
> stable ?
I also have reports but related to the network driver updates. So I
suggest to try again with 2.2.19 but with the drivers/net/* of 2.2.18.
Andrea
next prev parent reply other threads:[~2001-04-30 18:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-28 21:21 2.2.19 locks up on SMP Ion Badulescu
2001-04-28 23:16 ` bert hubert
2001-04-28 23:09 ` idalton
2001-04-28 23:59 ` Tim Moore
2001-04-30 9:22 ` Ion Badulescu
2001-04-30 17:55 ` Alan Cox
2001-04-30 18:15 ` Andrea Arcangeli [this message]
2001-04-30 18:28 ` Andrea Arcangeli
2001-04-30 19:57 ` Alan Cox
2001-04-30 19:59 ` Ion Badulescu
2001-04-30 20:28 ` Mohammad A. Haque
2001-05-01 1:09 ` Ion Badulescu
2001-05-01 4:47 ` Ion Badulescu
2001-05-01 7:27 ` Alan Cox
2001-05-01 7:29 ` Ion Badulescu
2001-05-01 7:47 ` Ion Badulescu
2001-05-01 7:55 ` Ion Badulescu
2001-05-01 9:21 ` Ion Badulescu
2001-05-01 12:09 ` Trond Myklebust
2001-05-01 12:15 ` Ion Badulescu
2001-05-01 13:42 ` Trond Myklebust
2001-05-01 23:48 ` Ion Badulescu
-- strict thread matches above, loose matches on Subject: below --
2001-07-03 10:11 Scott Nursten
2001-07-03 10:48 ` Scott Nursten
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=20010430201547.G19620@athlon.random \
--to=andrea@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ionut@cs.columbia.edu \
--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