From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] apache: Update to 2.4.38
Date: Wed, 06 Feb 2019 17:45:22 +0000 [thread overview]
Message-ID: <386FEA60-BB2C-4FC0-B4A3-E638A7CD9C82@ipfire.org> (raw)
In-Reply-To: <4e9f22f1-bd2b-7b19-a9fd-36a69e1fcd8d@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
Why are you running the Duo Box on 32 bit? It supports 64, too
> On 6 Feb 2019, at 17:32, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> Hi,
>
> On 05.02.2019 21:57, Michael Tremer wrote:
>> Well in that case, are you sure that your hardware supports SSE2?
>
> Hm. Not sure.
>
> Its a Duo Box, Profil:
> https://fireinfo.ipfire.org/profile/5f68a6360ffbecb6877dcac75f5b8c8030f43ce8
>
>>> On 5 Feb 2019, at 17:45, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>>>
>>> Hi,
>>>
>>> On 05.02.2019 18:30, Michael Tremer wrote:
>>>> Why did the reboot fail?
>>>
>>> Good question.
>>>
>>> Boot screen was flooded with "Bus error" messages and several services
>>> failed to start. A lot. 'hostapd', unbound', ... Too much to count.
>>
>> A bus error is a problem accessing memory.
>
> I never had any problem with RAM with the Duo Box (4 GB), but on weekend
> I hope to have the time to look further into this...
>
> Best,
> Matthias
>
>>> ...
next prev parent reply other threads:[~2019-02-06 17:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 17:06 Matthias Fischer
2019-02-01 17:13 ` Michael Tremer
2019-02-01 17:44 ` Matthias Fischer
2019-02-01 17:47 ` Michael Tremer
2019-02-01 18:07 ` Matthias Fischer
2019-02-04 22:20 ` Michael Tremer
2019-02-05 17:24 ` Matthias Fischer
2019-02-05 17:30 ` Michael Tremer
2019-02-05 17:45 ` Matthias Fischer
2019-02-05 20:57 ` Michael Tremer
2019-02-06 17:32 ` Matthias Fischer
2019-02-06 17:45 ` Michael Tremer [this message]
2019-02-06 17:53 ` Matthias Fischer
2019-02-09 20:04 ` Matthias Fischer
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=386FEA60-BB2C-4FC0-B4A3-E638A7CD9C82@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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