* Brett Glass (br...@lariat.net) wrote:
Thank you! Did not know to look for this in the source tree; now I know.
You can get an Atom feed to monitor it for you here:
http://freshbsd.org/search?project=freebsdq=file.name%3Anewvers.shbranch=RELENG_9
/plug
--
Thomas 'Freaky' Hurst
* Jeremy Chadwick (free...@jdc.parodius.com) wrote:
It's been mentioned in the past that for simple SATA expansion cards,
a good/affordable choice at this point are cards using the Silicon Image
3124/3132/3531 chips (driven by the siis(4) driver). Avoid the 3112.
The reason I say that
* Jack Vogel (jfvo...@gmail.com) wrote:
Its using MSI? Given that its PCI-X I have no idea how robust MSI is,
how bout you compile it with that disabled, use legacy IRQ and see
if that makes any diff.
I'm seeing similar issues with a quad port 82546EB card, and they're not
using MSI as far as
* Steven Hartland (kill...@multiplay.co.uk) wrote:
If that's a supermicro then em3 is usually the IPMI shared card so perhaps
that's the cause?
No, it's a Tyan K8WE:
http://www.tyan.com/archive/products/html/thunderk8we.html
With a quad port Intel NIC in one of the 133MHz PCI-X slots.
* Robert Watson (rwat...@freebsd.org) wrote:
It would probably be worth skimming svn logs for stable/7 to see what
other testing focuses would be particularly useful.
In case it's of use, I have full searchable SVN history here:
http://beta.freshbsd.org/?q=branch:RELENG_7
--
Thomas
* Patrick Lamaizière ([EMAIL PROTECTED]) wrote:
Ruben van Staveren [EMAIL PROTECTED] a écrit :
Though experimental, I'm greatly enjoying
http://www.secnetix.de/olli/FreeBSD/svnews/?p=/stable/7
Nice. There is also http://freshbsd.org/ (really cool IMHO).
Thanks; I write/run that. I'm
* Edwin Groothuis ([EMAIL PROTECTED]) wrote:
I have made an update for the top(1) utility in the FreeBSD base
system to get it from the 3.5b12 version to the 3.8b1 version.
Looks good, thanks!
IO mode seems to have changed a bit, giving different values to 3.5, it
seems while 3.5 gives you
* Jeremy Chadwick ([EMAIL PROTECTED]) wrote:
On Mon, Aug 11, 2008 at 07:58:22AM +0100, Thomas Hurst wrote:
* Larry Rosenman ([EMAIL PROTECTED]) wrote:
ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=154593293
NAMESTATE READ WRITE CKSUM
ad8
* Larry Rosenman ([EMAIL PROTECTED]) wrote:
I'm getting the following on a zpool scrub:
ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=54817587
ad8: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=187521229
ad8: WARNING - READ_DMA UDMA ICRC error (retrying request)
* Evren Yurtesen ([EMAIL PROTECTED]) wrote:
I guess one good question is, how can one see the number of PV entries
used by a process? shouldnt these appear in the output of ipcs -a
command?
No, PV entries are a VM thing, not limited to SysV IPC.
Another good question is, in many places
* Evren Yurtesen ([EMAIL PROTECTED]) wrote:
How do I see what process is sharing memory and how much memory?
Guessing is normally sufficient; typically it's processes with the same
name and similar size/res. On 7-STABLE you can use procstat -v to look
at the VM mappings for a process, but
* Jeremy Chadwick ([EMAIL PROTECTED]) wrote:
I added it directly to the 2nd CPU (diagram on page 9 of
http://www.tyan.com/manuals/m_s2895_101.pdf) and the problem
seems to be the interaction between nfe0 and powerd :
That board is the weirdest thing I've seen in years.
K8WE's a
(kern/114438 btw)
--
Thomas 'Freaky' Hurst
http://hur.st/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
* Karl Denninger ([EMAIL PROTECTED]) wrote:
I have disks on the internal ICH7 adapters (on the motherboard), SATA,
and also a TWE controller with two disks.
When hitting the TWE controller hard I can hose the I/O performance on
the primary (onboard) adapter quite severely to the point that
* Chuck Swiger ([EMAIL PROTECTED]) wrote:
On Jan 25, 2008, at 11:24 AM, Joe Peterson wrote:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 114 071 006Pre-fail Always
- 82422948
[ ...
* Thomas Hurst ([EMAIL PROTECTED]) wrote:
* Kris Kennaway ([EMAIL PROTECTED]) wrote:
Excellent. I've been seeing this behavior for a long time, mostly on
backup runs (RAID-1 amr SATA - 1 disk Marvell ata). It's pretty odd
seeing a system with 8G of memory, 60% of which is just cache
* Kris Kennaway ([EMAIL PROTECTED]) wrote:
I don't understand your test procedure, can you elaborate?
The spikes from last night are from:
(/sbin/dump -$level -LuaC128 -f - $fs | /usr/bin/tee ${target} |
/sbin/sha1 ${target}.sha1)
Followed by:
nice -n 19 /home/freaky/bin/par2 c -t+ -r5
* Kris Kennaway ([EMAIL PROTECTED]) wrote:
Excellent. I've been seeing this behavior for a long time, mostly on
backup runs (RAID-1 amr SATA - 1 disk Marvell ata). It's pretty odd
seeing a system with 8G of memory, 60% of which is just cache, swap
out half a dozen things for no apparant
* John Baldwin ([EMAIL PROTECTED]) wrote:
We have noticed an issue at work but only on faster controllers (e.g.
certain mfi(4) drive configurations) when doing I/O to a single file
like the dd command mentioned causes the buffer cache to fill up. The
problem being that we can't lock the vm
* Jeremy Chadwick ([EMAIL PROTECTED]) wrote:
There's a periodic script (/etc/periodic/weekly/330.catman) which
rebuilds all the catman pages for you. However, it makes an immense
mess of your weekly system mails due to all the manpage/nroff
formatting mistakes. Have a look:
* Alexey Popov ([EMAIL PROTECTED]) wrote:
So I can conclude that FreeBSD has a long standing bug in VM that
could be triggered when serving large amount of static data (much
bigger than memory size) on high rates. Possibly this only applies to
large files like mp3 or video.
I've seen highly
I'm currently verifying a 50GB filesystem dump with sha1 at about
40MB/s. This is resulting in a small but annoying amount of swapping,
including my IRC client, text editors, even syslogd. Larger processes
like my .5G-each mysqld and squid don't seem to be effected:
Mem: 2045M Active, 5025M
* Vivek Khera ([EMAIL PROTECTED]) wrote:
I'll investigate this option. Does anyone know the stability
reliability of the mpt(4) driver on CURRENT? Is it out of GIANT lock
yet? It was hard to tell from the TODO list if it is entirely free of
GIANT or not.
Yes, mpt(4) was made MPSAFE in
* G?t Andr?s ([EMAIL PROTECTED]) wrote:
On these you've to forget the ipmi console, because once bge(4) loads
it blocks the bridge that the ipmi uses for remote console. There was
a patch for an older bge(4) driver, but on the 6.2 i couldn't patch
the driver. (I looked the source, but the
* Doug Barton ([EMAIL PROTECTED]) wrote:
If there is a consensus based on solid technical reasons (not emotion
or FUD) to back the root zone slaving change out, I'll be glad to do
so. I think it would be very useful at this point if those who _like_
the change would speak up publicly as well.
* Jeremy Chadwick ([EMAIL PROTECTED]) wrote:
* I'm left questioning why a disk manufacturer would process drives
(by this I mean the manufacturing process) differently based on their
transport type. It would cost a *huge* amount of money to have
separate fabs for SCSI, SAS, and SATA/PATA.
* Julian H. Stacey ([EMAIL PROTECTED]) wrote:
Either:
- You made a typo with ar0s2 meant ad0s2,
- Or you really mean ar - man 4 ar reports a comms card !
ataraid(4) exposes ATA RAID devices as ar%d:
-% man 4 ataraid |grep /dev
/dev/ar* ATA RAID device nodes
--
Thomas 'Freaky'
* G?t Andr?s ([EMAIL PROTECTED]) wrote:
So. The simple question is: Why FreeBSD has securelevel 0 if init sets
it to 1, if it sees at boot that the level is 0? :)
So when you boot to single user mode you can turn off immutable/append
only flags etc, without letting those capabilities propagate
* Bill LeFebvre ([EMAIL PROTECTED]) wrote:
The are only used when the process flag PS_INMEM is clear, which
is supposed to indicate that the process is or is not in memory.
This flag is only ever cleared in swapout, called from swapout_procs.
My bet is that the processes are being marked
* Vivek Khera ([EMAIL PROTECTED]) wrote:
Has anyone successfully booted FreeBSD 6 on the new M2 variants of
sun's X2100 or X4100 boxes? I have three X4100 original versions that
works stunningly well (but I don't use the internal disks) with
FreeBSD 6.1. I was just curious how the new ones
* Bill Moran ([EMAIL PROTECTED]) wrote:
Are you actually using /dev/random and not /dev/urandom?
/dev/random is military grade random data. It will block if it
feels that it hasn't gathered enough entropy to satisfy your request.
It will never provide random data at any reasonable speed,
* Damian Gerow ([EMAIL PROTECTED]) wrote:
I tried updating the BIOS on my K8WE (S2895) yesterday to 1.03, but
after the update, FreeBSD (RELENG_6 dated March 26) would randomly
freeze after booting.
As I was updating from v1.01, I suspect it may be the updates to
the nVidia SATA firmware
* Christoph Schug ([EMAIL PROTECTED]) wrote:
IIRC I had the problem that 'gmirror insert' without '-h' not always
inserted the slice specified by the entire block device (e.g.
/dev/ad4s1 vs. /dev/ad4). Apparently there is some auto detection
code and/or gmirror cannot differ correctly, but
* Brooks Davis ([EMAIL PROTECTED]) wrote:
The SII3112 is a piece of crap that won't work reliably. Order
something better (Soren recommends Promise cards).
Are all Promise cards currently supported? Even their 8/16+ port
SATA-II RAID6 cards? PCI-Express? The list of supported controllers
* David Sze ([EMAIL PROTECTED]) wrote:
super-smack select-key
5.4-RELEASE ~20,000 queries/second
6.0-CURRENT ~24,000 queries/second
CentOS w/async ~36,000 queries/second
CentOS w/sync ~26,000 queries/second
Uh, this should be an
* Steve Roome ([EMAIL PROTECTED]) wrote:
We're trying to get FreeBSD to perform reasonably well, in comparison
to Linux, or even what we should expect to see. We're getting about
half the performance we get from gentoo on the same application
(mysql).
Fancy giving CURRENT a try?
For the
* Søren Schmidt ([EMAIL PROTECTED]) wrote:
No, my only advise is to use the ATA mkIII patches or better yet -
current..
In a similar vein, I'm seeing the same WRITE_DMA timeouts and system
lockups using ATA mkIII patches as I did using the standard RELENG_5
driver, on two seperate systems.
* Doug White ([EMAIL PROTECTED]) wrote:
Ah, so they are all on the same bus. Yuck, performance is going to be
sucky. Bad Tyan, no cookie. That'll also explain the limited number
of interrupts available. I don't think there's anything we can do to
help the situation, sadly.
Buy a PCI-X
* Helge Oldach ([EMAIL PROTECTED]) wrote:
Count this my strong vote against removal of packages that are
traditionally part of the base system.
I hate sendmail with a passion. I use exim; hence it's just added
bloat sitting in my rather full /usr.
The existance of more up-to-date ports for
* Andrew Cowan ([EMAIL PROTECTED]) wrote:
It is really to much work to change the script variable names in
current, so that they relate exactly to what they do? eg.
ipfw_load_firewall_rules={yes,no}
ipfw_firewall_rules_file={open,simple,etc,/etc/myfirewall.rule}
The -stable
* Nuno Teixeira ([EMAIL PROTECTED]) wrote:
- why not integrate portupgrade with the main FreeBSD tree?
The main tree wants to be small; it's installed on all machines, from
little gateways sitting in the corner and *just* fitting on the drive,
to big-ass servers. Many of these machines
41 matches
Mail list logo
