From: Ben Hutchings <ben@decadent.org.uk>
To: paul.szabo@sydney.edu.au, 695182@bugs.debian.org
Cc: dave@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, pavel@ucw.cz
Subject: Re: Bug#695182: [RFC] Reproducible OOM with just a few sleeps
Date: Thu, 31 Jan 2013 13:38:49 +0000 [thread overview]
Message-ID: <1359639529.31386.49.camel@deadeye.wl.decadent.org.uk> (raw)
In-Reply-To: <201301310907.r0V974j9017335@como.maths.usyd.edu.au>
[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]
On Thu, 2013-01-31 at 20:07 +1100, paul.szabo@sydney.edu.au wrote:
> Dear Ben,
>
> Thanks for the repeated explanations.
>
> > PAE was a stop-gap ...
> > ... [PAE] completely untenable.
>
> Is this a good time to withdraw PAE, to tell the world that it does not
> work? Maybe you should have had such comments in the code.
>
> Seems that amd64 now works "somewhat": on Debian the linux-image package
> is tricky to install,
If you do an i386 (userland) installation then you must either select
expert mode to get a choice of kernel packages, or else install the
'amd64' kernel package afterward.
> and linux-headers is even harder.
In what way?
> Is there work being done to make this smoother?
[...]
Debian users are now generally installing a full amd64 (userland and
kernel installation. The default installation image linked from
www.debian.org is the 32/64-bit net-installer which will install amd64
if the system is capable of it.
Based on your experience I might propose to change the automatic kernel
selection for i386 so that we use 'amd64' on a system with >16GB RAM and
a capable processor.
Ben.
--
Ben Hutchings
If more than one person is responsible for a bug, no one is at fault.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-01-31 13:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 3:31 paul.szabo
2013-01-14 15:00 ` Dave Hansen
2013-01-14 20:36 ` paul.szabo
2013-01-15 0:34 ` Bug#695182: " Ben Hutchings
2013-01-15 0:56 ` Dave Hansen
2013-01-15 2:16 ` paul.szabo
2013-01-30 12:51 ` Pavel Machek
2013-01-30 15:32 ` Dave Hansen
2013-01-30 19:40 ` paul.szabo
2013-01-31 5:15 ` Bug#695182: " Ben Hutchings
2013-01-31 9:07 ` paul.szabo
2013-01-31 13:38 ` Ben Hutchings [this message]
2013-01-31 23:06 ` paul.szabo
2013-02-01 1:07 ` Ben Hutchings
2013-02-01 2:12 ` paul.szabo
2013-02-01 2:57 ` Ben Hutchings
2013-02-01 3:13 ` paul.szabo
2013-02-01 4:38 ` Phil Turmel
2013-02-01 10:20 ` Pavel Machek
2013-02-01 10:25 ` PAE problems was " Pavel Machek
2013-02-01 16:57 ` H. Peter Anvin
2013-02-01 17:45 ` Ben Hutchings
2013-02-07 0:28 ` Dave Hansen
2013-02-10 19:09 ` Pavel Machek
2013-02-17 9:10 ` Simon Jeons
2013-02-24 22:10 ` paul.szabo
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=1359639529.31386.49.camel@deadeye.wl.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=695182@bugs.debian.org \
--cc=dave@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paul.szabo@sydney.edu.au \
--cc=pavel@ucw.cz \
/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®