I appear to have a machine which will not run RELENG_6_2, though it runs
the released code quite happily. Is there a CVS tag I can use to revert the
sources back to the way they were on RELEASE? I want to be able to
verify that this is and track down what changed! I don't think it should
ever be th
Pete French wrote:
> I appear to have a machine which will not run RELENG_6_2, though it runs
> the released code quite happily. Is there a CVS tag I can use to revert the
> sources back to the way they were on RELEASE? I want to be able to
> verify that this is and track down what changed! I don't
On Mon, 19 Mar 2007 11:31:54 +
Pete French <[EMAIL PROTECTED]> wrote:
> I appear to have a machine which will not run RELENG_6_2, though it runs
> the released code quite happily. Is there a CVS tag I can use to revert the
> sources back to the way they were on RELEASE? I want to be able to
>
Martin Blapp <[EMAIL PROTECTED]> writes:
> Hi,
>
> I just fixed those issues with the port.
>
> Thanks for reporting !
So we can safely use libpthread.so again? No need to use libmap.conf?
--
One cannot sell the earth upon which the people walk
Ta
Krassimir Slavchev wrote:
After detecting HDD I have "Fatal trap 12: page fault ..." and "current
process 0 (swapper)".
"Process 0", which is accidentally "swapper" is a special thing - it's
unlikely your fault is swap-related.
___
freebsd-stable@
> I think you will want RELENG_6_2_0_RELEASE.
thanks (and to the others who responded)
> What happens with RELENG_6_2, IIRC there was only very limited changes
> to kernel which should only affect IPv6...
Indeed! Part of the reason I want to do the revert is to make absolutely
sure that it runs
Tom Samplonius wrote:
The one thing about IBM blades, is that the various controllers for all kinds
of IO devices may exist, but are simply not wired. FreeBSD is quite picky (or
stupid) about device probing. If it finds a device, it basically demands that
it works. It would be great if
Pete French wrote:
>> I think you will want RELENG_6_2_0_RELEASE.
>
> thanks (and to the others who responded)
>
>> What happens with RELENG_6_2, IIRC there was only very limited changes
>> to kernel which should only affect IPv6...
>
> Indeed! Part of the reason I want to do the revert is to ma
I think this is a very good idea, I've been caught at least once
not being able to recreate a working kernel due to the loss of
the original config file.
Steve
- Original Message -
From: "LI Xin" <[EMAIL PROTECTED]>
I always use options INCLUDE_CONFIG_FILE for my kernel :-) Maybe
> I always use options INCLUDE_CONFIG_FILE for my kernel :-) Maybe we
> should add it to DEFAULTS some day...
never seen it before - if it does what it sounds like it does then it
would be very useful!
-pete.
___
freebsd-stable@freebsd.org mailing list
On Mon, Mar 19, 2007 at 01:33:44PM -, Steven Hartland wrote:
> I think this is a very good idea, I've been caught at least once
> not being able to recreate a working kernel due to the loss of
> the original config file.
>
>Steve
>
> - Original Message -
> From: "LI Xin" <[EMAIL
Wojciech A. Koszek wrote:
> On Mon, Mar 19, 2007 at 01:33:44PM -, Steven Hartland wrote:
>> I think this is a very good idea, I've been caught at least once
>> not being able to recreate a working kernel due to the loss of
>> the original config file.
>>
>>Steve
>>
>> - Original Message
- Original Message -
From: "Wojciech A. Koszek" <[EMAIL PROTECTED]>
I did some work in this area, as several system administrators I've met
also seem to have problem with kernel configuration recovery. In my case
I came with a method of obtaining a configuration of a running kernel
via sy
On Mon, Mar 19, 2007 at 02:32:48PM -, Steven Hartland wrote:
> - Original Message -
> From: "Wojciech A. Koszek" <[EMAIL PROTECTED]>
> >I did some work in this area, as several system administrators I've met
> >also seem to have problem with kernel configuration recovery. In my case
>
- Original Message -
From: "Wojciech A. Koszek" <[EMAIL PROTECTED]>
Yes, it does. You get full configuration file from sysctl(8) or from
config -k , and config(8) is modified in a way, that lets you to
use this file without additional trimming.
Sounds like a very worth while addition,
Hello.
I have a problem with FreeBSD 6.2-RELEASE in VmWare Server on Windows
2003 host.
Time is a hour slow for a day.
I have hint.apic.0.disabled=1 in loader.conf
I've tried all possible values in kern.timecounter.hardware.
Nothing helps.
I've found it's not only my problem:
http://www.vmware.
Ivan Voras wrote:
Krassimir Slavchev wrote:
After detecting HDD I have "Fatal trap 12: page fault ..." and
"current process 0 (swapper)".
"Process 0", which is accidentally "swapper" is a special thing - it's
unlikely your fault is swap-related.
Yes, it isn't. The fault is in the ata_raid_
If memory serves me right, Pete French wrote:
> I appear to have a machine which will not run RELENG_6_2, though it runs
> the released code quite happily. Is there a CVS tag I can use to revert the
> sources back to the way they were on RELEASE? I want to be able to
> verify that this is and track
Sergey Matveychuk wrote:
> Hello.
>
> I have a problem with FreeBSD 6.2-RELEASE in VmWare Server on Windows
> 2003 host.
>
> Time is a hour slow for a day.
>
> I have hint.apic.0.disabled=1 in loader.conf
> I've tried all possible values in kern.timecounter.hardware.
> Nothing helps.
>
> I've f
On Mar 19, 2007, at 9:24 AM, LI Xin wrote:
I always use options INCLUDE_CONFIG_FILE for my kernel :-) Maybe we
should add it to DEFAULTS some day...
ew yucky
What I do is keep my kernel configs in subversion. I have a "common"
component which applies to all systems under my control,
> I have made bge(4) patch for -STABLE (sorry, not suitable for
> RELENG_6_2):
What dates stable is this relative to ? I am trying to apply your
patch to a cvsup of stable pulled on the day/time you sent your email,
but parts of it are failing for me unfortunately. I would like to test this
as I
Sergey Matveychuk <[EMAIL PROTECTED]> wrote on 19 Mar 2007 17:15:
> I have a problem with FreeBSD 6.2-RELEASE in VmWare Server on Windows
> 2003 host.
Unfortunately I can't help you, but I observed the same problem on a GSX 3.2.1
on Linux.
> Time is a hour slow for a day.
>
> I have hint.apic.0
Va'clav Haisman wrote:
Sergey Matveychuk wrote:
Hello.
I have a problem with FreeBSD 6.2-RELEASE in VmWare Server on Windows
2003 host.
Time is a hour slow for a day.
I have hint.apic.0.disabled=1 in loader.conf
I've tried all possible values in kern.timecounter.hardware.
Nothing helps.
I've
Einstein Oliveira wrote:
Va'clav Haisman wrote:
Sergey Matveychuk wrote:
Hello.
I have a problem with FreeBSD 6.2-RELEASE in VmWare Server on Windows
2003 host.
Time is a hour slow for a day.
I have hint.apic.0.disabled=1 in loader.conf
I've tried all possible values in kern.timecounter.hard
On Mon, Mar 19, 2007 at 10:23:53PM +0800, LI Xin wrote:
> Wojciech A. Koszek wrote:
[..]
> >> I always use options INCLUDE_CONFIG_FILE for my kernel :-) Maybe we
> >> should add it to DEFAULTS some day...
> >
> > I did some work in this area, as several system administrators I've met
> > also s
Guy Helmer wrote:
(reposting since this involves 6-stable)
I'm investigating a problem where a pretty much stock 6.2 SMP kernel
randomly hangs on multiple Supermicro X7DBR-i+ and X7DBR-8+ systems.
The system syncs the filesystems and prints "Uptime: ...", then hangs.
So far, I've narrowed it
At 12:28 PM 3/19/2007, Pete French wrote:
> I have made bge(4) patch for -STABLE (sorry, not suitable for
> RELENG_6_2):
What dates stable is this relative to ? I am trying to apply your
patch to a cvsup of stable pulled on the day/time you sent your email,
but parts of it are failing for me unf
I found that the solution here:
"http://taosecurity.blogspot.com/2006/07/slow-time-with-freebsd-61-guest-on.html";
(Add the following to /boot/loader.conf and reboot: kern.hz="100")
Worked well for me. I still have minor drift (about 5 minutes after a
week) but it can easily be handled by nt
> Mine applied cleanly to sources from last Friday.
O.K., that works (now I have the correct date in my supfile). Will
give it a shot...
-pete.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsub
> regression that was introduced late in the 6.2 release cycle. I'm
> personally pretty skeptical that this could cause a problem, although
> I'm admittedly a little biased, plus there weren't a lot of details in
> your email as to what the problem is.
Well, you are right - it wont run a stock -R
Mark Dotson <[EMAIL PROTECTED]> wrote on 19 Mar 2007 9:50:
> (Add the following to /boot/loader.conf and reboot: kern.hz="100")
>
> Worked well for me. I still have minor drift (about 5 minutes after a
> week) but it can easily be handled by ntp at that point.
>
> I'd give that a try. :-)
As
Frank Behrens wrote:
> Mark Dotson <[EMAIL PROTECTED]> wrote on 19 Mar 2007 9:50:
>> (Add the following to /boot/loader.conf and reboot: kern.hz="100")
>>
>> Worked well for me. I still have minor drift (about 5 minutes after a
>> week) but it can easily be handled by ntp at that point.
>>
>> I'
Recently the bugbusting team has been seeing a few cases where PRs are
being submitted without a clear understanding of how best to do so.
Although there is a document that references this*, please let me reiterate
a few points:
- Please only send one PR for a particular problem. The mail queue
This is the most often asked question with virtualisation of PC
hardware. The question was finally answered, but here's the reasoning:
* The operating system expects the clock/timer hardware to be consistent
* The timer hardware in a VM isn't that consistent as the
virtualisation environment is a
On Tue, 13-Mar-2007 at 00:45:24 +0800, Rong-en Fan wrote:
> On 3/12/07, Stefan Lambrev <[EMAIL PROTECTED]> wrote:
> >Rong-en Fan wrote:
> >> Hi folks,
> >>
> >> ncurses in 6.x is pretty old. We have update-to-date ncurses in 7.x
> >> with wide character support now. The patch at
> >>
> >> http://pe
35 matches
Mail list logo
