x27;s lost a segment
for some reason and is trying to trigger fast recovery early.
Stephen Hurd schrieb am 18.02.2010 17:18 (localtime):
...
one retransmit per five packets). Is this what you're seeing? If you
have a capture you could share covering a few seconds, I could take a
look and
Stephen Hurd wrote:
Some experimental results:
When rsyncing with windows, and FreeBSD is receiver, I see the same
ACK ever two segemnts, but speed is at 72MB/s.
When FreeBSD is sender and Windows is receiver, it looks more I
expected. There are about 20 data segments before a ACK is returned
Harald Schmalzbauer wrote:
Some experimental results:
When rsyncing with windows, and FreeBSD is receiver, I see the same
ACK ever two segemnts, but speed is at 72MB/s.
When FreeBSD is sender and Windows is receiver, it looks more I
expected. There are about 20 data segments before a ACK is ret
Harald Schmalzbauer wrote:
Some experimental results:
When rsyncing with windows, and FreeBSD is receiver, I see the same
ACK ever two segemnts, but speed is at 72MB/s.
When FreeBSD is sender and Windows is receiver, it looks more I
expected. There are about 20 data segments before a ACK is ret
Ivan Voras wrote:
An interesting problem. I presume that in either case (gpart or
GEOM_BSD/MBR) the output of "gstripe status" is the same? Only the
interpretation of the partition tables is problematic?
Yes, but the output of gstripe list is different in the mode lines...
for GEOM_PART, the
I've upgraded from 7.2-RELEASE_p2 to 8.0-BETA4 and using GEOM_PART_*
with my sliced gstripe array causes the /dev/stripe/raid0a to disappear
and the reset of the /dev/stripe/raid0[a-z] file systems to be unmountable.
My gvinum array is still working fine and, after chasing the ad* slices,
they
Kris Kennaway wrote:
I think something is not quite right in your analysis, because perl
does not depend on any external perl modules (it cannot, by definition).
I ran into something like this when I was switching from a threaded perl
to an unthreaded perl. It wasn't possible to just use a po
Dick Hoogendijk wrote:
On Fri, 29 Feb 2008 15:39:11 -0800
Stephen Hurd <[EMAIL PROTECTED]> wrote:
As a workaround, adding the line:
hw.ata.ata_dma="0"
To /boot/loader.conf will disable DMA and prevent the hangs that are
caused by the DMA timeouts.
Yeah, but having
> > As a workaround, adding the line:
> > hw.ata.ata_dma="0"
> >
> > To /boot/loader.conf will disable DMA and prevent the hangs that are caused
> > by the DMA timeouts.
>
> Does that workaround work when the disks are sata?
Don't know. I personally would assume so, but I wouldn't be surprised
> last night. It's a MiniITX board, model EN1200. My system can't remain
> up for more than 10minutes before something locks it up and frequently
> the screen will output error messages relating to DMA.
As a workaround, adding the line:
hw.ata.ata_dma="0"
To /boot/loader.conf will disable DMA and
Scott Long wrote:
I'd like to attack these driver problems. What I need is to spend a
couple of days with an affected system that can reliably reproduce the
problem, instrumenting and testing the driver. I have a number of
theories about what might be going wrong, but nothing that I'm
definitel
Scott Long wrote:
I'm betting that it's a driver problem and not
a hardware problem, though you should probably think about migrating
your data off to a new drive sometime soon.
Yeah, ordered a replacement drive today.
I'd like to attack these driver problems. What I need is to spend a
coupl
Jeremy Chadwick wrote:
And after the reboot, the READ_DMA timeouts were back.
You're not the only one seeing this behaviour. There are too many posts
in the past reporting similar. Here's the breakdown:
* Some have switched to alternate operating systems (usually Linux) for
a short wh
My system has been working reliably with 6.3 for quite some time... when
I rebooted into single user mode to do the installworld with the
7.0-RELEASE kernel, the install died about halfway through with READ_DMA
TIMEOUT errors. Since I had a mixed system at that point, I set
hw.ata.ata_dma="0"
1) How do people cope with custom termcap entries?
One workaround is to not modify /etc/termcap at all. Instead just store
them in a file somewhere and (depending on your shell) do
export TERMCAP=/my/custom/termcap
Or even
export TERMCAP=custom:my custom entry
See the ENVIRONMENT s
--- Begin Message ---
I've now shot myself in the foot at least three times in as many years with
custom termcap entries... here's the deal:
1) I modify /etc/termcap and customize a termcap entry for some valid reason
(I need 132x42 or whatever for my Link MC/5)
2) I update /etc/gettytab and
Max Laier wrote:
Yeah, I've noticed that too now that you mention it. When it happened
to me, I switched to using atapicam and cdrecord with the -swab parameter.
Also, you may want to look at audio/mp3burn (still need to pass -swab
though)
I would recommend that you file a PR on this one.
Michael A. Koerber wrote:
All,
Once upon a time, I think with 5.x or perhaps earlier, the command
(ATAPI drive)
burncd -ef /dev/acd0 audio *.cdr fixate
would produce an audio CD for me. However, under 6.0 and recently 6.1
this same command produces an CD filled with white noise only. T
Howard Leadmon wrote:
Would this just be lockd, or should I disable both lockd and statd? I notice
in the rc.conf it claims they are both supposed to be enabled, so not sure
what issues I run into if I disable them, if any.
No need to disable rpc.statd though I don't know if any other program
Howard Leadmon wrote:
Hello All,
I have been running FBSD a long while, and actually running since the 5.x
releases on the server I am having troubles with. I basically have a small
network and just use NIS/NFS to link my various FBSD and Solaris machines
together.
This has all been run
Security updates will be maintained for quite a while. However, it
takes manpower to test each proposed security change, so it's very hard
to justify doing them 'indefinitely'. The stated policy from the
security team is 2 years. So they will probably support 5.5 into
2008, but I wanted to be
MS-KILA wrote:
still present trying to install 6.0 on a 600Mhz celery, 384 ram, 8g
hdd; ftp install. will attempt the explicit ip idea.
does every first attempt at ftp choke like this?
wayne
___
freebsd-stable@freebsd.org mailing list
http://lists.f
Joseph Koshy wrote:
A custom kernel compiled with options PERFMON and cputype=athlon when ran on
an athlon causes ATA to not probe devices on FreeBSD 6.0-RELEASE. dmesg
seems normal except the ata probe is never done, so the only boot devices
available is the floppy.
AFAIR, "PERFMON" onl
A custom kernel compiled with options PERFMON and cputype=athlon when ran on
an athlon causes ATA to not probe devices on FreeBSD 6.0-RELEASE. dmesg
seems normal except the ata probe is never done, so the only boot devices
available is the floppy.
Just something I noticed in passing, not open
Daniel O'Connor wrote:
FreeBSD doesn't have rtc.ko.. Mine doesn't anyway :)
I'm not sure how mplayer in FreeBSD stamps frames either.
It's not stock, but /dev/rtc (via rtc.ko) can be had via emulators/rtc
if rtc.ko exists, it's a dependency, to force it to be built you can
frob the WITH_RT
I always build my production servers with CPUTYPE=i686 so they can be
transplanted to any machine with a PPro or better processor (or even
qemu if necessary).
Thanks, Craig. I'm glad to hear that I'm not alone in pursuing this
method.
Do you know of any particular disadvantages of continuin
I installed from two CDs, and got a working KDE system. Now, I want to do
Firefox from ports with my own make.conf for P4 optimisation. Good! So, I
sync with the sources using cvsup (just like emerge --sync) change to the
Firefox ports directory, type "make" and enter dependency hell like has
Matt Smith wrote:
In this case I think the hard disk filled up during the install as I got
later: "couldn't create /usr/compat - no space left on device."
Right... that's essentially the same error. What apears to happen when
the install is aborted/restarted is that instead of installing to
Matt Smith wrote:
Trying to put FBSD 6.0-Stable on a box and the error in the subject line
(/create/symlink failed: no inodes free) comes up right after the
filesystems are made and the transfer over FTP starts. What causes this
error?
I've found this tends to happen if the install is abort
29 matches
Mail list logo
