On Thu, Nov 21, 2013 at 12:42 PM, Ed Maste wrote:
> The variable name is "hw.memtest.tests" as it's intended to be
> extended to a bitmap of tests to run at boot, with other bits
> representing more comprehensive tests.
>
> -Ed
>
> commit 58f501f70427ce2aeb9c8b18d2b7bec543818dae
> Author: Ed Maste
On 16 November 2013 17:49, Eitan Adler wrote:
> On Sat, Nov 16, 2013 at 4:12 PM, Zach Crum wrote:
>> This setting is not listed in /boot/defaults/loader.conf. Is it supposed to
>> be singular or plural?
>
> Plural.
>
> I will commit the patch.
The FAQ update patch looks fine.
> Does any know of
On Sat, Nov 16, 2013 at 4:12 PM, Zach Crum wrote:
> This setting is not listed in /boot/defaults/loader.conf. Is it supposed to
> be singular or plural?
Plural.
I will commit the patch.
Does any know of cases where this memory test actually catches errors?
How important is it?
--
Eitan Adler
On 2013-11-16 13:36, James R. Van Artsdalen wrote:
> On 11/16/2013 8:52 AM, Allan Jude wrote:
>> I see this was in the release notes for 9.0 and 8.3, but other than
>> that, I don't see how anyone was supposed to find out about this.
>> Maybe it would make sense to print 'Starting memory test, set
On 11/16/2013 8:52 AM, Allan Jude wrote:
> I see this was in the release notes for 9.0 and 8.3, but other than
> that, I don't see how anyone was supposed to find out about this.
> Maybe it would make sense to print 'Starting memory test, set
> hw.memtest.test=0 to disable' before that starts, so
On 2013-11-16 00:48, Matthias Petermann wrote:
> Hello James,
>
> Am 16.11.2013 05:37, schrieb James R. Van Artsdalen:
> > Asus Z9PA-U8 motherboard, 256GB of RAM, 2.4 GHz Xeon E5-2695 v2,
> > FreeBSD 11.0-CURRENT r258092
>
> > There is a two minute pause when booting, after the loader's SMAP
> > di
At the risk of facetiousness, the nice thing about FreeBSD is that you
have to deal with this problem only a few times per year. ;)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, s
On Sat, 16 Nov 2013 06:48:11 +0100
Matthias Petermann wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello James,
>
> Am 16.11.2013 05:37, schrieb James R. Van Artsdalen:
> > Asus Z9PA-U8 motherboard, 256GB of RAM, 2.4 GHz Xeon E5-2695 v2,
> > FreeBSD 11.0-CURRENT r258092
> >
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello James,
Am 16.11.2013 05:37, schrieb James R. Van Artsdalen:
> Asus Z9PA-U8 motherboard, 256GB of RAM, 2.4 GHz Xeon E5-2695 v2,
> FreeBSD 11.0-CURRENT r258092
>
> There is a two minute pause when booting, after the loader's SMAP
> display and t
On 2013-11-15 23:37, James R. Van Artsdalen wrote:
> Asus Z9PA-U8 motherboard, 256GB of RAM, 2.4 GHz Xeon E5-2695 v2, FreeBSD
> 11.0-CURRENT r258092
>
> There is a two minute pause when booting, after the loader's SMAP
> display and the initial kernel output,
>
> Does anyone know what's going on he
In message: <[EMAIL PROTECTED]>
Andre Guibert de Bruet <[EMAIL PROTECTED]> writes:
: What does pciconf -vl show on the affected machine(s)?
I think you'll find that not relevant. I've seen this behavior with
the newer ata code and IDE controllers that had no IDE devices
connected to t
What does pciconf -vl show on the affected machine(s)?
> Andre Guibert de Bruet | Enterprise Software Consultant >
> Silicon Landmark, LLC. | http://siliconlandmark.com/>
On Sun, 17 Aug 2003, Bill Moran wrote:
> Mike Atamas wrote:
> > When my system boots it seems to stall when it gets here
Bill Moran wrote:
> > It stalls for about 20-30 seconds and then continues booting. I can
> > not figure out what the problem is or how to solve it. Has anyone
> > had similar issues.
>
> I've seen this on various hardware. I actually have a 200mhz machine
> sitting here that has always done this
On Mon, 18 Aug 2003, Kevin Oberman wrote:
> > Date: Mon, 18 Aug 2003 11:09:05 -0400 (EDT)
> > From: Andre Guibert de Bruet <[EMAIL PROTECTED]>
> >
> > On Mon, 18 Aug 2003, Kevin Oberman wrote:
> >
> > > > From: Bill Moran <[EMAIL PROTECTED]>
> > > >
> > > > Matthew D. Fuller wrote:
> > > > > On S
> Date: Mon, 18 Aug 2003 11:09:05 -0400 (EDT)
> From: Andre Guibert de Bruet <[EMAIL PROTECTED]>
>
>
> [CC list trimed]
>
> On Mon, 18 Aug 2003, Kevin Oberman wrote:
>
> > > From: Bill Moran <[EMAIL PROTECTED]>
> > >
> > > Matthew D. Fuller wrote:
> > > > On Sun, Aug 17, 2003 at 02:55:46PM -040
[CC list trimed]
On Mon, 18 Aug 2003, Kevin Oberman wrote:
> > From: Bill Moran <[EMAIL PROTECTED]>
> >
> > Matthew D. Fuller wrote:
> > > On Sun, Aug 17, 2003 at 02:55:46PM -0400 I heard the voice of
> > > Bill Moran, and lo! it spake thus:
> > >
> > >>My best guess is that the chipset responds
Andre Guibert de Bruet wrote:
> What does pciconf -vl show on the affected machine(s)?
[EMAIL PROTECTED]:0:0: class=0x06 card=0x154110b9 chip=0x154110b9 rev=0x04
hdr=0x00vendor = 'Acer Labs Incorporated (ALi)'
device = 'ALI M1541 Aladdin V/V+ AGP System Controller'
class=
> Date: Mon, 18 Aug 2003 08:45:36 -0400
> From: Bill Moran <[EMAIL PROTECTED]>
> Sender: [EMAIL PROTECTED]
>
> Matthew D. Fuller wrote:
> > On Sun, Aug 17, 2003 at 02:55:46PM -0400 I heard the voice of
> > Bill Moran, and lo! it spake thus:
> >
> >>My best guess is that the chipset responds slowl
Andre Guibert de Bruet wrote:
What does pciconf -vl show on the affected machine(s)?
[EMAIL PROTECTED]:0:0: class=0x06 card=0x chip=0x12378086
rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82440/1FX 440FX (Natoma) System Controller'
class= bridge
Matthew D. Fuller wrote:
On Sun, Aug 17, 2003 at 02:55:46PM -0400 I heard the voice of
Bill Moran, and lo! it spake thus:
My best guess is that the chipset responds slowly to probes, thus it
takes a while to get the list of devices from it. However, I've never
looked into it any more than that.
I'
On Sun, 17 Aug 2003 22:35:14 -0400 (EDT)
Andre Guibert de Bruet <[EMAIL PROTECTED]> wrote:
> pciconf -vl
Here is the output that it gave. I included everything because nothing particular
struck me as relavent.
[EMAIL PROTECTED]:0:0: class=0x06 card=0x80ac1043 chip=0x01e010de rev=0xc1
hd
On Sun, Aug 17, 2003 at 02:55:46PM -0400 I heard the voice of
Bill Moran, and lo! it spake thus:
>
> My best guess is that the chipset responds slowly to probes, thus it
> takes a while to get the list of devices from it. However, I've never
> looked into it any more than that.
I've always presu
I have been seeing this for some time (> 2 years) on my ASUS P5A based
K6 system. I have no idea why it's doing it, but I re-boot so
infrequently that I just have not worried about it. It does seem that
it is less likely to happen after a true cold boot. (Cut main power.)
I was seeing this with V4
Mike Atamas wrote:
When my system boots it seems to stall when it gets here:
xa807,0xa400-0xa403,0xa000-0xa007 mem 0xe100-0xe10001ff irq 11 at device 11.
0 on pci1
ata2: at 0xe100 on atapci0
ata3: at 0xe100 on atapci0
It stalls for about 20-30 seconds and then continues booting. I can
24 matches
Mail list logo
