On 30/08/2013 06:39, Paul Chakravarti wrote:
I am running FreeBSD 9.1-RELEASE-p6 and am getting multiple random
reboots daily (sometimes hours apart, sometimes minutes).
I suspect that it might be a hardware issue however have tried
extended runs (upto 8 hours) of 'cpuburn' and &#x
gly cheap at £2.49/month
>> - see http://www.ovh.co.uk/dedicated_servers/kimsufi.xml).
>>
>> I am running FreeBSD 9.1-RELEASE-p6 and am getting multiple random reboots
>> daily (sometimes hours apart, sometimes minutes).
>>
>> Unfortunately there is no evide
i.xml).
>
> I am running FreeBSD 9.1-RELEASE-p6 and am getting multiple random reboots
> daily (sometimes hours apart, sometimes minutes).
>
> Unfortunately there is no evidence anywhere on the system of the cause of
> these, in particular nothing at all in logs other then the
You're lucky to get your KS-2G… I'm still waiting for mine since one month.
Maybe some crypto and/or UFS problems?
For the moment I have the old KS-2G at 9€HT (sorry for conversion), no
crypto and I ran 9.1-RELEASE without any problem. Or just one.
First I used UFS and during a night
Hello,
I was wondering if anyone else is having reboot issues running FreeBSD 9.1 on
the OVH KS-2G low-cost dedicated servers (amazingly cheap at £2.49/month - see
http://www.ovh.co.uk/dedicated_servers/kimsufi.xml).
I am running FreeBSD 9.1-RELEASE-p6 and am getting multiple random reboots
Thanks for the quick answer!
Konstantin Belousov writes:
> -m32 does not work on stable. You need HEAD.
So I should have better luck with a binary compiled on i386, right?
--
Regards,
Mike
___
freebsd-stable@freebsd.org mailing list
http://lists.f
On Tue, Jul 09, 2013 at 08:08:22PM +0200, Michael Sperber wrote:
>
> I noticed that scsh (which only runs in 32-bit mode) fails on amd64. I
> narrowed it down to a regex malfunction (I think). This program:
>
> snip
> #include
> #include
>
> int
> main(void)
> {
> regex_t r;
> in
I noticed that scsh (which only runs in 32-bit mode) fails on amd64. I
narrowed it down to a regex malfunction (I think). This program:
snip
#include
#include
int
main(void)
{
regex_t r;
int status = regcomp(&r, "/afs", REG_EXTENDED);
size_t nmatch = 1 + r.re_nsub;
regmatch
On Wednesday, February 13, 2013 6:56:06 pm CeDeROM wrote:
> On Wed, Feb 13, 2013 at 4:48 PM, John Baldwin wrote:
> >> The simple answer that I have deduced is that APIC is MANDATORY for
> >> AMD64 machines and they won't run otherwise? This is why generic AMD64
> >> install fails when no APIC is e
On Wed, Feb 13, 2013 at 4:48 PM, John Baldwin wrote:
>> The simple answer that I have deduced is that APIC is MANDATORY for
>> AMD64 machines and they won't run otherwise? This is why generic AMD64
>> install fails when no APIC is enabled in the VBox?
>
> No, it is not quite like that. x86 machin
On Monday, February 11, 2013 4:34:37 pm CeDeROM wrote:
> On Mon, Feb 11, 2013 at 10:06 PM, John Baldwin wrote:
> > On Sunday, February 10, 2013 1:16:16 pm CeDeROM wrote:
> >> Hey :-) I have just noticed that booting installation media for
> >> FreeBSD 9.1-RELEASE AM
On Tue, Feb 12, 2013 at 12:53 AM, Jakub Lach wrote:
> As far as I remember, there is no apic option in amd64 kernel,
> because it's always included.
Yup, I guess that note in the handbook should be updated :-)
CPU: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GHz (2394.03-MHz K8-class CPU)
Ori
As far as I remember, there is no apic option in amd64 kernel,
because it's always included.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/9-1-RELEASE-AMD64-crash-under-VBox-4-2-6-when-IO-APIC-is-disabled-tp5785747p5786129.html
Sent from the freebsd-stable mailing list
On Mon, Feb 11, 2013 at 10:06 PM, John Baldwin wrote:
> On Sunday, February 10, 2013 1:16:16 pm CeDeROM wrote:
>> Hey :-) I have just noticed that booting installation media for
>> FreeBSD 9.1-RELEASE AMD64 from ISO bootonly under VirtualBox 4.2.6
>> results in a kernel pa
On Sunday, February 10, 2013 1:16:16 pm CeDeROM wrote:
> Hey :-) I have just noticed that booting installation media for
> FreeBSD 9.1-RELEASE AMD64 from ISO bootonly under VirtualBox 4.2.6
> results in a kernel panic both when ACPI is enabled and disabled in
> the boot dialog s
Hey :-) I have just noticed that booting installation media for
FreeBSD 9.1-RELEASE AMD64 from ISO bootonly under VirtualBox 4.2.6
results in a kernel panic both when ACPI is enabled and disabled in
the boot dialog screen (seems different cause of crash), when IO APIC
is disabled in VBox (which is
Hello Andriy,
Tuesday, December 25, 2012, 12:18:23 AM, you wrote:
>> I recompiled the kernel and is running with options you specified (I
>> enabled DEBUG in the file).
>>
>> Anyway even at boot time I started getting following warnings, is this
>> anything:
> These witness warning are OK-ish.
on 25/12/2012 02:11 Derek Kulinski said the following:
> Hello Andriy,
>
> Monday, December 24, 2012, 3:28:00 PM, you wrote:
>
>> I've looked through the cores and it does look like in all cases some sort of
>> memory corruption is a precursor to a subsequent crash.
>
>> I can't decidedly say if
Hello Andriy,
Monday, December 24, 2012, 3:28:00 PM, you wrote:
> I've looked through the cores and it does look like in all cases some sort of
> memory corruption is a precursor to a subsequent crash.
> I can't decidedly say if the corruptions are caused by the hardware, by some
> code overwrit
on 24/12/2012 20:17 Derek Kulinski said the following:
> Hello Andriy,
>
> Monday, December 24, 2012, 8:01:26 AM, you wrote:
>
>> on 24/12/2012 00:23 Derek Kulinski said the following:
>>> Dumping 3701 out of 8072
>>> MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%
>
>> So do you have the
Hello Mark,
Monday, December 24, 2012, 12:46:53 PM, you wrote:
> On Mon, Dec 24, 2012 at 10:17:19AM -0800, Derek Kulinski wrote:
>> Yes, but they are 3.5GB each. I attached text dump to GNATS but I can
>> resend it to you
> We have a limit of 500K on GNATS PRs. For something that huge, a PR
> d
On Mon, Dec 24, 2012 at 10:17:19AM -0800, Derek Kulinski wrote:
> Yes, but they are 3.5GB each. I attached text dump to GNATS but I can
> resend it to you
We have a limit of 500K on GNATS PRs. For something that huge, a PR
database is really not the right place for it -- please post the dumps
som
Hello Andriy,
Monday, December 24, 2012, 8:01:26 AM, you wrote:
> on 24/12/2012 00:23 Derek Kulinski said the following:
>> Dumping 3701 out of 8072 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%
> So do you have the crash dump(s)?
Yes, but they are 3.5GB each. I attached text dump to GNA
on 24/12/2012 00:23 Derek Kulinski said the following:
> Dumping 3701 out of 8072 MB:..1%..11%..21%..31%..41%..51%..61%..71%..81%..91%
So do you have the crash dump(s)?
--
Andriy Gapon
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.or
tests successfully.
I never had this type of issue on 9.0, and not much changed in my
kernel config besides installing WiFi card.
System:
FreeBSD chinatsu.takeda.tk 9.1-RELEASE FreeBSD 9.1-RELEASE #2 r244482: Wed Dec
19 23:28:15 PST 2012 r...@chinatsu.takeda.tk:/usr/obj/usr/src/sys/CHINATSU
amd64
On 06/12/2012 22:26, David Demelier wrote:
Hello,
I'm trying to make as small as possible a FreeBSD installation for my
Alix 2D2, I did it with 8.1-RELEASE so, a lot of changes appeared I
think.
I'm trying to make TARGET_ARCH=i386 buildworld and it fails at:
===> sys/boot/i386/gptboot (all)
Hello,
I'm trying to make as small as possible a FreeBSD installation for my
Alix 2D2, I did it with 8.1-RELEASE so, a lot of changes appeared I think.
I'm trying to make TARGET_ARCH=i386 buildworld and it fails at:
===> sys/boot/i386/gptboot (all)
Warning: Object directory not changed from o
012 5:30 AM, "Ronald Klop"
wrote:
On Wed, 05 Dec 2012 12:16:25 +0100, Shiv. Nath <
shiv.nath@digital-infotech.**net >
wrote:
anyone knows what to do?
Maybe wait until 9.1-RELEASE is actually released.
Ronald.
[root@rock]# freebsd-update -r 9.1-REL
On Wed, 05 Dec 2012 12:16:25 +0100, Shiv. Nath
wrote:
anyone knows what to do?
Maybe wait until 9.1-RELEASE is actually released.
Ronald.
[root@rock]# freebsd-update -r 9.1-RELEASE upgrade
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 9.1-RC3
anyone knows what to do?
[root@rock]# freebsd-update -r 9.1-RELEASE upgrade
Looking up update.FreeBSD.org mirrors... 3 mirrors found.
Fetching metadata signature for 9.1-RC3 from update5.FreeBSD.org... done.
Fetching metadata index... done.
Fetching 1 metadata patches. done.
Applying metadata
On 11/26/12 23:48, Bas Smeelen wrote:
On 11/26/12 23:36, Rick Miller wrote:
On Mon, Nov 26, 2012 at 5:25 PM, Bas Smeelen wrote:
Hi
Just modify newvers.sh to 9.1-RELEASE recompile and your on RELEASE :)
Who has a no non-release policy, management?
It's not just management,
Just to sum
On 11/26/12 23:36, Rick Miller wrote:
On Mon, Nov 26, 2012 at 5:25 PM, Bas Smeelen wrote:
Hi
Just modify newvers.sh to 9.1-RELEASE recompile and your on RELEASE :)
Who has a no non-release policy, management?
It's not just management,
checked, they don't have a clue, that's
On Mon, Nov 26, 2012 at 5:25 PM, Bas Smeelen wrote:
> Hi
> Just modify newvers.sh to 9.1-RELEASE recompile and your on RELEASE :)
> Who has a no non-release policy, management?
It's not just management, but also software engineers, architects, and
business folks. When a company
3 has been really stable for me, but we have a no non-release policy on
production machines.
We're so far behind compared to
http://www.freebsd.org/releases/9.1R/schedule.html (which has already been
updated multiple times because of delay after delay)
Hi
Just modify newvers.sh to 9.1-RELEASE
Hi. With the recent delays from the security incident and the three SAs out of
the way, what now are we waiting for? I think we should just get rid of the
release schedule on FreeBSD.org if we aren't even going to be close to the set
dates.
RC3 has been really stable for me, but we have a no no
All
Can someone merge in r240315 into the 9.1 release. This fixes a few bugs in
pc-sysinstall . I am planning on using pc-sysinstall for automated network
installs of 9.1-RELEAE ( not pc-bsd ) much akin to jumpstart with sysinstall in
past releases . With out this commit a few options for
Just a quick note to say we have settled on a target schedule for the
FreeBSD 9.1 Release. The schedule itself is here:
http://www.freebsd.org/releases/9.1R/schedule.html
The highlights:
Code Freeze:July 2nd, 2012
BETA1: July 6th, 2012
RC1:July 20th, 2012
RC2
37 matches
Mail list logo
