On Sun, Oct 21, 2007 at 09:19:35AM +0200, Peter Schuller wrote:
Hello,
Since then I have now tried two distinct TX4 cards (but only in one
PCI slot). Both suffer from the same problem. Amazingly a SiI 3114
*does* seem to work in the same PCI slot - no corruption, and no DMA
timeouts and
On Saturday 20 October 2007, Yi Wang wrote:
Hi,
My box is running 7.0-PREREALEASE.
When I run more than two building tasks, X11 became extremely slow.
The mouse pointer can also hardly move.
Running more than two building tasks under 6-stable does not
introduce the issues.
Does any one
Thanks to all.
But I have the ULE scheduler enabled in the kernel.
% cat /usr/src/sys/i386/conf/MYKERNEL | grep -v ^# | grep -v ^$
cpu I686_CPU
ident MYKERNEL
options SCHED_ULE # 4BSD scheduler
options PREEMPTION # Enable kernel
Yi Wang wrote:
Hi,
My box is running 7.0-PREREALEASE.
When I run more than two building tasks, X11 became extremely slow.
The mouse pointer can also hardly move.
Running more than two building tasks under 6-stable does not introduce
the issues.
Does any one know how to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
If you are running Radius see /etc/services. Ports used by Radius are
1812/1813.
Squirrel wrote:
For some reason, my port 1645 is closed on FreeBSD 6.2. I have all the
firewall disabled, but it's not allowing me access the port 1645. How do
On Sun, 21 Oct 2007, Squirrel wrote:
For some reason, my port 1645 is closed on FreeBSD 6.2. I have all
the firewall disabled, but it's not allowing me access the port 1645.
How do you manually open this port? I can't seem to find at google.
I suspect this belongs over on
Try adding options FULL_PREEMPTION to your kernel.
What is the difference between this and PREEMPTION + IPI_PREEMPTION?
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any
- Squirrel [EMAIL PROTECTED] wrote:
For some reason, my port 1645 is closed on FreeBSD 6.2. I have all
the firewall disabled, but it's not allowing me access the port 1645.
How do you manually open this port? I can't seem to find at google.
You also need to have something listening
IPI_PREEMPTION allows the scheduler running on CPU A to preempt a thread
on CPU B. This should reduce latency in some circumstances.
# PREEMPTION allows the threads that are in the kernel to be preempted
# by higher priority threads. It helps with interactivity and
# allows
Squirrel wrote:
For some reason, my port 1645 is closed on FreeBSD 6.2. I have all the
firewall disabled, but it's not allowing me access the port 1645. How do you
manually open this port? I can't seem to find at google.
You need to configure an application to listen on the port.
Squirrel wrote:
For some reason, my port 1645 is closed on FreeBSD 6.2. I have all the
firewall disabled, but it's not allowing me access the port 1645. How do you
manually open this port? I can't seem to find at google.
FreeBSD does nothing special here. If you are sure you have an
Hi Squirrel (odd name that is...),
On Sun, 21 Oct 2007 14:54:53 -0500, Squirrel [EMAIL PROTECTED] wrote:
For some reason, my port 1645 is closed on FreeBSD 6.2. I have all the
firewall disabled, but it's not allowing me access the port 1645. How do
you manually open this port? I can't seem
yes, already had tried.
renice -10
On 10/22/07, Pollywog [EMAIL PROTECTED] wrote:
Yi Wang wrote:
Hi,
My box is running 7.0-PREREALEASE.
When I run more than two building tasks, X11 became extremely slow.
The mouse pointer can also hardly move.
Running more than two
On 18/10/2007, Roland Smith [EMAIL PROTECTED] wrote:
The user in question probably needs read/write access to the /dev/smbX
device in question.
There is no such device:
# ls /dev/smb*
ls: No match.
(with and without a smbfs mount point mounted by root)
Can anyone take a look on PR kern/104406 ? I got repeatable hang
situation,
but I can't obtain a kernel dump to get result of all show commands from
here:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html
After my break to debugger using
The card seems to be doing naughty things to the PCI bus under load;
your dmesg ought to be full of PCI timeouts.
No timeouts or errors in dmesg. I expected some, because that is what
I got on another machine (earlier 7-CURRENT) where I was unable to use
SiL/Promise because of such issues. In
Hi,
Ivan Voras wrote:
On 18/10/2007, Roland Smith [EMAIL PROTECTED] wrote:
The user in question probably needs read/write access to the /dev/smbX
device in question.
There is no such device:
# ls /dev/smb*
ls: No match.
Err, /dev/smb stands for System Management Bus and have
On Mon, Oct 22, 2007 at 02:04:15PM +0200, Ivan Voras wrote:
On 18/10/2007, Roland Smith [EMAIL PROTECTED] wrote:
The user in question probably needs read/write access to the /dev/smbX
device in question.
There is no such device:
# ls /dev/smb*
My bad. That's a device for the system
Hello,
During buildworld on RELENG_7 csup'd as of 10/22, it dies in
sys/boot/i386/boot2 with:
=== sys/boot/i386/boot2 (all)
-533 bytes available
*** Error code 1
Stop in /usr/src/sys/boot/i386/boot2.
*** Error code 1
I took a look at the cc command line:
cc -Os -fno-guess-branch-probability
On 22/10/2007, Stefan Lambrev [EMAIL PROTECTED] wrote:
Err, /dev/smb stands for System Management Bus and have nothing to do
with smbfs :)
What I found is the claim that only root is allowed to set up the
kernel's iconv table
And now I'm thinking, may be, if the root setup this table, the
20 matches
Mail list logo
