On Sat, Sep 12, 2015 at 03:09:54PM +0200, Martin Pieuchot wrote:
> > > Interesting, the previous report I had with similar symptoms was about a
> > > machine using nested NFS mounts from two different servers.
> >
> > Well, i don't think it's nfs related. Also a ping, nfs, sftp
> > transfe
On Sat, Sep 12, 2015 at 03:09:54PM +0200, Martin Pieuchot wrote:
> On 12/09/15(Sat) 14:45, Mark Patruck wrote:
> > On Sat, Sep 12, 2015 at 11:07:07AM +0200, Martin Pieuchot wrote:
> > > On 11/09/15(Fri) 18:56, Mark Patruck wrote:
> > > > On Fri, Sep 11, 2015 at 06:27:36PM +0200, Martin Pieuchot wro
On 12/09/15(Sat) 14:45, Mark Patruck wrote:
> On Sat, Sep 12, 2015 at 11:07:07AM +0200, Martin Pieuchot wrote:
> > On 11/09/15(Fri) 18:56, Mark Patruck wrote:
> > > On Fri, Sep 11, 2015 at 06:27:36PM +0200, Martin Pieuchot wrote:
> > > > On 11/09/15(Fri) 18:07, Mark Patruck wrote:
> > > > > dmesg b
On Sat, Sep 12, 2015 at 11:07:07AM +0200, Martin Pieuchot wrote:
> On 11/09/15(Fri) 18:56, Mark Patruck wrote:
> > On Fri, Sep 11, 2015 at 06:27:36PM +0200, Martin Pieuchot wrote:
> > > On 11/09/15(Fri) 18:07, Mark Patruck wrote:
> > > > dmesg below is currently running, but it also didn't work wit
On 11/09/15(Fri) 18:56, Mark Patruck wrote:
> On Fri, Sep 11, 2015 at 06:27:36PM +0200, Martin Pieuchot wrote:
> > On 11/09/15(Fri) 18:07, Mark Patruck wrote:
> > > dmesg below is currently running, but it also didn't work with a 2 week
> > > old snapshot from the local mirror. (system was freshly
On Fri, Sep 11, 2015 at 06:27:36PM +0200, Martin Pieuchot wrote:
> On 11/09/15(Fri) 18:07, Mark Patruck wrote:
> > dmesg below is currently running, but it also didn't work with a 2 week
> > old snapshot from the local mirror. (system was freshly installed)
> >
> > Note: the machine hasn't been us
On 11/09/15(Fri) 18:07, Mark Patruck wrote:
> dmesg below is currently running, but it also didn't work with a 2 week
> old snapshot from the local mirror. (system was freshly installed)
>
> Note: the machine hasn't been used over the last two months, so i've
> double checked battery, memory, psu.
dmesg below is currently running, but it also didn't work with a 2 week
old snapshot from the local mirror. (system was freshly installed)
Note: the machine hasn't been used over the last two months, so i've
double checked battery, memory, psu.
OpenBSD 5.8-current (GENERIC.MP) #0: Mon Sep 7 15:5
I had to reboot the system last evening and 'unfortunately' the error
doesn't show up right now. However...there were lots of changes to src
the last hours, so i'll try with a new snap today/tomorrow and report
back. This way i also have fresh values (vmstat -i, netstat -m, ...)
before and after th
On 11/09/15(Fri) 17:12, Mark Patruck wrote:
> I had to reboot the system last evening and 'unfortunately' the error
> doesn't show up right now. However...there were lots of changes to src
> the last hours, so i'll try with a new snap today/tomorrow and report
> back. This way i also have fresh val
> Could you also include the output of "ifconfig", "netstat -nf inet" and
> "netsat -rn"?
"vmstat -i" might be useful as well.
Mark Patruck wrapped.cx> writes:
>
> over the last few weeks i'm having a strange issue here running amd64
> -current (last updated 3 days before)
>
> ### system
> Supermicro X7SPA-HF-D525 1,8Ghz Atom
> 4 GB RAM
> 1x 128GB SSD (system)
> 1x 6TB /1x 4TB HDD (NFS exported)
>
> Everything works fi
Hi,
over the last few weeks i'm having a strange issue here running amd64
-current (last updated 3 days before)
### system
Supermicro X7SPA-HF-D525 1,8Ghz Atom
4 GB RAM
1x 128GB SSD (system)
1x 6TB /1x 4TB HDD (NFS exported)
Everything works fine the first few hours, then suddenly
- the system
13 matches
Mail list logo
