On 2020-02-08 16:40, Otto Moerbeek wrote:
> When booting, the contents of the existing dmesg buffer are examined.
> If the current contents are deemed to be a dmesg, it is not cleared.
> It's possible the (random) contents of the buffer are seen as valid by
> chance and are thus regarded as dmesg c
On 2020/02/10 13:11, whistlez...@riseup.net wrote:
> On Mon, Feb 10, 2020 at 09:45:06AM -, Stuart Henderson wrote:
> > On 2020-02-10, Janne Johansson wrote:
> > > Den lör 8 feb. 2020 kl 11:31 skrev :
> > >
> > >> Hi,
> > >> I have some strange output from dmesg, what could be ?
> > >> At the f
On Mon, Feb 10, 2020 at 09:45:06AM -, Stuart Henderson wrote:
> On 2020-02-10, Janne Johansson wrote:
> > Den lör 8 feb. 2020 kl 11:31 skrev :
> >
> >> Hi,
> >> I have some strange output from dmesg, what could be ?
> >> At the follwoing link I've posted some screenshots:
> >> https://postimg.
On 2020-02-10, Janne Johansson wrote:
> Den lör 8 feb. 2020 kl 11:31 skrev :
>
>> Hi,
>> I have some strange output from dmesg, what could be ?
>> At the follwoing link I've posted some screenshots:
>> https://postimg.cc/gallery/1o4wsaw74/
>>
>
> dmesg is contained in a memory buffer with (hopeful
Den lör 8 feb. 2020 kl 11:31 skrev :
> Hi,
> I have some strange output from dmesg, what could be ?
> At the follwoing link I've posted some screenshots:
> https://postimg.cc/gallery/1o4wsaw74/
>
dmesg is contained in a memory buffer with (hopefully) room for more than
one dmesg, so you can get
p
Thank you. Yes they are truly superb devices. I’m using the RAM that it
came with, but I did change the mSATA SSD to a Samsung Evo. I haven’t found
time to investigate the weird output, but I don’t suspect any corruption -
the device works fine. Probably some garbage from previous boots as was
ment
Justin Noor wrote:
> I have the same output on a Protecli firewall device (it's not in
> production yet) running 6.6 stable, and have yet to figure out what it
> is.
> I'm planning to spend some time on it next week. It's a brand new device
> and there were no errors during installation.
>
> Spec
On Sat, Feb 08, 2020 at 03:27:55PM -0500, Bryan Steele wrote:
> On Sat, Feb 08, 2020 at 11:28:41AM +0100, whistlez...@riseup.net wrote:
> > Hi,
> > I have some strange output from dmesg, what could be ?
> > At the follwoing link I've posted some screenshots:
> > https://postimg.cc/gallery/1o4wsaw74
On Sat, Feb 08, 2020 at 11:28:41AM +0100, whistlez...@riseup.net wrote:
> Hi,
> I have some strange output from dmesg, what could be ?
> At the follwoing link I've posted some screenshots:
> https://postimg.cc/gallery/1o4wsaw74/
> Thank you
I thought this was pretty well known, but you're looking
On Sat, Feb 08, 2020 at 11:12:47AM +, Ottavio Caruso wrote:
> On 08/02/2020 10:28, whistlez...@riseup.net wrote:
> > Hi,
> > I have some strange output from dmesg, what could be ?
> > At the follwoing link I've posted some screenshots:
> > https://postimg.cc/gallery/1o4wsaw74/
> > Thank you
>
On February 8, 2020 2:24:21 PM UTC, Justin Noor wrote:
>I have the same output on a Protecli firewall device (it’s not in
>production yet) running 6.6 stable, and have yet to figure out what it
>is.
I have seen similar on an intel i3 but then it has just been short term
(snapshot or maybe partic
I have the same output on a Protecli firewall device (it’s not in
production yet) running 6.6 stable, and have yet to figure out what it is.
I’m planning to spend some time on it next week. It’s a brand new device
and there were no errors during installation.
Specs:
- Intel Dual Core Celeron J
> 8. feb. 2020 kl. 11:28 skrev whistlez...@riseup.net:
>
> Hi,
> I have some strange output from dmesg, what could be ?
> At the follwoing link I've posted some screenshots:
> https://postimg.cc/gallery/1o4wsaw74/
Is this running on bare metal, or under a hypervisor of some sort?
I vaguely re
On 08/02/2020 10:28, whistlez...@riseup.net wrote:
Hi,
I have some strange output from dmesg, what could be ?
At the follwoing link I've posted some screenshots:
https://postimg.cc/gallery/1o4wsaw74/
Thank you
All I can think of is filesystem corruption.
--
Ottavio Caruso
Hi,
I have some strange output from dmesg, what could be ?
At the follwoing link I've posted some screenshots:
https://postimg.cc/gallery/1o4wsaw74/
Thank you
On October 15, 2015 8:32:43 AM GMT+02:00, Stefan Wollny
wrote:
>Am 10/15/15 um 03:23 schrieb Stuart Henderson:
>>> kvm_mkdb(31159): syscall 16
>> ..
>>> > kvm_mkdb(31287): syscall 16
>>> > bzip2(6396): syscall 5
>>> > smtpctl(24717): syscall 5
>>> > smtpctl(4120): syscall 5
>> I think these parti
Am 10/15/15 um 03:23 schrieb Stuart Henderson:
>> kvm_mkdb(31159): syscall 16
> ..
>> > kvm_mkdb(31287): syscall 16
>> > bzip2(6396): syscall 5
>> > smtpctl(24717): syscall 5
>> > smtpctl(4120): syscall 5
> I think these particular ones should all be gone with the newer
> version that you're now ru
On 2015-10-14, Stefan Wollny wrote:
> Hi there! A couple of days ago I managed to reactivate my iMac by
> installing a SSD. Beside the usual glitches from some nVidia-stuff the
> machine works fine - running OpenBSD, of course! :-) With Theo's request
> on checking dmesg for pledge(2)-related erro
Hi there! A couple of days ago I managed to reactivate my iMac by
installing a SSD. Beside the usual glitches from some nVidia-stuff the
machine works fine - running OpenBSD, of course! :-) With Theo's request
on checking dmesg for pledge(2)-related errors I stumbled upon the
following:$ dmesg | gr
Running -current (updated 5/19/12) and saw these entries today:
=
pf: pfi_table_update: cannot set 1 new addresses into table fxp1:0: 12
pf: pfi_table_update: cannot set 1 new addresses into table fxp1:network: 12
pf: pfi_table_update: cannot set 1 new addres
I recently purchased 3x 1U rack servers and all of them seem to give
me an internal compiler error when compiling (almost anything, but
sometimes I can get lucky). I've ran a memtest86 overnight without any
problems, so I assume memory is ok. I ran a benchmark program
(lmbench) to see if anything f
21 matches
Mail list logo
