On 06/07/2017 01:14 PM, Ben Hutchings wrote:
> On Wed, 2017-06-07 at 18:10 +0100, Ben Hutchings wrote:
>>> CONFIG_SERIAL_8250_RUNTIME_UARTS=16
>> That seems reasonable.
> [...]
>
> Actually, having looked further at what this does, I'm unconvinced
> about changing it. It can always be overrid
Package: linux-image-4.9.0-3-amd64
Severity: medium
When my system boots the Debian installer, it appears to hang at a blank
screen. There are two reasons for this, and two kernel configuration
parameters need to be modified:
CONFIG_SERIAL_8250_RUNTIME_UARTS=16
CONFIG_SERIAL_8250_MID=y
There ar
On 01/30/2013 04:51 AM, Pavel Machek wrote:
> Are you saying that HIGHMEM configuration with 4GB ram is not expected
> to work?
Not really.
The assertion was that 4GB with no PAE passed a forkbomb test (ooming)
while 4GB of RAM with PAE hung, thus _PAE_ is broken.
--
To UNSUBSCRIBE, email to d
On 01/17/2013 01:04 PM, paul.sz...@sydney.edu.au wrote:
>>> On my large machine, 'free' fails to show about 2GB memory ...
>> You probably have a memory hole. ...
>> The e820 map (during early boot in dmesg) or /proc/iomem will let you
>> locate your memory holes.
>
> Now that my machine is runnin
On 01/14/2013 12:36 PM, paul.sz...@sydney.edu.au wrote:
> I understand that more RAM leaves less lowmem. What is unacceptable is
> that PAE crashes or freezes with OOM: it should gracefully handle the
> issue. Noting that (for a machine with 4GB or under) PAE fails where the
> HIGHMEM4G kernel succ
On 01/11/2013 07:31 PM, paul.sz...@sydney.edu.au wrote:
> Seems that any i386 PAE machine will go OOM just by running a few
> processes. To reproduce:
> sh -c 'n=0; while [ $n -lt 1 ]; do sleep 600 & ((n=n+1)); done'
> My machine has 64GB RAM. With previous OOM episodes, it seemed that
> runn
On 01/10/2013 05:46 PM, paul.sz...@sydney.edu.au wrote:
>> > ... I don't believe 64GB of RAM has _ever_ been booted on a 32-bit
>> > kernel without either violating the ABI (3GB/1GB split) or doing
>> > something that never got merged upstream ...
> Sorry to be so contradictory:
>
> psz@como:~$ un
On 01/10/2013 04:46 PM, paul.sz...@sydney.edu.au wrote:
>> Your configuration has never worked. This isn't a regression ...
>> ... does not mean that we expect it to work.
>
> Do you mean that CONFIG_HIGHMEM64G is deprecated, should not be used;
> that all development is for 64-bit only?
My last
On 01/10/2013 01:58 PM, paul.sz...@sydney.edu.au wrote:
> I developed a workaround patch for this particular OOM demo, dropping
> filesystem caches when about to exhaust lowmem. However, subsequently
> I observed OOM when running many processes (as yet I do not have an
> easy-to-reproduce demo of t
9 matches
Mail list logo
