-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Seems that the new drm schema requires an interrupt to attach.
"dmesg" returns:
pcib0: port 0xcf8-0xcff on acpi0
pci0: on pcib0
agp0: on hostb0
pcib1: at device 1.0 on pci0
pci1: on pcib1
vgapci0: port 0x9000-0x90ff mem
0xd100-0xd1f
I'm getting a really odd condition on one of my servers (and I suspect its
happening on one of my other servers as well) ... after a period of time
(<3 days), the server hangs solid ...
Running vmstat in an xterm, the one thing I'm noticing is that when it
hangs, my avm == 12455M and fre ==
Yes that is exactly the point. RNDC is supposed to run on 953 and the name
service itself is on 53. Think about it, if tcp/53 is used for real DNS
(jumbo RR) traffic, how can rndc be listening for commands on the same
channel?
On 2009-03-17 06:10:44PM -0600, Squirrel wrote:
> I realized that defau
I realized that default for RNDC was 953, and forced it to 53, but was still
getting the same error.
As you recommended, I used the '-g' and noticed only unusual thing was:
/etc/namedb/named.conf:23: couldn't add command channel 127.0.0.1#53:
address in use
So I took out the port 53 out of
On Sun, 15 Mar 2009 19:49:12 +0100, Robert Noland
wrote:
I went ahead and merged the Radeon R6/7xx code to -STABLE a while ago.
The current xorg drivers will not enable it by default on R600+ chips.
You will need to be using xf86-video-ati-6.12.0,
xf86-video-radeonhd-devel or possibly even b
On Tue, 17 Mar 2009, Robert Noland wrote:
On Tue, 2009-03-17 at 12:20 -0500, Greg Rivers wrote:
On Sat, 10 Jan 2009, Robert Noland wrote:
I just merged drm (Direct Rendering) from HEAD.
- Support for latest Intel chips
- Support and fixes for many AMD/ATI chips r500 and below
In message , Squirrel writes:
> My BIND9.6.0 on FreeBSD 6.2 works fine when I manually start with:
>
>r...@ns2# named -4 -S 1024 -c /etc/namedb/named.conf
>
> But it won't start on boot and no error messages or log. And it won't start
> using rndc, it cause error message. Why does the err
Will, just for heck of it, I've changed the default ports to 953 on both
named.conf and rndc.conf, but still same error.
-Original message-
From: Squirrel squir...@mail.isot.com
Date: Tue, 17 Mar 2009 22:41:26 -0600
To: freebsd-stable freebsd-stable@freebsd.org
Subject: rndc: connect fai
My BIND9.6.0 on FreeBSD 6.2 works fine when I manually start with:
r...@ns2# named -4 -S 1024 -c /etc/namedb/named.conf
But it won't start on boot and no error messages or log. And it won't start
using rndc, it cause error message. Why does the error shows port 953 when I
specified for por
Hi.
FreeBSD 7-STABLE.
Subj message appears when I try to kldload cbb.ko and kernel
cannot find exca due to its non-existence.
The pccbb(4) manpage doesn't mention exca.
make install exca helps with kldload, now:
cbb0: at device 1.0 on pci1
cbb0: [ITHREAD]
Would it be correct to add a new entry
Nice!!!
Thank you.
---
PCShare.Com
-Original message-
From: David Kelly dke...@hiwaay.net
Date: Tue, 17 Mar 2009 20:32:10 -0600
To: Squirrel squir...@mail.isot.com
Subject: Re: general: warning: max open files (3636) is smaller than maxsockets
(4096)
> On Tue, Mar 1
On Tue, 2009-03-17 at 12:20 -0500, Greg Rivers wrote:
> On Sat, 10 Jan 2009, Robert Noland wrote:
>
> > I just merged drm (Direct Rendering) from HEAD.
> >
> >- Support for latest Intel chips
> >- Support and fixes for many AMD/ATI chips r500 and below
> >- Support AMD/ATI
On Tue, Mar 17, 2009 at 10:19:11AM -0400, Ken Smith wrote:
>
> We're starting the release process for FreeBSD 7.2-RELEASE. The major
> highlights of the schedule are:
Is there a chance the latest ZFS bugfixes from CURRENT will make it
into 7.2-RELEASE?
Regards,
Holger
On Tue, Mar 17, 2009 at 12:31:43PM -0600, Squirrel wrote:
> This happend since I've upgraded bind 9.21 to 9.6.0. I've increased
> the max open files to 4096:
>
>sysctl -w kern.maxfiles=4096
>
> which shows it resized from 4040->4096
>
> But I guess it's different for bind? I've googled and
This happend since I've upgraded bind 9.21 to 9.6.0. I've increased the max
open files to 4096:
sysctl -w kern.maxfiles=4096
which shows it resized from 4040->4096
But I guess it's different for bind? I've googled and found several references
to this warning message, but everyone states i
On Mon, 16 Mar 2009 17:23:09 -0600
Dan Allen wrote:
> It turns out that one must have a debug kernel around. I use STABLE
> as a production system. There is no "kernel.debug" on my system. I
> guess I therefore cannot provide a stack trace.
Have you disbled building of the kernel.debug th
On Sat, 10 Jan 2009, Robert Noland wrote:
I just merged drm (Direct Rendering) from HEAD.
- Support for latest Intel chips
- Support and fixes for many AMD/ATI chips r500 and below
- Support AMD/ATI IGP based chips (rs690/rs485)
- Lots of code cleanups
- Lots
Nicolais wrote:
Also - this was extracted from kenv:
smbios.system.maker="MICRO-STAR INTERANTIONAL CO.,LTD"
smbios.system.product="MS-7368"
as I supposed in previous message your MB is MicroStar product. So I
insist that you read thread [1] in freebsd-stable named 'Interrupt
storm' started b
Nicolai wrote:
Hi all,
I have had this problem since day 1 on my new server.
It has run since November 15th 2008, and serve approx. 10 GB worth of web
traffic per month for the main site and then some 40 domains with mail and
small web pages. (hence - it's NOT that busy yet)
I started wi
Also - this was extracted from kenv:
LINES="24"
acpi_load="YES"
bootfile="kernel"
comconsole_speed="9600"
console="vidconsole"
currdev="disk0s1a:"
hint.acpi.0.oem="ACPIAM"
hint.acpi.0.revision="1"
hint.acpi.0.rsdp="0xf98a0"
hint.acpi.0.rsdt="0x7dfd"
hint.atkbd.0.at="atkbdc"
hint.atkbd.0.irq="
We're starting the release process for FreeBSD 7.2-RELEASE. The major
highlights of the schedule are:
Code Freeze:March 23rd
BETA1 March 30th
Branch April 10th
RC1 April 13th
RC2
Hi all,
I have had this problem since day 1 on my new server.
It has run since November 15th 2008, and serve approx. 10 GB worth of web
traffic per month for the main site and then some 40 domains with mail and
small web pages. (hence - it's NOT that busy yet)
I started with 7.1-RELEASE-pX
On Mon, Mar 16, 2009 at 5:47 PM, Dan Allen wrote:
>
> On 16 Mar 2009, at 1:01 PM, Alan Cox wrote:
>
>> For now, can you just provide the stack trace?
>
> As I mentioned, I am unable to do so - I have no kernel.debug.
>
> However, I am trying to reproduce the bug again. (It takes a while.)
> Alth
while rebooting:
(kgdb) bt
#0 doadump () at pcpu.h:196
#1 0x80514298 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
#2 0x80514575 in panic (fmt=Variable "fmt" is not available.
) at /usr/src/sys/kern/kern_shutdown.c:574
#3 0x806a74d4 in trap_fatal (frame=0xbf5b9a24, eva=12) at
Dear all:
With 7.2 approaching, I wanted to review the set of known network bug reports
(especially panics, hangs, lock order reversals) relating to TCP, UDP,
sockets, and routing in 7-STABLE.
If you are aware of problems along these that you can confirm definitely occur
with 7-STABLE check
I switched to xfce myself and did not reinstall consolekit… don't know
how armfull it could be though…
Le 17 mars 09 à 10:31, Arrigo Marchiori a écrit :
Hello,
On Fri, Mar 13, 2009 at 01:24:57PM +0100, Arrigo Marchiori wrote:
On Mon, Mar 09, 2009 at 12:15:15PM +0100, spara wrote:
[...]
A
Hello,
On Fri, Mar 13, 2009 at 01:24:57PM +0100, Arrigo Marchiori wrote:
> On Mon, Mar 09, 2009 at 12:15:15PM +0100, spara wrote:
[...]
> > Any other fix ?
>
> It seems to me that no package has been depending on consolekit, since
> a couple of days. At least, portupgrade is not showing any more
27 matches
Mail list logo
