On Sat, Mar 07, 2009 at 09:22:02PM -0800, David Ehrmann wrote:
It's been reported before, but I haven't seen anything new. vge devices
Because I don't have access to the hardware it looks like hard to
fix.
won't autonegotiate to gigabit speeds, and if I set the media to
1000baseTX,
Hello.
I thought rc used to start nfsiod if you set nfs_cilent_enable
back years ago.
Now, on my 7.1-RELEASE machine, it sets up a couple of sysctls
in /etc/rc.d/nfsclient script but not nfsiod.
Is nfsiod obsolete by now?
It is still on the system; does it still improve nfs performance?
Thanks,
Hi,
last week I made a rebuild on my system (7.1 RELENG_7 amd64).
After this i could not reach my system from outside the LAN. It was
extremely slow. I suspected Modem, Firewall and so on, because inside my
LAN I could work. But then with tshark I found, that also there where
many
Hi,
last week I made a rebuild on my system (7.1 RELENG_7 amd64).
After this i could not reach my system from outside the LAN. It was
extremely slow. I suspected Modem, Firewall and so on, because inside my
LAN I could work. But then with tshark I found, that also there where
many
On Mon, 2 Mar 2009, John Baldwin wrote:
On Wednesday 28 January 2009 10:13:46 pm David Adam wrote:
I upgraded my 7.0 system to 7.1-RELEASE with freebsd-update only to find
that it no longer boots correctly, instead crashing with a BTX backtrace.
If I break to the loader prompt and use 'ls
On Sun, Mar 08, 2009 at 10:07:59AM +0100, Beat Siegenthaler wrote:
Hi,
last week I made a rebuild on my system (7.1 RELENG_7 amd64).
After this i could not reach my system from outside the LAN. It was
extremely slow. I suspected Modem, Firewall and so on, because inside my
LAN I could
Hi,
On 26 Feb 2009, at 2:28, Charles Sprickman wrote:
On Wed, 25 Feb 2009, Robert Watson wrote:
Just a minor heads up: I've merged both Kip Macy's lock order fixes
to the kernel routing code, and the route locking and reference
counting fixes from kern/130652 to stable/7. These fixes
On Sun, 8 Mar 2009, Ruben van Staveren wrote:
Just a minor heads up: I've merged both Kip Macy's lock order fixes to the
kernel routing code, and the route locking and reference counting fixes
from kern/130652 to stable/7. These fixes should correct a number of
reported network-related
On Sun, 8 Mar 2009, Yoshihiro Ota wrote:
I thought rc used to start nfsiod if you set nfs_cilent_enable back years
ago. Now, on my 7.1-RELEASE machine, it sets up a couple of sysctls in
/etc/rc.d/nfsclient script but not nfsiod.
Is nfsiod obsolete by now?
It is still on the system; does it
Hi Robert,
On 8 Mar 2009, at 12:24, Robert Watson wrote:
On Sun, 8 Mar 2009, Ruben van Staveren wrote:
Just a minor heads up: I've merged both Kip Macy's lock order
fixes to the kernel routing code, and the route locking and
reference counting fixes from kern/130652 to stable/7. These
Pyun YongHyeon wrote:
I touched fxp(4) to add more hardware assistance so it could cause
problems on your box. Please show me dmesg output and
ifconfig fxp0
output.
If you doubt checksum offloading or TSO issues, try
ifconfig fxp0 -tso -txcsum -rxcsum.
As I remember this Dual card is
On Sunday 08 March 2009 02:36:42 Pyun YongHyeon wrote:
On Sat, Mar 07, 2009 at 05:17:57PM +, ian j hart wrote:
On Tuesday 20 January 2009 02:45:19 Pyun YongHyeon wrote:
On Mon, Jan 19, 2009 at 06:33:46PM -0500, Jung-uk Kim wrote:
On Monday 19 January 2009 04:33 pm, Jung-uk Kim
Luigi Rizzo wrote:
Hi all,
this is an update on the work that Fabio Checconi and I are doing
on disk scheduling, which was first announced here a couple of
months ago:
http://lists.freebsd.org/pipermail/freebsd-stable/2009-January/047597.html
Since the previous version, we have done
On Sun, Mar 08, 2009 at 07:38:30PM +0100, Ivan Voras wrote:
Luigi Rizzo wrote:
...
Apart from that (which needs to be fixed by adding a field to the
struct bio), we believe the code to be quite stable now, so future
...
Hi,
Do you have some documentation about the long-term plans? You
for Mac OSX does not establish data I/O
because of unexpected data segment length.
I will plan to fix it in the near future.
o FreeBSD initiator can't connect to the target because of StatSN error.
I don't know a reason.
Here is release 20090308:
http://shell.peach.ne.jp/aoyama/archives/342
On Sun, Mar 08, 2009 at 06:04:35PM +0100, Beat Siegenthaler wrote:
Pyun YongHyeon wrote:
I touched fxp(4) to add more hardware assistance so it could cause
problems on your box. Please show me dmesg output and
ifconfig fxp0
output.
If you doubt checksum offloading or TSO issues,
On Sun, Mar 08, 2009 at 05:10:58PM -0700, David Ehrmann wrote:
Pyun YongHyeon wrote:
On Sat, Mar 07, 2009 at 09:22:02PM -0800, David Ehrmann wrote:
It's been reported before, but I haven't seen anything new. vge devices
Because I don't have access to the hardware it looks like
Hi,
Sorry for the late reply.
On Mar 3, 2009, at 7:07 AM, Pyun YongHyeon wrote:
Ok, when you plug UTP cable can you see re0: link state changed to
UP in dmesg output? Or if you unplug the cable, you should see
re0: link state changed to DOWN(With tail -f /var/log/message,
you can easily check
On Sun, Mar 08, 2009 at 09:52:19PM -0400, Steve Wills wrote:
Hi,
Sorry for the late reply.
On Mar 3, 2009, at 7:07 AM, Pyun YongHyeon wrote:
Ok, when you plug UTP cable can you see re0: link state changed to
UP in dmesg output? Or if you unplug the cable, you should see
re0: link state
Have you tried re(4) in HEAD?
I had one report that re(4) in HEAD still does not fix the issue so
I posted a possible workaround for that. Unfortunately he didn't
report back so I don't know whether it was right workaround or not.
If re(4) in HEAD does not fix the issue, would you try
20 matches
Mail list logo
