essage-
> > From: owner-freebsd-curr...@freebsd.org
> > [mailto:owner-freebsd-curr...@freebsd.org] On
> > Behalf Of O. Hartmann Sent: Tuesday, July 01, 2014 8:08 AM
> > To: Dimitry Andric
> > Cc: Adrian Chadd; FreeBSD CURRENT
> > Subject: Re: [CURRENT]: weird me
Am Tue, 01 Jul 2014 17:57:26 +0200
Willem Jan Withagen schrieb:
> On 2014-07-01 17:33, O. Hartmann wrote:
> > Am Tue, 01 Jul 2014 17:23:14 +0200
> > Willem Jan Withagen schrieb:
> >
> >> On 2014-07-01 16:48, Rang, Anton wrote:
> >>> DOT => DOD
> >>>
> >>> 444F54 => 444F44
> >>>
> >>> That's a si
On 2014-07-01 17:33, O. Hartmann wrote:
Am Tue, 01 Jul 2014 17:23:14 +0200
Willem Jan Withagen schrieb:
On 2014-07-01 16:48, Rang, Anton wrote:
DOT => DOD
444F54 => 444F44
That's a single-bit flip. Bad memory, perhaps?
Very likely, especially if the system does not have ECC
It just h
orm. dmidecode gives:
Manufacturer: ASUSTeK Computer INC.
Product Name: P5Q-WS
Version: Rev 1.xx
>
>
> >
> > Anton
> >
> > -Original Message-
> > From: owner-freebsd-curr...@freebsd.org
> > [mailto:owner-freebsd-curr...@freebsd.org] On
&
set to completion.
--WjW
Anton
-Original Message-
From: owner-freebsd-curr...@freebsd.org
[mailto:owner-freebsd-curr...@freebsd.org] On Behalf Of O. Hartmann
Sent: Tuesday, July 01, 2014 8:08 AM
To: Dimitry Andric
Cc: Adrian Chadd; FreeBSD CURRENT
Subject: Re: [CURRENT]: weird memory/linke
drian Chadd; FreeBSD CURRENT
Subject: Re: [CURRENT]: weird memory/linker problem?
Am Mon, 23 Jun 2014 17:22:25 +0200
Dimitry Andric schrieb:
> On 23 Jun 2014, at 16:31, O. Hartmann wrote:
> > Am Sun, 22 Jun 2014 10:10:04 -0700
> > Adrian Chadd schrieb:
> >> When th
Am Mon, 23 Jun 2014 17:22:25 +0200
Dimitry Andric schrieb:
> On 23 Jun 2014, at 16:31, O. Hartmann wrote:
> > Am Sun, 22 Jun 2014 10:10:04 -0700
> > Adrian Chadd schrieb:
> >> When they segfault, where do they segfault?
> ...
> > GIMP, LaTeX work, nothing special, but a bit memory consuming reg
Am Mon, 23 Jun 2014 17:22:25 +0200
Dimitry Andric schrieb:
> On 23 Jun 2014, at 16:31, O. Hartmann wrote:
> > Am Sun, 22 Jun 2014 10:10:04 -0700
> > Adrian Chadd schrieb:
> >> When they segfault, where do they segfault?
> ...
> > GIMP, LaTeX work, nothing special, but a bit memory consuming reg
Am Mon, 23 Jun 2014 09:27:46 -0600
Ian Lepore schrieb:
> On Mon, 2014-06-23 at 16:31 +0200, O. Hartmann wrote:
> >
> > I'm out of ideas. Is there a way to stress test the CPU and memory
> > system to check
> > whether RAM, the CPU itself and, as an additional possibility, the
> > disk i/o contro
On Mon, 2014-06-23 at 16:31 +0200, O. Hartmann wrote:
>
> I'm out of ideas. Is there a way to stress test the CPU and memory
> system to check
> whether RAM, the CPU itself and, as an additional possibility, the
> disk i/o controller
> (Intel ICH10)?
>
> Thanks for your patience,
A really good t
On 23 Jun 2014, at 16:31, O. Hartmann wrote:
> Am Sun, 22 Jun 2014 10:10:04 -0700
> Adrian Chadd schrieb:
>> When they segfault, where do they segfault?
...
> GIMP, LaTeX work, nothing special, but a bit memory consuming regrading GIMP)
> I tried
> updating the ports tree and surprisingly the tr
Am Sun, 22 Jun 2014 10:10:04 -0700
Adrian Chadd schrieb:
> When they segfault, where do they segfault?
>
>
>
> -a
Now I get more fun.
After a buildworld and reboot, the box in question is at CURRENT:
FreeBSD 11.0-CURRENT #0 r267782: Mon Jun 23 13:12:56 CEST 2014 amd64
After a reboot, every
Am Sun, 22 Jun 2014 10:10:04 -0700
Adrian Chadd schrieb:
> When they segfault, where do they segfault?
>
>
>
> -a
>
>
I have not investigated this issue so far, since I was convinced - in the first
place -
it is triggered by a defetive memory system. So I rebooted immediately being
glad h
On 2014-06-22 10:56, O. Hartmann wrote:
>
> Hello.
>
> I face a strange problem on a set of CURRENT driven boxes. The systems in
> question are
> all the same version of CURRENT (more or less, a week or so discrepancy).
>
> The boxes affected have 8 GB of RAM and are old-style Core2Duo systems.
When they segfault, where do they segfault?
-a
On 22 June 2014 07:56, O. Hartmann wrote:
>
> Hello.
>
> I face a strange problem on a set of CURRENT driven boxes. The systems in
> question are
> all the same version of CURRENT (more or less, a week or so discrepancy).
>
> The boxes affected
Hello.
I face a strange problem on a set of CURRENT driven boxes. The systems in
question are
all the same version of CURRENT (more or less, a week or so discrepancy).
The boxes affected have 8 GB of RAM and are old-style Core2Duo systems.
The phenomenon:
Starting up the box shows the operati
16 matches
Mail list logo
